When 10,000 People Have No SOPs
Recovered from re-explaining the same process to the same people every week.
Work done by a MetMov partner in an operating role, inside the company, before MetMov. Not a client engagement. The employer is not named.
Key results
- 01
- Non-Value-Add Hours / Month: from Hidden, accumulating to 100 hours recovered
- 02
- Workforce Covered: from Tribal pockets to 10,000+ members
- 03
- Process Discoverability: from Search by asking a person to Search by query
- 04
- SOP Ownership: from Unassigned to Named owner per SOP
- 05
- Cross-Hub Process Variation: from High to Standardised baseline
- 06
- Onboarding Self-Service: from Minimal to Repository-led
Documentation Deficit Syndrome
In a fast-scaling commerce and supply chain organisation, the operating knowledge lived inside people, not inside systems. A process worked because a specific manager remembered how it should be done. A workflow ran because a particular analyst had built the spreadsheet two quarters ago and was still on the team.
At 10,000+ workforce members spread across hubs, central operations, finance, and category teams, this model had quietly broken. Nothing was documented in a way the next person could find. Nothing was discoverable in a way the next site could reuse.
The visible symptoms:
Re-explanation overhead. Senior managers were spending hours every week answering the same questions across hubs. The same induction conversation, the same escalation matrix, the same exception path — repeated, never written.
Onboarding lag. New hires took weeks to find their footing because there was no place to read how things actually worked. They learned by interruption, not by reference.
Process variation. The same workflow ran differently in different cities. Each variant was defensible locally and indefensible at scale.
Knowledge loss on attrition. When a process owner left, an unrecoverable amount of operating knowledge walked out with them.
The organisation was not undertrained. It was underwritten. Knowledge was tribal, and tribes do not scale.
What the Surface Symptoms Were Hiding
The instinct is to call this a documentation problem and assign someone to "write SOPs." That fails predictably. SOPs written without an underlying architecture become a graveyard of shelfware.
The actual diseases were structural:
- Documentation Deficit. There was no canonical place for process truth, no naming convention, no ownership map, and no discovery layer. Even the documents that did exist could not be found in under five minutes.
- Scaling Fracture. The organisation had crossed the headcount threshold where tribal knowledge stops working, but the operating model had not adapted. The cost of every undocumented process compounded with each new hire and each new market.
Until both diseases were treated together, writing more documents would not have moved the number.
What Was Built
A digital process repository was designed and rolled out across the org. Four structural layers:
Discussion
Ready for a similar transformation?
Install your Operating Spine in 90 days. Start with a short scoping call.