Waiting should have an owner

A waiting status can look organized on the surface. The task is not active, so it gets marked as waiting and dropped out of immediate attention. The problem is that a lot of work does not come back on its own.

Maybe it is waiting on approval. Maybe it is waiting on a customer reply. Maybe another team owes an input before the next step can happen. Those are normal situations. The failure happens when the work is marked as waiting and nobody is clearly responsible for checking back, following up, or pushing it forward.

That is how work starts to drift. It is still in the system, but not in a way that creates motion. Everyone can see that it is not done, yet nobody has the next move.

Good operations make waiting accountable. If something is blocked, somebody owns the unblock. If something is pending, somebody owns the next touch. If something is paused, the reason should be visible and the path back into motion should be clear.

Waiting is not a free parking spot for work. It is still a live state, and it still needs an owner.