The Theory
Some people learn by building. Others learn by dismantling. The reverse engineer takes a working system — a piece of software, an organization, an argument — and carefully separates it into components to understand how each part contributes to the whole. This is different from destroying: the goal is not to break things but to map the internal structure. Polya formalized decomposition as a mathematical problem-solving strategy: break a complex problem into smaller, tractable sub-problems. The eliminative thinker uses a related but distinct approach: systematically discarding wrong answers until only the right one remains, the way a doctor runs through a differential diagnosis.
What the Research Found
Polya showed that decomposition is one of the most reliable problem-solving heuristics: complex problems that resist direct attack often yield when broken into components. Tversky formalized elimination by aspects — people often choose by sequentially removing options that fail key criteria rather than by comparing all options holistically. Simon demonstrated that human rationality is bounded, and that satisficing through elimination is often more adaptive than optimizing, because it works within our actual cognitive constraints.
How We Use It
Question B2 option (a) — "I take it apart piece by piece: I remove components until I understand what each one does" — maps to deconstructive strategy (dimension value 2.5). B4(e) captures the same approach applied to failing projects. The eliminative variant appears in B2(c) — eliminating wrong explanations one by one (dimension value 2.7) — and B6(e). If your instinct when facing something unfamiliar is to disassemble it systematically, your strategy is deconstructive.