How it shows up
Last year's team could run the book of work. This year's book needs extra coordinators, extra reports, extra meetings. Output per person is not rising. Coordination per person is.
Why it happens
The process was designed around a volume that fit in a few heads. Software was never asked to absorb the repetitive stitching. Hiring was easier to explain than redesigning the path.
If nothing changes
The organization eventually hires people primarily to coordinate other people and systems.
Money
Gross margin thins because overhead grew in lockstep with revenue.
Time
Lead time stretches because the queue of coordination grew.
People
Good operators are promoted into coordination and then buried in it.
Process
Every new hire is trained on the workarounds, so the workarounds become culture.
Customers
Service feels slower even as the company 'invests in people'.
Risk
The business cannot run without the coordinators. That is a fragile kind of scale.
Growth
The next increment of volume requires another layer of administration.
Questions worth asking
If volume doubled, what would you have to hire: producers or coordinators?
Which tasks exist only because two systems or two teams do not connect?
Where does a manager still have to personally unblock a file?
What is the actual constraint: labour, machines, or information moving?
What would you stop doing if the process carried its own follow-up?
When it is working
Volume can rise without a matching rise in administrative roles. Exceptions still need people. Routine stitching does not. Management watches capacity and exceptions.
What we might actually do
Workflow
Repetitive paths with clear states so a person is not the router.
Scheduling and dispatch support
When the constraint is assigning work.
Self-service status
Removes a class of coordination traffic entirely.
Automation
After the path is stable. Automating chaos scales chaos.
When software is the wrong first move
- Demand is erratic and the underlying process is not stable enough to encode.
- The constraint is genuinely labour or equipment, not information.
- Leadership wants a tool instead of deciding who owns the process.
Where we see it
Roles this hits
Related problems
Selected work
Comparable files are walked through in a working session. We do not invent percentages for the website.
Describe the process as it runs. A specification is optional.