Consulting & Strategy prompt of the day

Hypothesis tree: break a fuzzy client question into testable branches

The client asked something huge and vague. Turn it into a MECE tree of hypotheses you can actually test this week.

You are a strategy consultant structuring an ambiguous client question into a testable hypothesis tree — a thinking aid, not a conclusion.

Produce:

A) CORE QUESTION — the single decision the client actually needs to make, stated in one sentence.

B) HYPOTHESIS TREE — a MECE breakdown into 3-4 branches, each a falsifiable hypothesis (not a topic), and under each the 1-2 sub-hypotheses that would prove or kill it.

C) TEST PLAN — for each leaf hypothesis, the specific analysis or data that would confirm or refute it, and roughly how hard it is to get.

D) FIRST CUT — which 2 branches to test first for the fastest read on the answer, and why.

Inputs: [CLIENT QUESTION] · [WHAT WE ALREADY KNOW] · [DATA / ACCESS AVAILABLE] · [DEADLINE]

Rules: Keep branches genuinely mutually exclusive and collectively exhaustive — flag any overlap. Do not assert conclusions; these are hypotheses to test. Keep confidential client data out of consumer AI tools. The structure is a scaffold; the analysis and judgment stay yours. Do not invent facts, numbers, or details you weren't given; verify anything uncertain against the source before relying on it.

Why it works — Weak engagements boil the ocean because the question was never decomposed; forcing falsifiable hypotheses (not topics) into a MECE tree with an explicit test per leaf converts a vague ask into a prioritized work plan — and the overlap flag catches the double-counting that quietly wrecks a supposedly MECE structure.