Issue Trees and Problem Structuring

A sharp key question, MECE issue trees that can be tested, branches prioritised by value at stake, a living tree on real work and the weekly drills that make structuring fast and natural.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Issue Trees and Problem Structuring, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

202

Starter tasks

📋 Management Consulting

Issue Trees and Problem Structuring

Breaking a client problem into a MECE issue tree: the key question, branches that can be tested, prioritising and using the tree to plan the analysis.

  1. Key question written in one testable sentence
  2. Problem statement worksheet for a live problem
  3. Situation, complication and question framing
  4. First MECE issue tree with a gap and overlap check
  5. Choosing between issue, hypothesis, driver and decision trees
  6. Structuring speed baseline on three old problems
  7. Tree drawing conventions and a personal template
  8. Scope boundary and out-of-scope list
  9. Decision maker's definition of a useful answer
  10. Weekly structuring drill on a business headline
  11. Branch pattern library for reuse
  12. Living issue tree for the current problem
  13. Monday branch status check
  14. Monthly peer tree swap
  15. Tree retrospective at the end of each problem
  16. Daily key question check before email
  17. Structuring practice log and monthly score
  18. Structuring reading list and quarterly reread
  19. Splitting drills by segment, process, formula and stakeholder
  20. Driver trees that reconcile to the numbers
  21. Converting branches into testable hypotheses
  22. Decision trees for choices between options
  23. Whiteboarding a tree live with a client team
  24. Root cause trees for operational failures
  25. Structuring qualitative and people questions
  26. Explaining the tree in two minutes to a senior client
  27. Branch prioritisation by value at stake and ease
  28. Stop rule for killing branches
  29. Analysis list built from the leaves of the tree
  30. Reframing a solution brought in as a problem
  31. Repairing a tree that fails review
  32. Choosing a tool for drawing and sharing trees
  33. Merging competing trees from two stakeholders
  34. Draft issue tree in the first week of an engagement
  35. Tree review session with the manager or partner
  36. Pressure-test session on the tree with the client team
  37. Restructuring when the main branch is refuted
  38. Teaching a structuring session to new joiners
  39. Analyst ownership of one branch
  40. Coaching junior team members on their trees
  41. Issue trees inside an in-house strategy team
  42. Structuring alone as an independent consultant
  43. Two-hour structure for an urgent executive question
  44. Structuring skills self-assessment grid
  45. Value driver tree linked to the client's accounts and KPIs
  46. Systems maps for problems with feedback loops
  47. Sizing every branch before analysis starts
  48. Pre-mortem on the tree and the emerging answer
  49. Structuring a where-to-play strategic question
  50. Structuring a problem with sensitive stakeholder politics

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Key question written in one testable sentence

Every tree inherits the quality of the question at its root, and most weak trees start from a topic ("customer churn") rather than a question someone must answer. Writing the key question as one sentence with a decision, a metric, a time frame and an owner gives the whole team the same target before anyone draws a branch.

First tasks

  • Write the problem you are working on as a single question in under 30 words
  • Add the decision, the metric, the time frame and the decision maker to the sentence
  • Ask two colleagues to restate the question in their own words
  • Save the agreed wording at the top of the problem document

Problem statement worksheet for a live problem

Before a tree is worth drawing you need the context around the question: what success looks like, what is out of scope, the constraints, who the stakeholders are and what would count as sufficient accuracy. A one-page problem statement worksheet captures all of it, and filling it in usually exposes a disagreement nobody had spotted.

First tasks

  • Sketch the seven worksheet boxes on one page for your current problem
  • Rewrite each success criterion so it has a number or a clear test
  • List the stakeholders and note what each one most wants from the answer
  • Walk the problem owner through the worksheet and capture their edits

Situation, complication and question framing

Clients rarely bring a clean question; they bring a story about what changed. Separating the situation (what was stable), the complication (what changed or went wrong) and the question it raises turns a rambling briefing into a key question you can defend, and it is the same framing you will later use to open the storyline.

First tasks

  • Write the situation in three sentences describing what used to be true
  • State the complication as one specific change with a number or a date
  • Derive the question that the complication forces the client to answer
  • Read the framing to someone outside the work and note what confused them

Make it yours.

Install Issue Trees and Problem Structuring, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.