Strategic Volatility · Primary
Every quarter starts over. Nothing compounds.
How this principle feeds it
correction arrives as abrupt reprioritization in place of deliberate change.
Principles Library / Evidence over assumption
Evidence-Based Decisions Reduce Assumption Risk
Base important decisions on observed evidence rather than untested assumptions, prediction, opinion, or authority.
Assumptions are unavoidable, but risk grows when they go untested, when evidence cannot reach decisions before they are locked in, or when a definition of value is allowed to outlive the conditions that created it. Change is not a planning failure. It is evidence that learning has occurred.
Wrong assumptions show up before they're locked into decisions.
Plans adjust as evidence arrives, so change doesn't turn into a disruption.
Each learning cycle ends in a real adjustment, so teams stay engaged in it.
Every quarter starts over. Nothing compounds.
correction arrives as abrupt reprioritization in place of deliberate change.
Delivery is consistent. Value is not landing.
untested beliefs about customer value replace current evidence of it.
We know what happened. Nobody can explain why.
a confident narrative stands in for reasoning that can be traced to evidence.
Customers find defects before the team does.
reviews that change no decision let the same problems repeat, which shows up partly as recurring defects.
The team built exactly what was asked. It is no longer what is needed.
governing intent stays fixed after it stops being valid.
Problems are found at release, not before it.
work accumulates before evidence validates it, so corrections expose everything at once.
Every team hits its targets. The product still misses.
teams keep optimizing measures whose link to outcomes went unchecked, which can fragment end-to-end value.
AI signs are on by default. Use the AI switch to exclude them.
For each consequence: Not seen / Sometimes / Persistently / Not sure.
Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.
Strategic Volatility: Every quarter starts over. Nothing compounds.
Customer Disconnect: Delivery is consistent. Value is not landing.
Attribution Failure: We know what happened. Nobody can explain why.
Quality Fragility: Customers find defects before the team does.
Intent Drift: The team built exactly what was asked. It is no longer what is needed.
Batch Amplification: Problems are found at release, not before it.
Local Optimization Bias: Every team hits its targets. The product still misses.
What else have you observed? Optional. Shared only if you choose to start coaching.
Start a Diagnosis session: review and edit a draft containing your note, conditions you recognized in Step 3 (including whether they match partly), warning signs and consequence ratings before sending it. No scores or principle files are sent.
Showing all 6 practices. Answer the Diagnose questions and the most relevant come first.
Decide which decisions genuinely need empirical evidence, and write down the assumptions underneath them.
Start by asking your team: What are we assuming, and what evidence would change our mind?
Decisions rest on evidence, and data that contradicts the current view actually gets weighed.
Build feedback loops that reach decisions before they're locked in. Watch for drift or regression as execution speeds up.
Start by asking your team: Which decisions need new evidence before we revisit them, and which have gone too long without it?
Learning happens during delivery, while decisions can still change.
Hold a fixed learning cadence that delivery pressure can't cancel. Each cycle should produce a real adjustment, and a status update doesn't count.
Start by asking your team: Where is learning protected in our cadence, and what happens if that protection goes?
Reviews happen on schedule even under pressure, and each one changes something.
Judge each decision by the outcomes you observed, whatever the original intent was.
Start by asking your team: What are we observing right now, and what are we only predicting?
Metrics change decisions, and shipped features show real impact.
Treat plans, backlogs and roadmaps as hypotheses. Revalidate them as conditions change, and deprioritize work whose expected value no longer holds.
Start by asking your team: Would we still choose this priority if we were deciding today?
Roadmaps change when conditions do, without a fight over justification.
Set a human checkpoint that compares AI predictions and agent behavior with real outcomes. Feed what it finds into agent configuration and policy.
Start by asking your team: As AI executes faster, are our feedback and evaluation loops keeping pace?
People check AI outputs against what they observe, and outcome feedback reaches agent configuration.