An 88-page process manual from an integrated advertising agency. The document described how work moves from client intake through creative execution and delivery. It had been created during an internal initiative, presented to leadership, and filed in a shared drive. The team referenced it occasionally. Nobody had ever read it as structural data.
The team had reorganized twice, added a standing sync, and hired a coordinator to manage the handoffs that kept breaking. The friction never went away.
| Total steps | 24 | Large for a single declared workflow |
| Total transitions | 27 | Non-linear: includes parallel execution paths |
| Unique roles | 7 | Spanning creative, media, coordination, production, and leadership |
| Cross-role transitions | 18 of 27 | 67% of all transitions cross department boundaries |
| Approval steps | 4 of 24 | Contract, business case, presentation, creative execution |
| Convergence points | 3 → 1 | Three parallel paths feed into a single step |
| Declared exceptions | 0 | No exception handling paths documented |
Bottleneck Risk
Three parallel execution paths converge on a single step. Nothing downstream can move until all three arrive. The team knew this step was slow. They assumed it was the person.
Detection basis: In-degree of 3 at convergence step. All three inbound transition IDs traceable to parallel paths in the execution phase.
Handoff Density
Two out of every three transitions cross a department boundary. Work changes hands constantly. The dominant pattern is a ping-pong coordination structure: the primary coordination role hands off to a specialist department, receives it back, and hands off again.
Detection basis: 18 of 27 transitions involve a role change between source step and target step.
Exception Fragility
Four steps branch into parallel paths, creating 17% branch density across the workflow. None of these branch points have declared exception handling. When something goes wrong at a branch, the workflow has no documented path for resolution. The team handles exceptions by feel.
Detection basis: 4 of 24 steps with fan-out of 2 or greater. Zero exception paths declared across entire workflow.
Role Concentration
One department owns 10 of 24 steps, spanning all three phases of the workflow. This role acts as the initiator, the coordination layer, and the scheduling function. If this department is constrained, the entire workflow stalls.
Detection basis: Single role assigned to 42% of all steps across definition, solution, and execution phases.
| The team believed | The structure showed |
| The bottleneck was a person | It was a convergence point where three paths meet |
| There were 3–4 major handoffs | 18 cross-role transitions — 67% of all movement |
| Exceptions were handled | Zero declared exception paths in the entire workflow |
Before the audit, the team had observations. After the audit, they had evidence.
The bottleneck they blamed on a person was a convergence point built into the structure. The handoff friction they experienced daily was measurable. The exceptions they caught by instinct had no structural support in the documented process. All of it was already declared in the document. Nobody had read it that way.
None of this required a consultant's opinion. It required reading the organization's own documentation as structural data, which is what the engine does.