liveBook · Manning

Structured divergence

As explained in The Architecture of Reasoning

A reasoning technique that deliberately widens the context and alternatives considered before commitments are made.

A team can produce a long list of options and still explore only one path. Pricing tiers, feature bundles, promotions, and discount timing may all preserve the same pricing model. Structured divergence asks for alternatives that change the underlying approach, not just its details. It widens the context and available paths before the team commits. section 4.4

The sequence matters: generate and clarify distinct branches first, then compare them. If every new idea meets an immediate objection, an unfamiliar approach may be rejected before anyone understands how it would work. If the team converges without surfacing alternatives, it also loses a record of paths it could have considered when conditions later change. section 4.4

A pricing discussion that has not branched

Suppose a product team debates three tiers, two bundles, and a temporary discount. The list is substantial, but every option assumes the same way of charging for value. Asking whether a different pricing model, target segment, or way of delivering value would change the decision opens genuinely different branches. Each branch needs enough shape to be compared, not just a name on a whiteboard. section 4.4

Use the smallest amount of branching the decision warrants:

  • Branch when the problem’s shape is uncertain, several functions bring competing constraints, or the consequences extend over time. section 4.5
  • Invest more before decisions that lock in technical, financial, or cultural commitments; easily reversed, low-cost decisions usually need less exploration. section 4.5 section 4.5.2
  • Keep branching bounded. Early criticism, senior voices, time pressure, and too many options can each prevent a useful comparison. section 4.8

In a live discussion, first check whether people share an understanding of the current proposal’s assumptions. If not, make those assumptions visible before adding options. If they do, but keep circling the same path, ask for a small number of structurally distinct approaches. Compare them against shared criteria once they are formed. The aim is not perpetual exploration; it is enough diversity to make commitment defensible. section 7.5 section 4.8

How The Architecture of Reasoning covers it

How deep it goes
Explains sequencing and decision triggers, then identifies social and cognitive failure modes without prescribing a fixed branching procedure.
Examples
Uses pricing tiers, bundles, discounts, alternative pricing models, target segments, and value delivery to distinguish many ideas from distinct branches.
What it assumes
Assumes participants can surface a proposal’s assumptions; when they cannot, makes that reasoning visible before branching.
What you can do after
Practice/perform structured divergence by forming a few distinct approaches before comparing them against shared criteria.
How it connects
Connects branching to linear reasoning, chain-of-thought, assumption surfacing, perspective rotation, and hypothesis-and-evidence testing.

This explainer was generated by Manning's knowledge graph from the text of The Architecture of Reasoning. The section links point to the parts of the book it draws on.