The method

A better decision starts before the meeting.

Strategical gives consequential decisions a structured path: clarify the question, assemble the right stakeholder perspectives, pressure-test the assumptions, surface what needs evidence, and capture the conditions for action.

01
Explore
Understand the territory when the question is still forming.
02
Frame
State the decision, the stakes, and the evidence already in hand.
03
Pressure-test
Let accountable perspectives challenge it and each other.
04
Decide
Name the conditions, the dissent, and what is still missing.
05
Capture
Leave with a Decision Brief leadership can revisit.
↳ New evidence / new questions→ explore again
Start with the right kind of problem

Not every question is ready for a decision.

Two entry points. Which one you need depends on whether the decision exists yet.

Path A — the territory is fuzzy

Field Study

Use Field Study when the team is still trying to understand the shape of the problem — and again later, when new evidence, market signals, or strategic questions emerge.

Field Study can be revisited whenever new questions emerge—helping surface the next consequential decision worth testing.

What is changing
Where the tension is
What customers or stakeholders may care about
What assumptions are shaping the discussion
Which decisions are actually emerging
You leave with
Field Notes
InsightsTensionsBlind spotsCandidate decisions
Path B — the decision is defined

Pressure Test

Use Pressure Test when there is a clear choice or proposed action on the table.

Launch or delay
Enter or stay out
Increase price or hold
Build or partner
Centralize or decentralize
Reposition or maintain course
You leave with
Decision Brief
RecommendationStrongest dissentConditionsEvidence still missing
Field Study→Candidate decision→Pressure TestA Field Study generates the decisions worth pressure-testing.
Frame the decision

A vague question produces a vague challenge.

The room needs enough context to challenge the decision rigorously without treating assumptions as facts. Three inputs are required. Four more make the challenge sharper.

Required
The decision
The stakes
Evidence already available
Recommended
Current lean
Alternatives
Success criteria
What would change your mind
Decision contextIllustrative Pressure Test example
Decision
Should we increase enterprise pricing 12% next quarter?
Stakes
Margin improvement against renewal and expansion risk.
Evidence
Renewal cohorts, churn history, competitive pricing, customer feedback.
Current lean
Increase pricing, but timing and rollout remain unresolved.
Alternatives on the table
Hold price and raise at renewal; increase 6% now and 6% next year; increase only in two segments.
Success criteria
Net revenue retention holds above target; no more than two enterprise accounts lost to price.
What would change our mind
Evidence that a material share of in-flight expansion revenue re-opens on announcement.
Build the right room

Challenge the decision from the accountabilities that matter.

Stakeholders are selected around who the decision actually affects. The point is not diversity of titles. It is different reasons to support, oppose, or condition the decision.

FinanceSalesOperationsCustomerChannelProductLegalRegional leadershipProcurementExecutive leadership
Mandate
What this stakeholder is accountable for.
Incentives
What success looks like from their seat.
Evidence threshold
What they require before supporting the decision.
Role boundary
What they will not compromise on.
Current stance
SupportiveConditionalOpposedUndecided
Decide what the room should know

Give each stakeholder only the context they would realistically have.

Company-aware

Use when the stakeholder would genuinely know your business.

Strategy
History
Operating realities
Prior decisions
Customer context
Commitments
Internal constraints
Independent — no company context

Use when you want a first encounter with the offer, concept, or argument.

Prospects
Unfamiliar buyers
Outside stakeholders
First-impression reactions
External decision-makers
Realism improves when the simulation does not know more than the real stakeholder would.
Pressure-test the decision

Now let the disagreement do the work.

This is not brainstorming. Each stakeholder holds a position they can defend, and the session moves through challenge, dissent, evidence, and conditions.

01
Stakeholders form independent positions before hearing each other.
02
Each challenges the decision from its own accountability.
03
They respond to you — and then to one another.
04
Evidence gets requested, by name and by segment.
05
Assumptions get separated from what is actually known.
06
Conditions emerge: what must be true to proceed.
07
Stances hold under pressure unless something material changes.
08
When a position moves, the reason it moved is recorded.
ChallengeDissentEvidenceConditionsStanceChange reasonSee the room in action →
Track what changes

The important signal is not what people said. It’s what moved.

The Decision Board holds the evolving decision state while the conversation moves, so the session ends with a position on every open item rather than a transcript.

Tracked continuously through the session
Stakeholder stance
Supportive, conditional, opposed, undecided — per accountability.
Strongest objection
The dissent most likely to prove correct.
Evidence gaps
What the decision currently rests on without proof.
Assumptions
Stated plainly, and separated from evidence.
Open conditions
What must be true before the decision can proceed.
Unresolved questions
Questions worth putting to real stakeholders.
Evidence confidence
How strong the basis is, not how strong the opinion is.
What changed a position
The argument or evidence that moved a stakeholder, named.
Before and after the session· illustrative Pressure Test example

End with explicit conditions, not vague alignment.

The session opens with what the team believes and closes with what it can defend. Compare the two states to see whether the decision actually became clearer.

What the team brought in · illustrative example
Current lean
Increase pricing, but timing and rollout remain unresolved.
Assumptions
Customers will absorb the increase; competitors are moving too.
Expected risks
Some churn at the low end of the enterprise book.
Success criteria
Net revenue retention holds; margin improves this year.
What would change the decision
Not yet defined.
What the team can defend · illustrative exampleProceed with conditionsThe lean survived. The timing did not.
Recommendation
Hold the increase one quarter and announce after the renewal window.
Strongest dissent
A third of in-flight expansion revenue re-opens on announcement.
Conditions for proceeding
One rollout with identical terms; a stated value narrative before customer notice.
Evidence still missing
Segment-level price sensitivity; the in-quarter renewal cohort.
Decision readiness
02 / 03 · evidence pending
Next action
Sensitivity analysis by segment, with the exposed-account list, before the pricing memo goes out.
What changed
The increase itself was never the contested part. Sequencing became the decision, one stakeholder moved from supportive to conditional on rollout consistency, and "what would change our mind" went from undefined to a named threshold.
Produce a durable artifact

The meeting ends. The decision work does not.

Field Study output
Field Notes
What the territory contains
Themes
Tensions
Insights
What the team is not seeing
Blind spots
Where it leads next
Candidate decisions
Recommended follow-up
Pressure Test output
Decision Brief
The call
Recommendation
Stakeholder signals
Strongest dissent
What it rests on
Evidence confidence
Assumptions
Risks
Terms of proceeding
Conditions
Unresolved questions
What happens after
Required actions
Monitoring criteria
What would change the recommendation
The Decision Brief is what leadership comes back to when the question returns.
Revisit when the evidence changes

A good decision can change when the evidence changes.

Strategical is not a verdict machine. A decision is re-opened when the basis underneath it moves — which is what makes this a practice rather than an event.

The same decision can be revisited as evidence arrives, conditions are met, or assumptions break—without rebuilding the reasoning from scratch.

New evidence can also create new questions. Field Study gives teams a structured way to explore those questions and identify the next decision worth pressure-testing.

New customer evidence arrives
Financial assumptions change
Market conditions move
A pilot finishes
A stakeholder condition is met
A risk becomes real
Confidence changes materially
Where judgment stays

Strategical strengthens the decision. Leadership still owns it.

Strategical provides
Decision framing
Simulated stakeholder challenge
Structured dissent
Evidence-gap identification
Synthesis
Durable artifacts
Decision discipline
Leadership provides
Real-world context
Judgment
Accountability
Primary evidence where required
Final decision authority

Bring one decision. Leave knowing what still has to be true.

Start with a consequential decision or an unresolved strategic territory. Strategical will help determine whether to explore it first or pressure-test it directly.

Common questions

How the challenge works in practice

Do all stakeholders see the same information?
Can a stakeholder change position during a Pressure Test?