Why the Plan You Paid for Is Still in a Drawer

Almost every owner-led business I walk into has had strategic work done before. Sometimes twice. The document is usually good. Occasionally it is very good. And a startling amount of the time, nothing in it is running.

Owners tend to blame themselves for this, or quietly conclude that consulting does not work. Neither is quite right. The failure is structural, and once you can see the structure you can check for it before you spend the money.

Why Does Implementation Fail So Consistently?

The People Who Would Implement It Are Already Fully Committed

In a company of thirty to three hundred people, the individuals capable of driving a cross-functional change are the same individuals currently holding the business together. There is no bench. So the roadmap goes to the person with the most capability, who is also the person with the least available time, and it waits behind the things that will break today if ignored.

The Deliverable Is a Document, Not a Working Thing

A recommendation transfers the hard part to you. Somebody still has to design the workflow, configure the system, write the procedure, train the team and handle the first six weeks of complaints. That work is most of the work, and it is almost never what was purchased.

Nobody Owns the Sequencing

A good roadmap has fifteen initiatives on it. Three get started because three feel urgent. All three are partially done at the point where the fourth thing catches fire. Partial implementations are worse than none, because the organisation now has two ways of doing everything and no confidence in either.

The Commercial Relationship Ended at Delivery

This is the uncomfortable one. If the advisor is paid on delivery of a document, the advisor is economically indifferent to whether anything changes. Not dishonest — just pointed somewhere else. Nobody is measuring the adoption curve because nobody is being paid to care about it.

What Actually Predicts Whether a Change Holds?

From the engagements I have watched succeed and fail, three things predict it better than the quality of the analysis:

• Whether a working system existed at handover. Changes that arrive as software, a form, a dashboard or a redesigned workflow survive. Changes that arrive as an agreement to behave differently do not.
• Whether one named internal person had authority to unblock. Not accountability for the outcome — authority to remove obstacles. These are different, and only the second one matters during a build.
• Whether anyone was still measuring at month six. A system nobody watches decays to the previous state within about a year, in my experience faster in businesses with high staff turnover.

Six Questions to Ask Before You Sign

These are the questions I would ask if I were buying rather than selling. Any firm worth hiring will answer all six without hedging.

• What exactly is in my hands on the last day — a document, or something running?
• Who builds it, and are they the same people who diagnosed it?
• What is the baseline measurement, how is it captured, and when?
• Which of your own clients' initiatives did not stick, and what did you learn?
• What does your engagement look like at month six, and what are you paid for then?
• What would make you tell me not to proceed?

That last one is the most revealing. A firm that has never turned work down is not diagnosing anything.

What This Means for How You Buy

Buy the diagnostic separately and cheaply, so you can stop. Buy the build as a build, with a working system named in the scope. And structure the back half so somebody is still economically attached to the outcome when the novelty has worn off and the first exception hits.

That is the whole argument for the operating-partner model, and it is why our own method is shaped the way it is.