The Discipline Before the First Solution
Question Zero, for executive leadership
The Premise
Most transformations do not fail because of technology. They fail because the underlying problem was never defined.
Organizations commit — resources, architecture, attention — while the problem is still a perception. Velocity increases. Direction does not.
Money spent before definition buys speed, not direction.
Question Zero is the question before the first solution: is there a real problem — and what kind of problem is it? This brief outlines the discipline.
The Error of the Third Kind
Systems science has a name for the failure mode this brief exists to prevent: the error of the third kind — the right answer to the wrong problem.
It begins quietly. Every project starts counting at question one — how do we solve it? — and the solution language arrives before the problem language:
Which model should we buy?
Which vendor do we choose?
How fast can we deploy?
What will it cost?
None of these are wrong. They are questions one and two, asked before question zero. The stated problem is still a perception — often repeated because someone said it early. Organizations, like individuals, take perception for reality.
What the Question Changes
Is there a real problem — and what kind of problem is it?
The kind decides everything. A systems constraint answers to architecture. A governance gap cannot be automated away. A leadership clarity issue does not yield to a new platform. Misaligned incentives outlast every tool bought to fix them.
Until the constraint is defined, effort amplifies misalignment. And some problems, once defined, dissolve — nothing needs to be built.
The Discipline
A Question Zero is a fixed-scope run of the method on one decision — one to three weeks, four movements.
The System — whose problem is this, and what system does it live in? Stakeholders mapped, decision ownership made explicit.
The Evidence — every claim sorted: observation, evidence, assumption, interpretation. What is known, what is felt, what is repeated.
The Convergence — the constraint map: is there a real problem, and what kind? Constraints separated from symptoms.
The Decision Architecture — what to decide, in what order, and what not to do, delivered as an executive briefing.
The center of gravity is the evidence sort: no conclusion is allowed to stand on an ungraded claim.
Provenance
The method was born in 2006 as Fråga Noll — carried from Cranfield's Systems Engineering for Defence into the Swedish Armed Forces Headquarters, where the same discipline governed national materiel decisions: no development begins before the objectives are defined.
It was proven at its sharpest in the JAS 39 Gripen E/F program — environments where an undefined problem costs more than money.
Twenty years of live use. The name is the method.
The Engagement
A Question Zero is commissioned on one decision: fixed fee, one to three weeks, ending in a decision architecture — delivered as an executive briefing.
One outcome is always allowed: there is no real problem here — do not spend. That answer alone can be worth the fee many times over.
Where a real problem exists, the change is carried by your own organization — advised, structured, supported. Change owned from within lands.
Clarity before solution.
Definition before transformation.
Governance before automation.
Prepared for executive leadership facing transformation decisions.