PromptSharp › Prompt Library › Consulting & Strategy › Hypothesis tree: break a fuzzy client question into testable branches
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.
The prompt — copy and run it
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 this prompt 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.
Want the daily version?
The PromptSharp Consulting Brief delivers prompts like this every day. Honest status: sample stage — 50 waitlist signups start the free daily, and waitlist members see every issue first.
Frequently asked
When should I use this prompt?
The client asked something huge and vague. Turn it into a MECE tree of hypotheses you can actually test this week.
Why does this prompt work?
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.
What mistake does this prompt help you avoid?
{'code': 'PF02', 'note': 'Boiling-the-ocean scoping — a falsifiable, overlap-checked MECE tree with a per-leaf test plan forces prioritization before analysis begins.'}
Related Consulting & Strategy prompts
Issue tree builder: from vague client ask to testable hypotheses
New engagement, vague problem statement. Build the issue tree and the week-one analysis plan before the team burns days boiling th…
Interview synthesis: 12 transcripts into findings your partner will sign
Two weeks of expert interviews sit in a folder. Get to defensible findings — with quote-level evidence — before the midpoint reado…
All Consulting & Strategy free prompts
The PromptSharp Consulting Brief page — five full free prompts plus the ladder status.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt each day, rotating across the roster. See what each vertical is like before you commit to one.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Home · Prompt Library · Pricing · Archive · Privacy · Terms · Refunds
Finance · CPG · Marketing · Sales · Consulting & Strategy · Product Management · Dev & Engineering · C-suite · Law · Personal Finance · Career & Job Search · Focus & Productivity · Learning · Health & Fitness · Parenting