Hypothesis-Driven Problem Solving

Learning objectives

By the end you can:

1. Explain, from first principles, why hypothesis-first problem solving reaches better answers faster than exhaustive research-first approaches on a fixed-time, fixed-budget engagement, and state the module's core discipline in one sentence.
2. Form a testable, falsifiable day-one hypothesis from limited information (a client conversation, pattern-matching against analogous situations, a quick first data pull, or an industry base rate), and state its kill criterion before you analyze anything.
3. Distinguish a driver tree from an issue tree, build both additive and multiplicative driver trees for a given metric, and know which form applies to which kind of decomposition.
4. Decompose a period-over-period change in a driver-tree metric into a full three-term bridge (a base-price/base-volume effect, an incremental effect, and an interaction/mix term) by hand, verify that the three terms reconcile exactly to the actual change, and correctly interpret the interaction term's sign.
5. Design the minimum killing analysis for a hypothesis: rank candidate analyses by directness and cost/time, and choose the cheapest test that could kill the hypothesis first, before reaching for anything slower or more elaborate.
6. Produce and defend a one-day answer (a current, dated, falsifiable best-answer stated in one sentence with an explicit confidence level) and update it as evidence arrives, without treating it as either a final verdict or an excuse to withhold judgment.
7. Build a ghost deck: reverse-engineer a lean workplan from a hypothesized answer, and apply the guardrails that keep it a private planning tool rather than a source of anchoring bias.
8. Recognize the symptoms and root causes of boiling the ocean, and apply the four-tool discipline (hypothesis, driver tree, minimum killing analysis, ghost deck) as the standing defense against it.
9. (Productivity objective.) Use an AI assistant to accelerate drafting a first-pass hypothesis list, driver tree, or ghost-deck skeleton, while keeping the prioritization, the kill-test judgment, and every final number your own, verified against a primary or client source. AI proposes; you dispose.

Prerequisites & connections

Builds on. CN1.01 (Issue Trees & MECE) is the direct foundation: the issue tree maps every possible explanation for a problem, built MECE. This module teaches what to do with that map, bet on which region holds the answer, and test it fast. Read CN1.01 first if you have not. CN0.01 (The Consulting Mind) supplies the six-stage engagement cycle (define → structure → prioritize → analyze → synthesize → recommend) this module lives inside, at the prioritize-and-analyze stages, plus the galaxy's honest-scope framing. If you have already run E11.03 (The Consulting Case-Interview Lab), the Cycle-2 taster, its learning objective on hypothesis-first structuring gave you a compressed, interview-length version of this discipline; this module is the deep, MBB-partner-depth expansion of that one line: real bridge mathematics with the interaction/mix trap made explicit, the ghost deck, the one-day-answer rhythm, and a diagnosis of why teams boil the ocean, not a repeat of the taster. From the Finance galaxy: M4.01/M4.02 (business-model anatomy and unit economics) supply the vocabulary your driver trees decompose into; M5.01–M5.10's seventeen sector playbooks are where the industry base rates that make a hypothesis credible rather than arbitrary actually live. Cross-link them; this module does not re-teach sector economics.

Feeds forward. CN1.03 (The "So What": Synthesis & the Answer-First Storyline) takes the hypothesis you have confirmed, refined, or replaced (plus its evidence) and turns it into Minto's governing-thought → key-line → support pyramid (M10.03 teaches Minto's Pyramid Principle in full). This module deliberately stops at "a validated point of view with evidence," never a polished client storyline, a hand-off stated explicitly wherever the two could be confused (the one-day answer and ghost deck are private working tools, not client-ready output). CN2.01–CN2.04 (casing) reuse this entire cycle under a stopwatch, a case interview is this discipline compressed to thirty minutes; the module's mapped Case-Engine case (named in the Mastery check) is a profitability case built on the same bridge logic. CN3.03 deepens the diagnose-before-prescribe stance this module opens with, citing Rumelt directly. CN5.01/CN5.03 apply the identical method to due diligence, where the hypothesis is a deal thesis and the kill test is a piece of commercial due diligence. CN6.01 hypothesizes about deal value the same way this module hypothesizes about a metric's movement. CN7.03 (Partner Capstone) requires you to run this entire cycle, unaided, under time, on a company you have never seen.