Most Workflow Gaps Show Up as Waiting

When people picture a gap in a workflow they usually imagine a missing step. In my experience the gaps show up as waiting. A job sits. A quote waits for a number. An order waits for somebody to confirm a detail. The work is not stopped by effort. It is stopped by a missing answer.

Waiting is easy to miss because everyone is busy. The shop is running, the office is working, and each person is doing their job. But the job itself is idle. A company can look productive at every desk and still be slow.

On the floor I look for four kinds of waiting. Waiting for information. Waiting for approval. Waiting for a part or a person. And waiting for somebody to notice that something is stuck. The last one is the most common and the least discussed.

Each kind points to a different fix. Missing information needs a clearer handoff. Waiting for approval often means decisions are routed to the owner by default. Waiting for people or parts is a planning question. Nobody noticing is a visibility question.

The point is not to eliminate waiting. Some of it is reasonable. The point is to know where it happens and why, so the process removes the waiting that does not need to be there.

This week, choose one job and mark every point where it sits for more than a few hours. Beside each, write the reason. You will probably see the same two or three reasons repeat.

If you would like help finding where your work waits, reach out to us. Email us at info@devconsultantsllc.com or call (201) 540-7762.

Previous
Previous

A Workaround Is a Process Nobody Wrote Down

Next
Next

Follow One Job From the Door to the Dock