Issue Tree and Hypothesis Workplan
Excel workbook for hypothesis-driven problem solving: build an issue tree, prioritize hypotheses, plan analyses and log evidence, with structure checks built in.
FreeFree Excel workbook. Excel workbook for hypothesis-driven problem solving: build an issue tree, prioritize hypotheses, plan analyses and log evidence, with structure checks built in. Download it, add your project details and use it today: no sign-up for software, no paywall.
Hypothesis-driven problem solving is the core discipline of management consulting, but issue trees often live on a whiteboard photo that nobody updates. This workbook turns the method into a working tool. Break a key question into a structured issue tree with parent checks, attach testable hypotheses with impact and effort, and get a priority score for each. Plan the analyses that will prove or disprove them, track due dates and overdue work, and log every piece of evidence as supporting or refuting. The Summary shows which branches still lack hypotheses and where the evidence points. Built for consultants, strategy and transformation teams, and anyone running a structured diagnostic.
What's inside
- Issue Tree: One row per node. Parent and child counts check the structure. Example is illustrative.
- Hypotheses: Testable hypotheses linked to tree nodes. Priority = impact x ease (1-9).
- Workplan: Analyses and tasks that test the hypotheses, with working days and overdue tracking.
- Evidence Log: Every finding, linked to a hypothesis, marked as supporting or refuting.
- Summary: key numbers calculated automatically from your data
- Drop-down lists, worked example rows and formulas you can rely on
How to use it
- Write one key question on 'Issue Tree' as node I-0 at level 'Key question'. Make it specific, time-bound and owned by a decision maker.
- Break the question into Level 1 branches that are mutually exclusive and collectively exhaustive (MECE). Note in 'How this branch is split' the logic you used, for example price x volume x mix, or internal versus external causes.
- Continue to Level 2 and Level 3 until each leaf can be answered with a specific analysis. The Parent check flags any node whose parent ID does not exist.
- On 'Hypotheses', write a falsifiable statement for each important leaf, the evidence that would prove or disprove it, and the data source. Rate impact if true and effort to test; the priority score (1-9) favors high impact, low effort.
- On 'Workplan', schedule the analyses for the top-priority hypotheses first. Keep tasks to a few working days each so progress is visible.
- Log every interview, data cut or document finding on 'Evidence Log', marked as supporting, refuting or neutral, with its strength. Update the hypothesis status when the weight of evidence is clear.
- Use the Summary in team problem-solving sessions to spot leaves without hypotheses, overdue analyses and refuted hypotheses that should change the storyline.
Who it's for
Aspiring and practicing management consultants, internal strategy teams and leaders who need to drive decisions.
Let's connect
I'm Pranshu Shubham, a Microsoft Dynamics 365 F&O Solution Architect and PMP-certified program lead with 8+ years of ERP and AI transformation across the USA, Europe and APAC. I created this resource from real project experience, and I'd love to hear how you use it.
- Connect with me on LinkedIn and tell me what you're working on
- Have a question or a project in mind? Send me a message. I reply within 24 hours
- Explore more free e-books, templates and videos and the latest articles