Read any strategy cascade from the top and something happens two-thirds of the way down. It stops being about money and starts being about dates.
Here is a five-row cascade for a commercial property developer, reproduced in substance from a teaching example. It is presented in its source as a worked illustration, without commentary, and it is worth reading slowly.
- Corporate goal: grow the business by 5% over the next five years.
- Business goal: complete ten major developments over five years at an average profit of 7.5%.
- Programme goal: design, develop and establish for sale a mixed development — a park, a community centre and a light industrial complex — at a 10% profit margin.
- Project goals: the park, delivered for $90,000 within six months; the community centre, $1.2 million within eighteen months; the industrial complex, $3.4 million within twenty-four months.
- Individual goal: value manage the park project to save $10,000 and deliver one month early.
Nothing in that list is wrong. Every row is specific, measurable and traceable to the row above it. It is, by the ordinary standards of strategic planning, a good cascade.
And yet something breaks between row three and row four. The first three goals are denominated in growth and margin. The last two are denominated in cost and elapsed time. Somewhere between the programme and the project, the organisation stopped measuring the thing it wanted and started measuring something that correlates with it under conditions nobody stated.
The Strategic Context
Cascading strategy is one of the oldest disciplines in management, and the logic is sound. An organisation cannot act on a five-year growth ambition; it can act on a task with a date. The cascade exists to convert intent into something a person can do on a Tuesday.
The teaching material sets out the conversion carefully. A mission answers what business we are in and what our reason for being is. A vision defines the field of endeavour. Goals are general statements of aim in line with the mission, and may be qualitative. Objectives are the quantification, where possible, or a more precise statement of the goal. Strategies are broad statements of intent showing the types of action required. Actions are individual steps that link broad direction to specific operational issues and individuals.
Read that sequence carefully and you notice what it promises: increasing precision. Each level is meant to be a sharper statement of the same thing. Nowhere does the sequence license a change in what is being measured. The cascade is supposed to narrow the aperture, not swap the instrument.
But swapping the instrument is exactly what happens, in almost every organisation, at almost exactly the same point — and it happens because at that point the work becomes deliverable-shaped, and deliverables have costs and dates rather than margins.
What Leaders Commonly Misread
The first misreading is that cost and time are proxies for margin. They are, under conditions. Delivering a fixed-price component under budget improves margin if revenue is fixed, if the saving does not degrade the asset, and if the saving is not consumed elsewhere in the programme. Three conditions, none of them stated in the cascade, and all of them routinely false.
Consider the individual goal in the example: save $10,000 on a $90,000 park and deliver a month early. Both are real achievements. Both are also entirely compatible with reducing the programme's 10% margin — if the saving comes out of landscaping that the community centre's sale price partly depends on, or if finishing early simply means the site sits idle waiting for the industrial complex. The measure at the bottom can be satisfied in full while the measure at the top moves the wrong way, and nothing in the cascade would show it.
The second misreading is that the bottom of the cascade is where execution happens and therefore where precision belongs. This inverts the problem. Precision at the bottom is easy; fidelity is what is scarce. A goal can be perfectly precise and still be a poor representation of what the enterprise wanted. The park manager's target is more precise than the corporate growth ambition and less faithful to it.
The third misreading is that this is a communication problem. It is regularly treated as one — better line of sight, clearer cascading, more visible strategy maps. But the people at the bottom of the example understand the corporate goal perfectly well. They are not confused. They are responding accurately to the measure they were given, which is a different measure. No amount of communication changes an incentive.
A separate question is whether the signal that a target is drifting reaches anyone in time to act — a matter of detection and indicator design, treated in [Related article: Measuring an Outcome You Cannot Predict]. The problem here is prior to detection: the measure being watched is the wrong quantity, and watching it faster would not help.
A fourth error is subtler and belongs to the executive. Because each row is derived from the row above, the cascade looks internally consistent, and internal consistency is easily mistaken for validity. Every row can follow logically from its parent while the chain as a whole fails to preserve the quantity that matters. Derivation is not conservation.
Reframing the Issue
The useful reframing is to treat a cascade as a chain of unit conversions, and to ask at each link what was converted and on what exchange rate.
Growth to profit is one conversion. Profit to margin on a specific development is another. Margin to cost-and-schedule on a component is a third — and it is the third that is unexamined in most organisations, because it happens at the boundary between people who think about money and people who think about delivery, and neither group regards the conversion as theirs.
Two things follow immediately.
The exchange rate should be written down. Somebody decided that saving $10,000 on the park was worth pursuing. That decision embeds a view about what a dollar of construction saving is worth in margin terms — including whether it is worth anything at all. If nobody can state that view, the conversion happened by default.
The conversion is where the strategy is actually made. Executives believe strategy is set at the top of the cascade. In practice, the choice of what to measure at the delivery level determines what the organisation will do, and therefore what strategy it will actually execute. A margin ambition converted into a cost target produces a cost-minimising organisation, whatever the strategy document says.
There is a related failure that this article does not cover. Where a set of constraints contains conflicts nobody has ranked, the trade-off is resolved silently by whoever encounters it — a different mechanism with a different remedy, examined in [Related article: Read the Constraints, Not the Deliverables]. Here the constraints are not in conflict. The measure has simply changed species.
Strategic Analysis
Where the conversion happens, and why it is invisible
The conversion sits at the seam between the investment case and the delivery plan. Above it, work is described in financial terms because that is how it was funded. Below it, work is described in scope, cost and duration because that is how it is contracted and scheduled.
Both descriptions are correct for their purpose. The problem is that no artefact spans them. The business case states a margin; the project plan states a budget and a date; nothing in between records the reasoning that connects the two, and so nothing preserves it when circumstances change. Six months in, the margin assumption has moved and the cost target has not, because the cost target is in a system that does not know about margins.
Consider a university launching a new postgraduate portfolio. The corporate goal is a share of a growing market. The faculty goal is a specified number of enrolled students at a stated contribution per student. The programme goal is four new courses. And the project goal — the one the academic developer is actually measured on — is course accreditation by a date, within a development budget.
Accreditation by the date is achievable by narrowing the course. Narrowing the course is achievable within budget. Both measures are met. Enrolment falls short because the narrowed course is less attractive than the one the contribution assumption was based on, and nobody connected the two, because the person who narrowed it was optimising the measure they held.
A further consequence sits upstream. If the top of the cascade was never a genuine choice between competing investments, the conversion problem compounds a selection problem — whether the portfolio function chose at all is examined in [Related article: Is Your Portfolio Function Selecting, or Supervising?].
The asymmetry of correction
When the top-level measure disappoints, organisations look downward for the cause and find that every lower measure was met. This produces a characteristic and unhelpful conclusion: that the strategy was sound and execution was adequate, so the market must have moved.
Sometimes the market did move. But the cascade guarantees that this conclusion will be reached whether or not it is true, because a cascade whose units change cannot be audited end to end. There is no arithmetic that reconciles $10,000 of construction saving to five per cent of enterprise growth, and so the reconciliation is never attempted.
The asymmetry matters commercially. It means the organisation cannot distinguish a strategy that was wrong from a strategy that was correctly stated and incorrectly converted — and those two failures need opposite responses.
The bottom row assumes a person
One further quiet assumption sits in the individual goal. It presumes a person with the attention to pursue it. In matrix organisations that person is typically committed to several initiatives at once, and the target they will actually pursue is whichever one is most visibly measured — a capacity problem examined in [Related article: There Is No Such Thing as Half a Project Manager]. A measure in the wrong unit is worse when the person holding it is also divided.
What the cascade is good at, and should keep doing
None of this argues against cascading. A cascade does three things well: it makes work traceable to intent, it lets people at every level know what they are contributing to, and it creates the accountability structure without which nothing large gets done.
The argument is narrower. A cascade converts, and conversion loses information unless somebody records the rate. The remedy is not to abolish the instrument but to make one specific conversion explicit — the one where money becomes time.
Decision Framework
Five steps, applicable to any cascade already in place, and quick enough to run in a single session.
1. Write the cascade out in one column and mark the unit of each row. Growth. Profit. Margin. Cost and duration. Cost and duration. The point of change is usually visible at a glance, and it is usually lower than executives expect.
2. At the point of change, state the conversion. In one sentence: we are treating a dollar of delivery cost as worth a dollar of margin, on the assumption that revenue and quality are unaffected. Writing it down is most of the work, because it is very often the first time anyone has.
3. Test the three conditions. Is revenue genuinely fixed at this level? Can the saving degrade something the revenue depends on? Will the saving be consumed elsewhere in the programme? If any answer is uncertain, the conversion is unsafe and the lower-level measure needs a companion.
4. Add one measure at the delivery level that is denominated in the top-level unit. Not a replacement — a companion. The park manager keeps the cost and schedule targets and gains one measure expressed in margin terms, however coarse. A coarse measure in the right unit outperforms a precise measure in the wrong one.
5. Name the owner of the conversion. Someone must be accountable for whether the exchange rate still holds. In most organisations this is the programme owner, and in most organisations they do not know it is their job.
A useful test of whether the framework has bitten: ask the person at the bottom of the cascade what would have to be true for their target to be worth achieving. If they cannot answer, the conversion is undocumented.
From Strategy to Execution
Immediate. Take the cascade for the initiative with the largest financial consequence and run steps one and two. This takes under an hour and produces a written conversion statement that did not previously exist. In most organisations the exercise also reveals that two different parts of the business hold incompatible views of the exchange rate.
Medium term. Change the business case template so that it carries the conversion explicitly. One additional field — the delivery targets below derive from this financial objective on the following basis — placed where the investment case hands over to the delivery plan. This is the cheapest structural fix available and it survives staff turnover, which conversations do not.
Long term. Build the habit of measuring in the top-level unit at every level, even coarsely. This is harder than it sounds, because delivery organisations are structured to produce cost and schedule data and are not structured to produce margin data. The change is not primarily analytical; it is a decision about what the reporting line is for.
Signals to Monitor
- Lower-level targets met while the top-level measure disappoints. The single clearest indicator, and it should trigger an examination of the conversion rather than of the market.
- Savings that nobody can trace to a financial outcome. When delivery reports a cost underrun and no one can say what it was worth, the exchange rate is undocumented.
- Early delivery treated as unqualified good news. Finishing ahead of schedule creates value only if something downstream can use the time. Where early delivery is celebrated without that question being asked, the schedule measure has become an end in itself.
- Disagreement between finance and delivery about whether an initiative succeeded. This is usually not a disagreement about facts. It is two groups reading two different units and each being correct.
- Business cases whose financial assumptions are never revisited after approval. If the margin assumption is fixed at approval and the cost target is managed continuously, the two have detached, and only one of them is being governed.
Questions for the Leadership Team
- On our largest current initiative, at exactly which level does the measure stop being financial — and who made that conversion?
- Can anyone state, in one sentence, the exchange rate between a dollar of delivery saving and a dollar of margin on that initiative?
- What would have to be true for our delivery-level targets to be worth achieving, and have we tested it?
- When a lower-level target is met and the enterprise outcome is not, what does this organisation conclude — and is that conclusion available to us on the evidence?
- Who is accountable for whether the conversion still holds six months after approval?
- Is there a single measure at delivery level anywhere in our portfolio that is denominated in the unit the board actually cares about?
Closing Perspective
A cascade is a translation, and every translation loses something. The question is not whether loss occurs but whether anyone recorded what was traded away.
In most organisations nobody did, because the loss happens at an organisational seam where the people on each side are doing their jobs correctly. Finance states a margin. Delivery states a budget and a date. The conversion between them is performed once, silently, by whoever wrote the project brief — and from that point on the enterprise is executing a strategy denominated in a unit its board never chose.
The remedy costs an hour and a sentence. Write down the exchange rate, name its owner, and put one measure at the bottom of the cascade in the unit at the top. The alternative is an organisation that hits every target it set and wonders why the number that mattered did not move.
The second half of this problem is the reverse journey — what delivery learns that ought to change the strategy, and why almost nothing is built to carry it upward. That is the subject of [Related article: What Your Projects Know That Your Strategy Doesn't].
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.