Does this create enough value to sustain itself?
Follow the value created and the capacity required to keep creating it.
StratOS · the method
A way to locate the next responsible commitment.
StratOS separates the question being asked, the level where the system operates, and the place where proof lives. Build it with me one question at a time—by the third step you will have assembled the whole model yourself, and know exactly what each part is for.
01 · Start with the question
Three questions define the decision.
What are we really asking? Every enterprise decision protects one of three conditions the organization needs to keep moving. Name which, and the rest of the method has somewhere to stand.
Can the organization deliver what it is committing to?
Match conviction and release velocity to evidence, controls, and reversibility.
Can the organization keep adapting as conditions change?
Balance what the organization knows how to run with what it needs to create next.
3 questionsthe axis we will multiply
02 · Add altitude
Ask each question at two altitudes.
At what level of the machine? Architecture is the machine you are building; mechanics is that machine as it runs. The same question answered at both keeps the design honest about delivery.
What machine are we building?
Where is the running machine succeeding or failing?
Where the spread comes from / what sustaining it costs
Does advantage come from assets the company controls or interactions it enables?
Is the company preserving the capacity that produces value, and does that capacity realize a durable return?
When to lock an answer / when to ship it
When should the company impose a clear answer, and when keep the problem open?
What must be assured inside the company, and what is ready to be released into the environment?
Making the new / running the known
Does renewal come from deepening what the company knows, or creating what the market has not seen?
Does output come from applied effort or from systems that remove the need for it?
3 questions × 2 altitudes = 6 tensionseach question, at architecture and at mechanics
03 · Add locus
Split each tension by where its proof lives.
Where does the proof live? One pole is proven by evidence inside the enterprise—the condition it needs in order to act. The other is proven at the boundary and beyond—the consequence it actually caused. Every tension now has two poles.
Protects the institutional condition required to act.
Protects the realized consequence of action.
Where the spread comes from / what sustaining it costs
Controlled value chainOrchestrated ecosystem
Workforce capacityCapital return
When to lock an answer / when to ship it
Structured convictionOpen inquiry
Risk frictionRelease
Making the new / running the known
Codified fluencyNovel offering creation
Execution disciplineSystems and flow
3 questions × 2 altitudes × 2 loci = 12 polesyou built the model—now we can read it
04 · Read the divergence
The disagreement is the signal.
Where do the signals disagree? A strong aggregate can sit directly above a strained operating condition. Divergence keeps both poles visible—so a headline result cannot hide the capacity, control, or consequence it depends on. This is the Klarna move, generalized.
The aggregate result, adoption, speed, or return.
The capacity, control, quality, and exception path underneath it.
05 · Locate the intervention
Move at the level that owns the condition.
At what level do you intervene? Divergence identifies what needs attention. L1–L5 identifies where the organization can govern it, from the original intent through the evidence of what occurred.
- L1Strategy
What are we trying to accomplish?
- L2Business case
What must be true before we commit?
- L3Implementation
What must be true before we launch?
- L4Operations
What must remain true while we run?
- L5Audit
Did the claimed outcome occur?
Return to accountability
Did we get what we said we wanted?
The method ends where the commitment began: with the declared objective. The next move is sized to the evidence, given a clearing condition, and revisited as the operating system changes.