Learning objectives
By the end you can:
- State MECE precisely (Mutually Exclusive and Collectively Exhaustive) and explain, from first principles, what specifically breaks in your analysis when a decomposition fails each half.
- Build a multi-level issue tree for a real business problem using each of the four standard cuts (algebraic/formula, process/value-chain, segment, and stakeholder) and explain, for any given problem, which cut fits best and why.
- Run the two live tests on any tree, the twin-membership test (does a single real case ever belong to two branches?) and the orphan-case test (does any real case belong to none?), and use them to diagnose a flawed tree, including your own.
- Recognize and repair the classic ways a tree fails: mixing dimensions at one level ("apples and oranges"), leaving a tie-break rule unstated, and a set of branches that does not numerically reconcile to its parent.
- Judge appropriate depth and breadth for a first-pass tree, and cleanly separate the MECE test (is the cut clean?) from the prioritization judgment (which branch matters most?), the latter being the subject of the next module.
- Build a correct two-dimensional segmentation (for example, product line and geography) as nested, independently-MECE cuts or an explicit matrix, without collapsing both dimensions into one flat, illegal list.
- Distinguish the issue tree taught here (a MECE map of a question, built before you have an answer) from Minto's pyramid (a MECE map of your argument, built after you have one), and state where each is taught in this program.
- (Productivity objective: R10 duality.) Use an AI tool to draft a first-pass tree fast and to red-team a finished one, while never letting the tool's draft, or its critique, substitute for your own twin-membership and orphan-case testing.
The duality, stated once (R10). Every module in this galaxy carries two objectives at once. The understanding objective (items 1–7) is what the mastery gate rewards: you earn the belt by building and testing a tree yourself, by hand, under the quiz and the mapped drill. The productivity objective (item 8) is the payoff you keep once you're gated through: knowing how to use AI to accelerate the first draft and to stress-test the finished one, without ever letting it own the judgment. A tool can propose a tree. It cannot dispose of one. That is your job, in this module and in every engagement that follows it.
Prerequisites & connections
Builds on. Almost nothing, deliberately. CN1.01 is the first module of the Structuring & Problem-Solving branch and, like every branch's opening node in this galaxy, carries no hard prerequisite from outside its own branch; it is fully self-contained. CN0.01 and CN0.02 are recommended reading for the mindset and honest-scope framing of what this galaxy does and does not teach, but nothing here depends on them, and cross-branch sequencing is advisory, never a gate. You need no mathematics beyond arithmetic, percentages, and a simple weighted average.
Feeds forward. CN1.02 (Hypothesis-Driven Problem Solving) takes the clean tree this module teaches you to build and supplies the piece it deliberately does not teach: a MECE tree gives you the exhaustive set of places an answer could be hiding; CN1.02 teaches which branch to open first, how little analysis confirms or kills a hypothesis, and how to avoid "boiling the ocean" by analyzing every branch equally. This module teaches the map, not the route. CN1.03, the branch's crown, is this module's mirror image: once you have an answer, you build a second, entirely different MECE structure (the governing-thought pyramid) to communicate it. That structure is Barbara Minto's, taught in full in M10.03 (The Communication Toolkit), which already carries the finance galaxy's C11 competency; CN1.03 teaches the consulting-specific answer-first synthesis on top of it and hands off deck/storyline craft to the future Presentation galaxy. Hold the distinction sharply from your first tree: the issue tree maps a question you have not yet answered; the pyramid maps an answer you already have. They share a test (MECE) and nothing else. Every later branch leans on this module as its opening move: the case formats of CN2.03/CN2.04 open every case with a tree; the named frameworks of CN3.01/CN3.02 are pre-built cuts you must still test for fit, and CN3.03 teaches you when to refuse a famous framework and build bespoke instead, the direct descendant of the "framework-dump" mistake named below; every industry read, deal screen, and operating-model diagnosis from CN4 through CN7 begins the same way, cutting the question cleanly before a single number gets pulled.