Execute
The morning after the room. One decision becomes priorities, owners and measures that reach every team, and stays honest as the quarter moves under it.
The call the room made hangs above everything under it. Each level below carries its own owner and its own measure, so nobody has to work out which version of the plan is current or where they fit in it.
Because the room decided
Wholesale is the growth engine for 2026
Two-day fulfilment on the Halifax line
Operations · measured on time to ship
One of three things your team owns off this decision.
Decided in the room, 14:20
Wholesale is the growth engine for 2026
Corporate priority
Sign three regional roasters
On trackTeam actions under it
Two-day fulfilment on the Halifax line
At riskRetire the DTC subscription
On trackTrade pricing for volume tiers
Needs an ownerEvery line traces back to the decision it came from.
No shared drive, no v12_final_final, no working out which document is current.
Anything without one shows as needing an owner rather than quietly reading as fine.
The cascade walks parent to child, so it reaches the level that actually does the work.
Each measure is read as pace against projection, so a number that is fine today but will not land in March says so in October. What reaches you is only the part that needs you.
Time to ship
Wholesale revenue
Churn
Move the needle today
Time to ship will miss by three weeks
Halifax line · one proposal waiting
Trade pricing for volume tiers has no owner
Finance · margin floor
Recently resolved
Petra moved the DTC retirement to March
Inside her own slack, nothing to do
Nothing routine ever lands here. Only drift, overdue and things blocking somebody else.
The dashes are where the number is heading, not where it is.
On track, at risk or off track is read from where the line is heading, not from the last update.
Routine cadence never reaches this surface, so a full list means something is genuinely wrong.
Who can see a measure follows the owner, the team and the manager chain, never the whole org.
When a measure will not land, the engine works out what it would take and proposes one move. It shows what it ruled out and why. Nothing is ever applied without somebody clicking it.
WHAT MOVED
Time to ship
At riskThree check-ins in a row came in under pace. The engine reads the trend, not the single miss.
Retime · stretch
Move two-day fulfilment on the Halifax line to 31 March
Holding the current date needs eleven more shifts than Operations has. Stretching by six weeks puts wholesale revenue back inside its own window.
WHAT IT RULED OUT
There is no auto-apply path. Every move waits for a human click.
It names the measure that is stalled and one recommended move, instead of inventing busywork.
The moves it considered and rejected come with the proposal, so you can disagree with the reasoning.
The prior dates travel with the proposal, so undoing never depends on what has been edited since.
Everything the engine can propose. Each one arrives as a pending proposal with its reasoning attached, and each one waits for a person.
Not a document somebody has to go and find, and not four versions of it. One plan that every team can see their part of, and that tells you when it is going wrong while there is still time to do something.