The deck was excellent. Multi-dimensional, well-argued, board-ready. Then someone had to make it real — and the company reached for a spreadsheet and a business controller.
I have watched this pattern twice now, in two different organisations, in two different sectors. The shape is identical enough that it is worth naming.
A large consulting firm arrives. Over several weeks — sometimes closer to twenty than to two — it produces a genuinely good strategy. Multi-dimensional, properly argued, appropriately ambitious. The board signs off. The consultants leave, or step back into an advisory perch. And the organisation is left holding a document that now needs to become reality.
At that point, a title appears. Strategy Implementation Lead. Transformation Manager. Someone is appointed, a mandate is implied, and the company tells itself the hard part is now underway. It usually isn’t. What actually gets built is a tracking function — and the person who ends up running it is, more often than one would expect, a business controller.
That is not a coincidence. It is a symptom.
“Implementation” is the wrong word for what happens next
Transformation, as a discipline, means shifting how an organisation decides, prioritises, and behaves under pressure. What actually happens after the consultants leave is something narrower: executing a long list of activities of wildly different character — one-off tasks, process management, process redesign, new projects, occasionally something that deserves to be called a programme. Bundling all of that under “transformation” flatters the work. It also sets an expectation the role was never built to meet.
The mislabelling is not harmless. It tells the board that direction-setting authority sits with the role, when in practice nobody sat down and decided that it should.
The business controller is not a coincidence
Once you see what the role is actually asked to do, the appointment makes sense. Somebody needs to catch the dollar impact — confirm that the initiative marked “done” actually moved the number it was meant to move, chase the owner who hasn’t updated their line in six weeks, keep a defensible record for the next board pack. That is a controller’s instinct and a controller’s skill set. It is a legitimate job. It is just not the job the title claims to describe.
The confusion is not that a controller was chosen. It is that the organisation needed a tracking-and-reconciliation function and bought a transformation title instead, then wondered why transformation didn’t happen.
Tracking a hundred-line list is not managing execution
The visible output of these roles is usually a dashboard — sometimes well over a hundred lines, colour-coded, refreshed weekly, presented with genuine effort. It is a real artefact and it has real value: it makes status visible. What it does not do, and was never built to do, is manage execution. There is no lever in a spreadsheet for stopping a low-value initiative, re-baselining a slipping one, or reallocating capacity from one workstream to another. Visibility and control are different things, and the gap between them is exactly where these programmes lose momentum without anyone being able to say precisely when.
Strategy execution implies authority you didn’t give anyone
“Execution” is doing real work in this sentence — it implies that whoever holds the role can influence how the plan unfolds, including changing the direction of unfolding when the facts on the ground contradict the deck. In both cases I am describing, that authority didn’t exist. The expectation, explicit or not, was to hold the line on what the consulting firm had written and report deviations upward, not to adjust course. That is compliance monitoring wearing an execution job title. It is a perfectly coherent thing to ask someone to do — but it should be named as such, and staffed and evaluated as such.
Strategy definition and strategy implementation are different disciplines
The firm that is excellent at building a strategy is frequently unequipped to help deliver it — not through lack of competence, but because the two activities call for different instincts. Definition rewards synthesis, structure, and a defensible narrative. Delivery rewards the willingness to renegotiate scope with a director three levels above you, to kill a workstream that isn’t working, and to sit in the discomfort of an unresolved priority collision for longer than feels comfortable. Assuming the same team, or the same organisational muscle, can do both is where a lot of these engagements quietly go wrong before anyone notices.
The fact that a dedicated body of knowledge exists for this second discipline is telling in itself. The Strategy Implementation Institute trains and certifies specifically in the competencies that separate a well-argued strategy from one that actually lands — treating implementation as a distinct professional skill set rather than an extension of the planning work. If the market has decided the two need separate training, separate certification, and separate ways of thinking, that’s a reasonable hint that they need separate people, or at least a deliberate handover between them. It is also, incidentally, the reason it is worth asking a prospective advisor directly whether they also implement what they design — the answer tells you which of the two disciplines you are actually buying.
The hidden assumption underneath all of this
There is a second, quieter assumption running through both cases, and it is arguably the more consequential one. The strategy gets handed down not just to a Transformation Lead with a tracker, but to every functional director, every manager, sometimes every senior specialist — with the implicit expectation that, on top of their line responsibility, they will now also run the projects that deliver their slice of the plan.
That expectation is rarely examined out loud, because it is rarely stated out loud. Nobody writes “we assume every department head is also a competent project manager” into the strategy document. But it is there, embedded in how the delivery plan gets built: a hundred-line list, each line with an owner, each owner already carrying a full-time functional job. The organisation has quietly assumed not only that these people will find the time and the motivation — a large enough assumption on its own — but that they already possess the competencies to plan, sequence, resource, and de-risk a project. As if project management were a skill that comes bundled with seniority, the way reading a P&L supposedly does.
It doesn’t. Running a project — scoping it properly, managing its risks, handling the change it creates in other people’s routines — is a distinct skill set, and a good functional director or a strong specialist has no particular reason to already have it. Most don’t, because their careers never required it until this strategy did. This is a large part of why the tracker-with-a-transformation-title pattern takes hold so easily: the organisation needed real project management capability distributed across dozens of owners, didn’t build it, and defaulted to central tracking as a substitute for capability it never installed.
What this costs
The cost rarely shows up as a single dramatic failure. It shows up as drift: initiatives that slip a quarter at a time without a clear decision point, a tracker that grows more detailed while the underlying numbers stay flat, and a person in an implementation-titled role who burns out trying to informally exercise authority nobody formally gave them. Underneath much of that drift sits the same root cause as the assumption above: owners who were never actually equipped to run what they were handed. By the time the board asks why the transformation hasn’t landed, the honest answer is usually two-fold — nothing with the authority to transform was ever appointed, and nobody who owned a piece of the plan had the grounding to deliver it.
Three things to secure before the strategy is finalised
If the gap is created this early — at the point where a hundred-line plan is handed to people who were never equipped to run projects — the fix has to start at the same point, not six months later when the tracker is already struggling. Before the document is finalised and the ownership list is locked, it is worth deliberately securing:
- Baseline project management literacy for non-project-managers. Not a certification track — a working vocabulary and a handful of habits: what a scope actually is, why a milestone needs a date attached to a deliverable rather than a wish, how to raise a risk before it becomes an issue. Every owner on that hundred-line list needs enough of this to run their piece competently, and it needs to exist before the plan is finalised, not be discovered mid-delivery.
- Practical change and risk management competence — and tools — for the same audience. Delivering a piece of the strategy almost always means changing how other people in the owner’s area work. Most functional owners have never had to manage that deliberately, and fewer still have a simple tool for spotting and tracking risk before it becomes a fire. This does not need to be a heavyweight methodology; it needs to be usable by someone who is not a change professional and does not have the bandwidth to become one.
- A strategy implementation framework that aligns the main stakeholders, not just the owners. Beyond individual competence, the organisation needs one shared way of talking about how the plan gets delivered — a common language for the sponsor, the functional directors, and whoever ends up coordinating the whole thing. Without it, every owner interprets “implementation” slightly differently, and the coordinating function spends its energy reconciling interpretations instead of managing delivery.
None of these three is expensive relative to the cost of discovering, a year in, that the strategy stalled because nobody who owned a piece of it had ever run one before.
What to ask before you hand someone the title
Before naming a Transformation Lead or Strategy Implementation Manager, it is worth answering three questions in writing, not in principle. Does this person have the authority to stop, hold, or re-baseline an initiative — or only to report that it’s off track? Is there a route back to the strategy’s authors when reality diverges from the plan, or is the mandate simply to hold the line regardless? And does the title match the actual decision rights being granted, or is it doing rhetorical work the role’s mandate doesn’t back up? An honest answer to all three, before the appointment is made rather than after the dashboard is built, is usually enough to tell you whether you are hiring a transformation lead or a very well-organised tracker.
A tracker with a transformation title is still a tracker.