Synthesis

The Synthesis domain. 3 frameworks in this family. Each is graded honestly; see the evidence model for the tiers.

Synthesis is the move from many small pieces to a few load-bearing ones: compress without discarding, and arrange what is left so the structure carries the meaning. The work happens in two directions. Sometimes the structure has to emerge from the items, bottom-up, when you do not yet know the right buckets. Sometimes the conclusion already exists and the job is to deliver it top-down so a busy reader gets the point first. Both turn a pile into a shape someone can reason about.

Reach for this family when

• You have dozens to hundreds of raw items - research notes, support tickets, survey free-text, retro stickies - and need a few emergent themes.
• You already hold a conclusion and have to communicate it to a busy or senior reader who needs the headline, not the journey.
• A draft or memo buries its point under context, and the answer needs to lead.
• You want the synthesis traceable: each theme or claim should point back to the evidence under it.

Which one to use

The split is direction of travel. Affinity Mapping works bottom-up, from items to themes: you have a scattered pile, the right structure is unknown, and you let categories surface from the data while keeping every item attached to its theme. It organizes what already exists; it does not generate new items, and it does not impose a logical decomposition.

Pyramid Principle works top-down, from a conclusion to its support: the answer is already known, and you lead with the governing thought, then a small MECE set of ordered arguments, then evidence under each. Reach for it once the thinking is done and the task is the write-up.

A note on the near-misses both frameworks flag. If you need to decompose a question into MECE sub-questions to investigate, that is an Issue Tree (it structures the question for the analyst), not synthesis. If you need to test whether a case is sound rather than communicate one, that is Argument Mapping. The pyramid composes a clear case; it does not check it.

Composes with

Synthesis is where a process lands, so it is mostly fed rather than feeding. Affinity Mapping consumes the output of Divergent Ideation and the raw notes that Perspective and Multi-Lens review produces, clustering many items into themes. Those themes, or any settled recommendation, then flow into Pyramid Principle for the write-up. Pyramid Principle in turn presents the result of Decision and Option Evaluation to a reader. Both members are evidence-graded P, practitioner-tier: durable and widely taught, with the honest caveat spelled out in the evidence model - they make a synthesis legible, not provably better or correct.

Framework	Evidence	What it does
Affinity Mapping	P	Produces a clustered theme map that groups many raw notes, observations, quotes, or data points bottom-up into a small set of named, traceable themes (the KJ method).
Concept Mapping	M/P	Builds a concept map - a non-hierarchical network of concept nodes joined by directed, labeled linking phrases so each node-link-node reads as an explicit proposition, with cross-links across clusters - then surfaces gaps, missing links, and questionable propositions.
Pyramid Principle	P	Produces a pyramid that structures a recommendation answer-first - a single governing thought on top, a small set of MECE, deliberately ordered key arguments beneath it, and supporting evidence under each (Minto), with an optional SCQA intro framing.

Not sure which of these fits your situation? The Framework Advisor will diagnose the job and recommend a minimal sequence.