Why execution is a discipline rather than an outcome: the operating cadence of metrics and reviews that move behaviour, transformation portfolios that survive the front line, and cost programmes that stick.
In short
- Execution is not what happens after the decisions; it is a discipline with its own instruments — a cadence of metrics and reviews, a transformation portfolio and a cost programme — each of which the COO must design rather than inherit.
- A cadence works when the metrics change what people do the following week. A cadence that produces accurate reports and unchanged behaviour is reporting, not execution.
- Transformations die at the front line because that is where the design meets the people who must live with it, and most portfolios are built as if that contact were somebody else’s problem.
- Cost programmes stick or fail on sequencing and morale, and on knowing the point at which further cuts destroy more than they save.
- The test of execution discipline is a decision the cadence changed, a transformation the front line adopted, and a cost programme whose savings were still there a year later.
On this page
Execution is a discipline, not a phase#
Execution is usually described as what happens after the decisions: the strategy is set, the model is chosen, and then the organisation executes. Treated that way, it becomes nobody’s design and everybody’s excuse. The COO seat exists because execution is a discipline in its own right, with its own instruments — a cadence of metrics and reviews, a transformation portfolio and a cost programme — each of which must be built deliberately rather than inherited from the last reorganisation.
The cadence: metrics and reviews that move behaviour#
The first instrument is the operating cadence — the rhythm of metrics that are measured and reviews at which they are examined. Every institution has one. The question is whether it moves behaviour. A cadence works when the metrics change what people do the following week: a number is missed, the review asks why, a decision is taken, and the next number shows the difference. A cadence that produces accurate reports and unchanged behaviour is reporting, not execution, however handsome the dashboard.
The COO’s craft in the cadence is selection and consequence: few enough metrics that each is watched, chosen so that the people measured can actually move them, and reviews at which something is decided rather than noted. The moment reviews become a place where numbers are presented and nothing follows, the organisation learns that the cadence is theatre, and behaves accordingly.
Why transformations die at the front line#
The second instrument is the transformation portfolio: the set of changes the institution is trying to make at once. Most portfolios are designed with care and die on contact with the front line, because the front line is where the design meets the people who must live with it — the branch, the plant, the operations floor, the service desk. A portfolio built as if that contact were somebody else’s problem produces the familiar pattern: launched with conviction, adopted on paper, quietly worked around in practice.
A cadence that produces accurate reports and unchanged behaviour is reporting, not execution, however handsome the dashboard.
A portfolio that survives contact is built differently. It is sized to what the front line can absorb, not to what the executive committee can approve. It sequences changes so that the same people are not asked to relearn their work three times in a year. And it treats adoption as the measure — not the launch, not the training completed, but whether the new way of working is the way the work is actually done. That measure belongs in the cadence, which is how the two instruments connect.
Cost programmes that stick#
The third instrument is the cost programme, and its failure mode is the best documented: savings announced, delivered on paper, and gone within a year as the costs return under other names. Cost programmes stick or fail on three things.
- Sequencing: removing the work before removing the people who did it, rather than the reverse.
- Morale: an institution that has watched capable colleagues leave does not execute the next transformation with conviction.
- The point of diminishing cuts, beyond which each further reduction destroys more capability than it saves — which the COO must be able to name before the programme starts rather than discover after it ends.
Where the discipline goes wrong#
The three instruments fail together more often than separately. A cadence that only reports allows a portfolio to be launched without adoption ever being measured, and a cost programme to declare victory on a spreadsheet. The common root is the same as in the operating model: nobody was accountable for the outcome, only for the activity. The COO seat is the correction — one executive who answers for whether the promise was kept, and who therefore has reason to design instruments that tell the truth.
What good looks like#
Execution discipline can be tested with three questions, each demanding a specific. Name a decision the cadence changed in the last quarter. Name a transformation the front line has adopted as the way the work is done, not merely completed training for. Name a cost programme whose savings were still in the numbers a year after it closed. A COO who can answer all three with specifics holds the seat; one who answers with process descriptions is describing the theatre. The second movement of The COO: Operations at Scale works exactly these three instruments through cases drawn from institutions across industries.
Frequently asked
What is execution discipline in an organisation?
Execution discipline is the deliberate design of the instruments by which decisions become outcomes: an operating cadence of metrics and reviews that change behaviour, a transformation portfolio sized and sequenced for the front line, and cost programmes whose savings persist. It treats execution as a discipline with an owner rather than as the phase that follows strategy.
What makes an operating cadence effective?
Whether it changes what people do the following week. That requires few enough metrics that each is watched, metrics the people measured can actually move, and reviews at which something is decided rather than noted. A cadence that produces accurate reports and unchanged behaviour is reporting, not execution.
Why do transformation programmes fail at the front line?
Because the front line is where the design meets the people who must live with it, and most portfolios are built for what the executive committee can approve rather than what the front line can absorb. Portfolios that survive are sized to absorption capacity, sequenced so the same people are not asked to relearn their work repeatedly, and measured on adoption rather than launch.
How do you make a cost reduction programme stick?
Three things decide it: sequencing, so that the work is removed before the people who did it rather than the reverse; morale, because an institution that has watched capable colleagues leave does not execute the next change with conviction; and knowing the point of diminishing cuts — beyond which each reduction destroys more capability than it saves — before the programme starts rather than after it ends.
The programme behind this article
Work through this material with the practitioners who wrote it.
The COO: Operations at Scale
The widest seat in the house — running today’s operations while building tomorrow’s, for COOs and operations executives with an enterprise remit.
View the programme →The CHRO Agenda: People, Culture & the Board
For chief people officers with an enterprise mandate — talent argued in commercial terms, culture as a governed asset, succession the board can defend.
View the programme →Executive Presence & Boardroom Communication
How senior executives earn the room — briefing boards, answering hostile questions and being trusted with bad news.
View the programme →