Deciding what a company should do and making the company do it are not two halves of one job. They are different professions. Most organisations still hand both to whoever was sponsoring the strategy when it closed.
The strategy deck gets its own budget line, its own consultants, and months of executive attention. What happens after approval gets none of that. It gets added to someone’s existing job description, on top of a role that was already full. The assumption is that skill in the first job transfers cleanly to the second. It rarely does.
Two different skills get filed under one title
Building a strategy is an analytical act. It rewards market pattern recognition and capital allocation judgement. It rewards the nerve to make a defensible bet before all the evidence is in. The people who are good at it can hold several futures in mind at once, then choose between them under real uncertainty.
Making a strategy real rewards something closer to the opposite. It takes discipline to hold one direction steady for eighteen months while smaller decisions keep pulling it sideways. The work is less about insight and more about sequencing and repetition. It means having the same uncomfortable conversation in the same steering meeting for the fourth month running. Neither skill is rarer than the other. They are simply not the same skill. A strategy deck says nothing reliable about who in the room can do the second job.
Execution leadership is not atomising the strategy
The confusion runs the other way too. Some organisations respond to the gap by appointing someone to “operationalise” the strategy. What that person actually does is cut it into workstreams, hand each one to a function head, and call the result an execution plan. The strategy survives as a set of headings. The intent behind it does not survive the cut — why this direction and not another, what trade-off it was built to make.
Real execution leadership does the opposite. It treats an approved strategy as a fixed input, not a draft awaiting a rewrite. It builds the operating rhythm that keeps every downstream decision honest against that input. The job is not to decide what the company should do; that decision is already made. The job is to make sure the thing delivered eighteen months later is recognisably the thing that was approved — not a drifted, well-intentioned relative of it.
Cadence is a discipline, not a calendar entry
A recurring meeting is not a cadence. A cadence is a fixed rhythm. The same questions get asked, in the same order, every time. Consequences attach to the answers: actual movement against plan this month, what changed since last time, who owns a gap that has now shown up twice. Most organisations have the meeting. Far fewer have the consequences. A cadence without consequences degrades within two cycles into a status update nobody reads before the call.
Building that rhythm is a specific, learnable competence. So is holding it under pressure — especially in month four, once the early energy has gone and the first real setback has landed. It does not appear automatically once a strategy is approved, and it is not a by-product of good strategy work.
The portfolio is where strategy meets scarcity
A strategy names priorities in the abstract. A portfolio is where those priorities compete for the same finite engineers, the same capital, and the same executive attention. That is where an abstract ranking has to become a concrete one. It is usually the first genuine test of a strategy’s seriousness — well before any output ships. Two initiatives were both approved as priorities. They now collide over the same scarce resource. Does anyone have standing to choose, or does the choice default to whoever escalated loudest?
Owning the portfolio means owning that arbitration. Not as an occasional favour when a conflict gets loud enough, but as a standing, expected part of the role. Without it, prioritisation happens by accident. The strategy’s stated priorities and the organisation’s actual behaviour quietly drift apart.
A performance system has to measure movement, not activity
Most transformation dashboards report what has happened: workshops run, deliverables submitted, milestones marked complete. None of that says whether the number the strategy was meant to move has actually moved. A performance system built for execution has to be anchored to that number from day one. It has to stay honest when the activity is healthy and the outcome is not. That reading is the one nobody wants to present in a steering meeting — and exactly the one an execution leader exists to insist on.
This is where the role gets uncomfortable in a way strategy work rarely does. Strategy gets judged on the quality of its logic at the point of approval. Execution gets judged on a number, months later, that either moved or did not.
Follow-through is the part no system can hold
Cadence and a performance system will surface every open decision, every collision, and every stalled metric. Neither one closes anything by itself. Someone still has to chase the decision that is now two weeks overdue. Someone has to tell a sponsor that their pet initiative is the one losing priority this quarter. Then do it again next month, when the same pattern resurfaces wearing a different disguise.
That is follow-through. It is the least glamorous part of the job, and the most structurally load-bearing. A well-designed cadence and a clean dashboard make it easier to see and harder to fake. Neither one does it for anyone.
Why the role keeps getting scattered instead of owned
Given all that, it is worth asking why so few organisations actually appoint someone to hold it. The honest answer is that the role rarely gets created; it gets absorbed. Spare authority already sits with the COO, so cadence gets wedged into whatever calendar gaps are left. Financial control already belongs to the CFO, so the performance system becomes theirs — built for control, not delivery. Project tracking already belongs to the PMO, so portfolio arbitration lands there too, minus the standing to decide anything. Each piece goes to whoever sat structurally nearest. None of them was given the time, the mandate, or the seat to hold the whole thing together.
Scattering the role this way is rarely named as a choice, even though it is one. It guarantees that no single person is accountable for the strategy actually arriving. Every piece has an owner. The whole does not.
The title is starting to exist elsewhere
A small number of organisations have stopped treating this as a gap to absorb. They have started giving it a name — a strategy realisation office, a chief transformation role with real portfolio authority. Some define a mandate that explicitly spans cadence, portfolio and performance, rather than letting it sit inside just one of the three. The pattern is not yet common, and it is not worth a headline on its own. But it is evidence. At least some boards have noticed the same gap this piece has been describing. They have concluded that a residual duty, bolted onto an already full role, was never going to close it.
Approving a strategy and delivering one call on different people — or on the same person operating in two entirely different modes. Naming that difference honestly, and giving the mandate gap between the two an actual owner, is usually the cheapest fix available to a board. It is also the one most boards reach for last.
Strategy chooses the destination. Strategy execution is the discipline that gets the organisation there — and it deserves a seat of its own, not a line in someone else’s job description.