By The Skyline Project ·
A 30-minute working session
- Pick one outcome, such as orders ready to ship. Set start and end points so everyone measures the same process.
- Pick a recent period. Include typical orders and exceptions. Mark missing times as unknown and note whether the sample leaves out difficult cases.
- Draw the handoffs. Count open work at each step at a consistent time. Compare elapsed time with time actually spent processing the work.
- Choose one change, one owner and one review date. Track completions and check whether errors or unfinished work increase elsewhere.
Scrollable table: swipe horizontally to see every column. You can also focus the table and use the arrow keys.
| Field | Example entry |
|---|---|
| Work item and step | Order A17, payment review |
| Entry and exit | Tuesday 9:05 a.m. to Wednesday 10:00 a.m. |
| Active work and reason for wait | 5 minutes of review, waiting for authorized approver |
| Owner and test | Operations lead, defined backup approver on one shift |
The row is illustrative. If orders wait at approval, a backup approver could reduce waiting. If the real reason is incomplete documents, adding a backup alone will leave the queue in place. Track completed orders and the share returned for clarification during the pilot. A queue seen once warrants more observation before you redesign a workflow. NIST describes value stream mapping as a way to see the current flow and plan a future state. NIST value stream mapping.
See our growth strategy service or tell us where work gets stuck.
