Translate the issue tree into a Pyramid Principle communication

Once the analysis is done, restructure your findings into a top-down recommendation, not a bottom-up summary of the tree.

Why it works

Issue trees are analytical tools; they trace the path of discovery (bottom-up, from data to conclusion). Communication should be top-down: conclusion first, then the supporting branches. Presenting the tree chronologically ("first we looked at revenue, then we examined costs") makes the audience follow your analytical journey rather than receive your answer. Translating into a Pyramid structure delivers the answer first and uses the tree branches as supporting reasoning.

How to do it

1. After completing the analysis, write the key finding as a one-sentence conclusion.
2. Identify the two to four key branches that support it most directly.
3. Present those as your top-level supporting points under the conclusion.
4. Make data from the tree available in an appendix, not the main flow.

Evidence

This practice combines the Pyramid Principle (Minto) with issue tree methodology; both are McKinsey-developed practices widely taught in consulting and analytical training programs. The principle — separate analysis from communication — is cognitively sound but not independently studied. (mechanistic)

Top-down communication can create resistance if the audience doesn’t trust the conclusion yet — in those cases, building to the conclusion can be more effective.

Common mistake

Presenting the analysis as the communication ("we examined four branches and found X in branch two") rather than leading with the finding and supporting it with relevant branches.