Waiting "Temachi"

The Muda of Waiting: What “Temachi” Really Means

In the Toyota Production System, we often talk about muda. One important type is the muda of waiting. But the original Japanese term that Taiichi Ohno used is a bit more nuanced: “temachi” 【手待ち】.

Let’s unpack that.

What Is “Temachi”? 手待ち

The word temachi is written as:

• 手 (te) – hand

• 待ち (machi) – wait

Literally, it means “waiting hands.” In a production or work context, this is when hands — people, machines, or resources — are idle, waiting for something else to happen.

Interestingly, temachi is also a term used in Japanese chess (shogi). In shogi, it refers to a move in which you effectively pass your turn. You move a piece, but the move has no real impact on the game. You’ve used up your turn without improving your position.

In other words, you wasted your turn.

Wasteful Waiting vs. Strategic Waiting

Not all waiting is bad. Just as in shogi, there is such a thing as a strategic pass.

In manufacturing or knowledge work, strategic waiting can be used to:

• Avoid overproduction.

• Prevent building inventory that no one needs yet.

• Maintain flow across the whole system instead of optimizing one local step.

This kind of waiting is deliberate. You “hold your move” so that the overall system performs better.

By contrast, temachi as muda is when:

• People are waiting for approvals, information, or materials.

• Machines are idle due to poor scheduling or breakdowns.

• Work-in-progress is stuck in queues with no good reason.

Here, the waiting doesn’t serve a higher purpose. It’s just a lost turn.     

Why “Temachi” Matters in Daily Work

Thinking in terms of temachi helps us notice where our “hands” are waiting:

• A developer is blocked on unclear requirements.

• A designer waiting days for feedback.

• A production line stopped for parts that haven’t arrived.

Each of these is a kind of wasted move.

At the same time, we shouldn’t rush to eliminate every instance of waiting. Some pauses are intentional buffers that keep us from creating more than our customers need.

The key question is:

Is this waiting a wasted turn, or a strategic pass?

When we can answer that honestly, we can begin removing true muda while preserving the strategic pauses that protect flow.

By the way, why is there a “Temachi” move in Shogi? Shogi has many defensive formations that, once in place, make it very difficult to attack. Instead of trying to break through the defense, this “Temachi” move serves as bait to open it. The same principle applies in operations. When there is “Temachi,” we should consider ways to grow, given the available resources.

In business, we often treat “waiting time” as a problem to eliminate. Idle headcount, spare server capacity, or unallocated budget are seen as waste. But just as in Shogi, “Temachi” can be a deliberate and powerful move — not an accident.

When operations are stable and resources are not fully stretched, we have a choice:

1. Force an attack: push teams harder, add more projects, and squeeze every drop of capacity out of the system.

2. Play Temachi: intentionally create a brief pause or a side move that creates new opportunities — testing a new market, piloting a product, or experimenting with a better process.

The second option is often underrated. A period of “Temachi” can be the perfect moment to:

• Run small experiments that would be too risky when the team is overloaded.

• Invest in capabilities like training that will pay off in the next growth curve.

• Re-examine constraints and discover new paths for revenue or efficiency that were hidden behind day-to-day firefighting.

In other words, “Temachi” in operations is not simply standing still. It is a strategic pause that invites the environment — customers, market conditions, competitors — to react. When they do, your organization is free and ready to respond.

Many teams misunderstand this phase. They worry that if everyone isn’t visibly busy, something is wrong. So they quickly fill the gap with low-impact tasks and cosmetic projects. The result is motion without progress.

Treat “Temachi” differently:

• Name it: acknowledge, “We are in a Temachi phase right now.” This reframes idle capacity as intentional rather than accidental.

• Define the move: what small moves can you make to open a new line of attack? A limited release, a pricing experiment, or a new partnership conversation.

• Protect slack (which we call “Yoryoku”): resist the urge to fill all available capacity with routine work. Slack gives you the freedom to seize real opportunities when they arise.

In Shogi, a careless Temachi loses tempo, handing the initiative to the opponent. A well-designed Temachi, however, creates exactly the opening you were waiting for. The operations are the same. The question is not “Do we have downtime?” but rather “Are we using our Temachi to set up our next move?”

When you notice space in your operations, don’t rush to fill it. Ask instead: What is the best Temachi we can play right now to unlock our next stage of growth?