Follow the Work, Not the Organization Chart

A simple way to find where a job actually waits between customer request and cash.

A leader may ask every department where the bottleneck is and receive a different answer from each. Sales sees slow estimating. Operations sees incomplete scope. Field teams see missing material. Finance sees jobs that are complete but cannot be invoiced. Each answer can be true within a department. The governing constraint is the condition that limits completed value across the whole path.

Start with a unit of value that matters to the customer and the business: an accepted installation, a closed service call, a commissioned system, or an invoice-ready job. Then trace a small sample from demand to completion and cash. The question is not who is busy. It is where the work stops, loops back, or waits for a decision.

Draw the real path

For one representative job type, write the few states that matter: request, scope, approval, ready for release, field execution, quality acceptance, invoice, collection. Define the evidence that moves a job into each state. A scheduled date alone does not prove that the next step is ready.

Take 15 to 20 recent jobs, including smooth completions and late or reopened ones. For each, capture the date it entered and left every state, the reason for each hold, and the owner of the next decision. Compare what the system said with what happened in source records and in the field. Keep unknown timestamps marked as unknown rather than filling them with estimates.

A process map becomes useful when it shows where value waits—not merely where responsibilities sit.

Separate three different delays

• Waiting for capacity: ready work queues ahead of a scarce crew, specialist, machine, or approval role.
• Waiting to become ready: the job is scheduled but lacks scope, access, material, prerequisite work, or a decision.
• Waiting after completion: acceptance, documentation, billing, or collection holds value that the field has already created.

Those conditions call for different responses. Hiring a crew does little for jobs that cannot be released. A new dispatch board does little for work waiting on customer acceptance. A faster invoice step may improve cash while leaving field throughput unchanged. The trace tells leadership which outcome can actually move.

A small test, not a company-wide redesign

Suppose 18 of 20 jobs show a long elapsed time between approved scope and field release. Before changing staffing, inspect the release evidence on those 18 jobs. If 12 repeatedly waited for the same material confirmation, the first test is a narrow material-readiness rule with one accountable owner. Compare the next comparable jobs on ready-at-release rate, release lead time, completed jobs, and exceptions. These counts are illustrative, not client results.

Follow the result all the way to accepted, billable output. If the queue moves downstream, the constraint may have shifted. That is useful evidence. It means the original condition was real, and the next improvement can be chosen from the new operating picture.