The Decision Hierarchy

Definition

The decision hierarchy is a framing tool that divides all decisions relevant to a situation into three groups: (1) decisions already made, which are taken as given and constrain everything below them; (2) the decisions to focus on right now, which define the actual scope of the current effort; and (3) decisions that can be made later or handled separately. Only things genuinely under the decision maker's control belong in the hierarchy — aspirations, goals, and outcomes affected by outside factors (like a house's future resale value) don't qualify as "decisions," however tempting it is to lump them in as if they were.

In the Book

The book builds the tool through Carl and Leitha's house decision: once they'd already decided to stay in their California region for 5-10 years and that they could afford to move, those became fixed "given" decisions that narrowed everything downstream, letting them skip the paralyzing "what are we doing with the rest of our lives?" question and focus on the actual choice — move or stay, and if move, where. The book warns that it's easy to blur this discipline: pulling an aspiration ("this house should be a good investment") into the given bucket, or letting a decision that should wait (paint color, which depends on which house is chosen) crowd the current scope. In Chapter 11, the tool reappears as the primary defense against the "narrow framing megabias" — the most common and, per Chevron's former CEO, most value-destructive source of decision failure — because testing whether the middle bucket is too small or too large is exactly what the hierarchy is built to expose.

Why It Matters

Most framing failures aren't analytical mistakes inside a decision — they're mistakes about which decision is actually being made, made invisible because nobody separated "already settled," "on the table now," and "not yet, and that's fine." This tool makes scope an explicit, inspectable object instead of an implicit assumption everyone in the room is quietly defining differently, which is what turns meetings into circular arguments. It applies to any planning or scoping exercise — product roadmaps, policy design, project charters — wherever unstated assumptions about what's fixed versus open are the real source of disagreement.