Assumption Testing¶
Diagnostic method — instantiates Dialectical Synthesis
Tests whether the conflict depends on hidden assumptions that can be revised, separated by context, or converted into conditional decision rules.
Assumption Testing treats the conflict itself as the suspect. Rather than expressing, mapping, or bargaining the two positions, it digs for the hidden assumption each side silently rests on, then checks whether that assumption is actually true — universally, sometimes, or not at all. The frequent and striking result is that the "unresolvable" tension turns out to be an artifact of a shared false premise: revise the premise and the conflict dissolves, or discover the premise holds only under certain conditions and the tension resolves into a simple conditional rule — if X, do the thesis; otherwise, the antithesis. Its object is the premise underneath the fight, not the positions on top of it, and a successful outcome may be that there was never a real tension at all.
Example¶
A fast-scaling company is deadlocked over whether to centralize or decentralize hiring. Recruiting leadership wants one central team for consistency and cost control; engineering directors want to run their own hiring for speed and fit. The debate has all the marks of a deep values tension.
Assumption Testing surfaces the premise both camps share without noticing: that hiring needs are roughly uniform across roles. Then it tests it — a quick pull of the last year's requisitions. The data is lopsided: high-volume, standardized roles (support, sales development) behave nothing like rare senior and specialist hires, which are slow, relationship-driven, and idiosyncratic. The shared assumption is simply false. The tension doesn't need a synthesis workshop or a negotiation; it dissolves into a conditional rule: centralize the high-volume, standardized pipelines; decentralize senior and specialist hiring to the teams. What looked like a philosophical war was a single untested premise, and testing it was the cheapest resolution available.
How it works¶
- List the load-bearing assumptions. For each side, name the premises such that if the premise were false, the position collapses.
- Rank by leverage. Test the assumption that most of the conflict hangs on first.
- Design a cheap test. A data pull, a small probe, a logical check — whatever cheaply establishes whether the premise holds.
- Route the result. If the assumption is false, the tension often dissolves; if it holds only sometimes, convert it into a context-conditional decision rule.
What distinguishes it from Adversarial Collaboration is its target: it probes the premise the whole conflict rests on, usually as a fast solo or analytic diagnostic, rather than running a jointly pre-committed study to decide which position is right.
Tuning parameters¶
- Assumption selection — which premise to test first; targeting the truly load-bearing one resolves the most conflict but requires judgment to identify it.
- Test rigor and cost — a five-minute logic check vs. a funded data study; more rigor buys confidence but spends time on what may be a non-issue.
- Falsification bar — how much evidence counts as "the assumption fails"; a strict bar avoids wishful dissolution but may leave a false premise standing.
- Conversion aggressiveness — how readily a sometimes-true assumption is turned into a conditional rule vs. tested further; quicker conversion is decisive but can over-simplify a real tension.
When it helps, and when it misleads¶
Its strength is that it is the cheapest possible resolution — a surprising number of "deep" tensions are artifacts of an untested shared premise, and surfacing that premise ends the fight without any elaborate synthesis. This is the discipline of Strategic Assumption Surfacing and Testing: aim the examination at the assumptions on which opposed strategic positions rest, not at their conclusions.[n1]
Its failure mode is testing the wrong assumption — a non-load-bearing one — and declaring victory while the real tension survives, or declaring a premise false on thin evidence because dissolving the conflict is convenient. It can also be misused to explain away a genuine tension an organization would rather not face, dressing avoidance as diagnosis. The guarding discipline is to target the assumption the conflict actually hangs on and to set the falsification bar before running the test, so the result is honest rather than motivated.
How it implements the components¶
Assumption Testing fills the diagnostic front of the archetype — probing whether the tension is even real before anyone builds a synthesis:
blind_spot_or_limit— its core act: it exposes the hidden assumption each side treats as given and shows where that premise breaks.level_or_context_distinction— when an assumption holds only under some conditions, it converts the tension into a context-conditional rule.synthesis_proposal— the conditional decision rule it yields (or the finding that no real tension remains) is the resolution it produces.
It does not run a jointly pre-committed empirical synthesis_test between opposing experts — that's Adversarial Collaboration; nor does it build the standing implementation_translation operating model that houses both needs — that's Both/And Strategy Design.
Related¶
- Instantiates: Dialectical Synthesis — Assumption Testing checks whether the tension is real and, when it isn't uniform, converts it into a conditional rule.
- Sibling mechanisms: Structured Debate · Adversarial Collaboration · Synthesis Workshop · Integrative Negotiation · Both/And Strategy Design · Thesis-Antithesis Mapping
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Tests whether the conflict depends on hidden assumptions that can be revised, separated by context, or converted into conditional decision rules, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Assumption Testing as 'Tests whether the conflict depends on hidden assumptions that can be revised, separated by context, or converted into conditional decision rules', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Strategic Assumption Surfacing and Testing was developed as a strategic-management method for exposing and dialectically challenging assumptions behind plans.
Related originating lineages:
- Philosophy — Critical inquiry supplies the demand that premises be surfaced and exposed to counterevidence.
- Psychology — Research on defensive reasoning and confirmation bias explains why assumptions remain tacit and resistant to challenge.
Review resolution: Mason and Mitroff's book presents Challenging Strategic Planning Assumptions as a managerial planning method centered on surfacing and testing assumptions. That named lineage resolves the primary domain in favor of organizational management, with philosophical critique and psychological defensive reasoning as material intellectual supports.
Attribution caveat: Its epistemic logic is philosophical, but the named method and its facilitated application originate in strategic management and organizational planning.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- Mason and Mitroff — Challenging Strategic Planning Assumptions
- Harvard Business Review — Double Loop Learning in Organizations
Notes¶
The most valuable outcome of Assumption Testing is often a non-synthesis: the discovery that the two sides were never really in conflict once a false shared premise was dropped. That makes it worth running early — before a debate, workshop, or negotiation is convened — because it can retire the tension at the lowest possible cost.
[n1] Strategic Assumption Surfacing and Testing (SAST) — Richard Mason and Ian Mitroff's method for exposing and examining the assumptions on which opposed strategic positions rest, so scrutiny targets the premises rather than the conclusions. It is the disciplined form of the move this mechanism makes on a stuck conflict. ↩