Issue analysis (Minto)

Issue analysis converts a broad strategic problem into a structured hierarchy of questions. It helps a team surface assumptions, identify evidence gaps and organise analysis around the decision that strategy must ultimately answer.

When to use it

• Use it near the start of strategy development for three purposes:
• Brainstorming: surface questions about markets, customers, competitors, prices, capabilities and trends.
• Evidence planning: reveal which questions require research or analysis.
• Structuring: organise questions into a logical pyramid that converges on a strategic answer without suppressing early exploration.

Origins

Barbara Minto developed the Pyramid Principle while working in management consulting and later codified it as a method for structuring thinking and communication. Consulting groups adapted its Situation–Complication–Question logic and mutually exclusive, collectively exhaustive groupings into issue trees for problem solving and strategy.

What it is

Issue analysis begins with the decision or key question, then decomposes it into the smaller questions whose answers are necessary to resolve it. Risks and opportunities may be external—demand, entrants, technology or regulation—or internal—customer loss, capability, leadership or execution.

The tree is both a thinking model and a research plan. Its branches should make clear what evidence is needed, who owns it and how lower-level conclusions combine into an answer.

How to use it

Start with S-C-Q:

• Situation: describe the relevant current and recent context in one paragraph.
• Complication: state the change, constraint or opportunity that makes action necessary.
• Key question: express the decision the strategy process must answer.

Key question

Level 1 questions

Level 2 questions

Level 3 questions

Under the key question, create 3, 4 or 5 major subquestions. Decompose each only as far as needed—sometimes to a third level—so that a workstream can answer it. Group branches by a coherent logic such as time, structure, process or rank.

Aim for questions that are independent and non-overlapping while collectively covering the decision. A yes/no form can force conclusion: “Will market demand exceed 5 per cent?” is more decision-oriented than “What is demand?” Yet exploratory “how” and “why” questions remain legitimate during diagnosis; convert them into testable hypotheses rather than banning them mechanically.

Avoid a branch with only one child, and generally keep fewer than 10 subissues under a node. Assign evidence, method, owner and due date to each leaf. During synthesis, work upward: answer leaves, combine the evidence and revise the tree when findings change the problem.

A simplified analysis might conclude that one entrant will enter and another will not; competition will intensify; but the firm can maintain growth because market expansion, advantage and manageable risks offset the pressure. The value lies in making that reasoning inspectable.

Top practical tip

Write a precise S-C-Q before building branches, then attach an evidence requirement and owner to every leaf question.

Top pitfall

Do not make an early issue tree rigid. It is a hypothesis about the problem and should change when evidence reveals a better framing.

Further reading

Minto, B. The Pyramid Principle: Logic in Writing and Thinking.