think-morphological-analysis
Morphological Analysis
Most design and option work jumps straight to a few familiar combinations and never sees the rest of the space. Morphological analysis (the "Zwicky box") refuses that shortcut. It treats a solution as a CONFIGURATION - a single value chosen on each of several semi-independent dimensions - and lays the whole space out so the unobvious corners come into view. The durable move has two halves, and the second is what separates it from a plain options list: (1) decompose the problem into a small set of independent PARAMETERS with their discrete VALUES, giving the full combinatorial cross-product; then (2) run a cross-consistency assessment - pair off every value with every other value across parameters, strike the internally incompatible pairs, and keep only the configurations that survive. The output is a morphological field: a parameter-by-value box plus a consistency-pruned set of internally consistent configurations. It is not a tree, not a ranked list, and not the chosen answer - it generates and prunes-for-consistency; a downstream step scores and chooses.
When to Use
- The solution genuinely is a configuration - a choice on each of several semi-independent dimensions (a product architecture, a service or pricing bundle, a feature set, a policy package, a research design, a go-to-market shape).
- The real risk is tunnel vision: the team keeps defaulting to one familiar combination and would not otherwise see the rest of the space, including the corners no forward search would visit.
- The parameters are real and discoverable, and some value pairs are clearly incompatible - so the cross-consistency pass does real pruning rather than rubber-stamping everything.
- The goal is breadth-with-structure (cover the space, then narrow to the viable region), with scoring and selection handled as a separate downstream step.