RecalibrateGovernancePlatform-enabled

Assumption Recalibration

The continuous governance of the assumption register — monitoring divergence, acting on triggers, and regenerating affected models before the strategy quietly becomes fiction.

Which assumptions have moved, which have breached their thresholds, and what must regenerate in response?
Why this matters

Calibration built the register; this method keeps it true. Every strategy decays through its assumptions — attendance drifts, growth deviates, policies change — and the decay is invisible until something built on a dead assumption fails publicly. This is the standing discipline: divergence monitored against thresholds, breaches convened rather than discovered, affected models regenerated through governance. The smallest method in the library, and the one that determines whether everything else stays alive.

When to use it
  • Continuously via monitoring, with quarterly governance review
  • Immediately on trigger breach: threshold crossings convene, they do not wait for the calendar
  • At every organisational event with registered-assumption relevance
Who should participate
  • Named assumption owners — the accountability structure Calibration created, now operating
  • The decision-environment's operational owner
  • Leadership team for breach decisions above operational scale
  • Strategist judging regeneration scope
Inputs
  • The live register: sources, confidence grades, owners, thresholds
  • Continuous evidence streams mapped to monitorable assumptions
  • Owner attestations for non-monitorable assumptions
  • Model-linkage map: which models each assumption drives
What happens
  1. Monitor continuously where streams permit: attendance against presence assumptions, headcount against growth, realisation against booking — divergence computed against thresholds, not impressions.
  2. Attest periodically where they don't: owners confirm or revise non-monitorable assumptions each cycle; unattested is flagged, not presumed.
  3. Classify movements: within-tolerance (logged), approaching-threshold (owner alerted), breached (convened).
  4. On breach, convene rather than patch: revise the assumption and regenerate affected models, hold it and intervene on reality (a policy enforced), or escalate to scenario level where the breach invalidates the chosen future.
  5. Regenerate through the protocol: models rebuilt, routed through governance for acceptance, decision history updated.
  6. Audit the register annually: retire, add, re-grade — it must describe the strategy the organisation currently runs.
What to look for
  • Breaches tolerated because regeneration feels like admitting error — divergence tolerated is strategy repealed silently
  • Compound approach: multiple assumptions drifting simultaneously — individually tolerable, jointly a scenario question
  • Owner decay: attestations becoming rubber stamps
  • Reality-intervention overuse: repeatedly enforcing assumptions against persistent reality instead of revising them
  • Regenerations bypassing governance under time pressure
Outputs
  • Divergence monitoring record with classifications
  • Breach decisions with reasoning: revise, intervene or escalate
  • Regenerated models accepted through governance
  • Annually audited register
  • Escalations to the Workplace Strategy Refresh where breach scale demands
How the output is used

This is the trigger mechanism for everything regenerable: ratio revisions, stack regenerations, kit updates and scenario re-selections initiate here. When breaches accumulate past structural tolerance, this method fires the Refresh — the register knowing before anyone else that the foundations have moved.

Human judgement required

The platform detects divergence; every breach response is a decision. Revising concedes a forecast; intervening asserts a policy; escalating admits the chosen future may be wrong. Judging which fits, and resisting the pressure to tolerate drift, is governance character more than analytical skill.

Common mistakes
  • Building the register in Define and never operating it
  • Setting thresholds and ignoring breaches
  • Treating every breach as regeneration when some are policy failures needing enforcement
  • Missing compound risk by reviewing assumptions individually
  • Letting the register ossify
Practical example

A media company's register flagged attendance approaching its +8-point threshold in month nine, breaching in month fourteen. The convened decision weighed both responses; evidence showed the rise was structural — a new client-delivery model — not policy drift. The assumption was revised, capacity and ratio models regenerated in four days, and a floor scheduled for sublease was retained. The sublease, six weeks from signature, would have been the public failure the register pre-empted.

45 methods in the library.