The Consultant Trap: Why the 500-Page Binder Always Fails
I spent 21 years leading digital transformations from the inside — which means I have been on the receiving end of the deliverable that looks impressive, satisfies the statement of work, and quietly fails six months after the consultants leave.
A firm is engaged to deliver a management system. A team arrives, runs a discovery phase, and produces a comprehensive documentation set — professionally produced, mapped exhaustively to every clause and control. It is presented at a closing workshop. Then the organisation is expected to operate it. The operating model described in those documents was designed by people who were in the building for eleven weeks.
Why it fails, specifically
- The processes describe an organisation that does not exist. Consultants write to the model. The document describes a three-tier review board with defined quorum, in a company where actual decisions are three people on a Thursday call.
- Nobody owns anything. Documents produced externally get accepted rather than authored. There is a difference between a policy someone wrote and a policy someone was handed.
- The rationale left with the team. A management system is a series of judgement calls. When the reasoning lives only in the consultants' heads, the first time reality diverges from the document the organisation has no basis for adapting it.
- Nothing was practised. The internal audit procedure has never been run. The incident process has never been triggered. A management system that has not completed a full cycle before certification is a design, not a system.
The alternative
Building with a team rather than for them: your people draft, we edit. Design decisions are made jointly and recorded with rationale. Everything is exercised before it is audited. And capability transfer is a deliverable — someone internal must be able to run the next cycle without us. If they cannot, the engagement has not succeeded, whatever the certificate says.