A strategy that only survives predictable conditions is not a strategy — it is a forecast. The mechanics are what make a strategy respond to costs, staff, and market moves without unwinding the plan.
How do you adjust pricing, sequencing, and structure when costs shift, staff change, or market conditions move?
The reversal
The dominant view treats strategy as a plan revisited annually. Cross-industry research on resilient performance1 shows the businesses that compound through cost shocks and demand swings do not revisit strategy annually; they operate a live mechanic layer between strategy and execution. That layer decides how prices move when input costs shift, how sequencing changes when staff turn over, and how structure adjusts when a market segment moves. Without the mechanics layer, every shock triggers a strategy debate; with it, most shocks trigger a pre-defined response and the strategy debate is reserved for the moves that actually deserve one.
The insight stack
What actually moves the P&L
Pre-authorise pricing responses to cost shifts
Pricing decisions that wait for executive review are pricing decisions that arrive late. Pre-authorise the range and shape of pricing responses to defined cost shifts — 'if input cost X rises by more than 8%, price on segment A rises by 3–5% within thirty days, on segment B by 1–2%, on segment C not at all' — and delegate the execution to a named owner with a written rulebook. Board debate is reserved for shifts outside the pre-authorised bands.
Design staffing mechanics around role continuity, not headcount
Staff changes are a continuous condition, not an event. Design mechanics around role continuity: every critical role has a documented handover, a named cover, and a defined ramp for a full replacement. The mechanic is triggered automatically when a resignation lands — no bespoke response, no strategic pause. Businesses with role-continuity mechanics report significantly lower productivity loss per transition than those that treat each departure as unique2.
Sequence major bets against explicit trigger conditions, not calendar dates
'Launch in Q3' is a calendar promise. 'Launch when the pipeline covers three months of forecast revenue and the operations team has cleared the current backlog' is a trigger promise. Trigger promises absorb shocks; calendar promises transmit them. Every major bet in the plan should carry the specific market or operational condition under which it launches, delays, or accelerates.
Instal a monthly mechanics review, not just a quarterly strategy review
Strategy reviews debate the plan. Mechanics reviews audit the responses: which pre-authorised triggers fired, did the response happen inside the defined window, did the outcome match the pre-modelled band? Monthly cadence is enough to catch drift; less than monthly, mechanics quietly stop firing and the business reverts to bespoke reaction.
Reserve strategic reset for a small number of pre-defined conditions
Not every shock deserves a strategy debate; most deserve a mechanic. But a small number of conditions — sustained margin compression beyond a threshold, structural competitor entry, regulatory reset — do warrant a full strategy reset. Pre-defining those conditions in writing protects the mechanics layer from being over-ridden by anxiety, and protects strategy debate from being wasted on shocks the mechanics were built to absorb.
Case example
A £26M consumer goods business absorbing an input-cost spike
The problem: a 24% spike in a critical input cost needed to be absorbed within one quarter, without triggering a company-wide re-plan and without losing the largest three customers. The business had no pre-authorised pricing mechanic; every previous cost spike had triggered a full board debate and a delayed, blunt across-the-board price increase that damaged the top of the customer curve. A mechanics layer was installed: segment-differentiated price bands (top-3 customers held for one quarter with cost recovered through spec-simplification; mid-tier priced up 5%; long-tail priced up 8%), a role-continuity mechanic for the commercial team executing the change, and a monthly mechanics review to verify the response was landing inside the pre-modelled band. Six months later, gross margin had held within 40 basis points of pre-spike level, the top-three customers had renewed at full spec, and the mid-tier attrition had run at 3% against a modelled 8%.
Mini-playbook
Five mechanics to install between strategy and execution
Pre-authorise pricing responses to defined cost shifts, delegated to a named owner.
Design role-continuity mechanics: documented handovers, named cover, defined ramp.
Sequence major bets on trigger conditions, not calendar dates.
Run a monthly mechanics review distinct from the quarterly strategy review.
Pre-define the small number of conditions that warrant a full strategy reset.
How Strategy Labs installs this
Anchored to Market & Competitive Positioning
Strategy Labs installs the mechanics layer inside CAE as a bridge between the strategy artefact and the operating cadence — with pre-authorised triggers, delegated owners, and audit trails built into the engagement lifecycle. The mechanics layer is a first-class deliverable, not a project-management afterthought.
Cost-shift modelling, price-elasticity mapping, and role-continuity benchmarking run in PDC, so the mechanics are calibrated against primary data — not against generic industry rules of thumb.
Frequently asked
Related questions executives ask
- How is a mechanics layer different from a business continuity plan?
- A continuity plan protects against catastrophic disruption; a mechanics layer optimises the routine shocks that never make it into a continuity plan. Both matter; only the mechanics layer runs monthly.
- How many pre-authorised mechanics is enough?
- Fewer than most executives think. Ten to fifteen well-designed mechanics — covering pricing, staffing, sequencing, supply, and cash — absorb the majority of monthly shocks in most mid-market businesses. Beyond twenty, the layer starts to compete with the strategic debate it was designed to protect.
- Who owns the mechanics layer?
- The COO or operating chief owns the layer; the CFO co-owns pricing mechanics; role-continuity mechanics sit with the people leader. The CEO owns the pre-defined reset conditions.
Over to you
When your last input-cost or staff shock hit, how long did the executive team spend in debate — and how much of that debate could a pre-authorised mechanic have removed entirely?
Continue reading
More Strategic Growth briefings
When is a growth business actually ready for growth capital?
Most scale-ups raise growth capital to prove product-market fit. The compounders raise after they have already proven it — and use the money to buy speed, not survival.
Read briefingWhy is pricing the highest-ROI decision most executive teams underinvest in?
A 1% improvement in captured price flows to operating profit at close to 100%. A 1% improvement in variable cost or volume never does. Yet pricing sits in a spreadsheet the CEO has not opened in nine months.
Read briefingHow should a growth business decide what to defund?
Every growth portfolio has a hidden liability: the initiatives that stopped compounding two years ago but still consume executive attention. Defunding is the highest-leverage capital-allocation decision most boards never make.
Read briefing
Discussion
(…)Comments are moderated before appearing. Your email is only used for moderation and is never shown publicly.
Loading discussion…