Map the whole idea first, then decompose — knowledge gaps…
Before attempting decomposition of any complex idea, map it as a whole with your current understanding externalized, then decompose systematically until you encounter steps you cannot explain clearly—those uncertainty points are your actual knowledge gaps.
When This Fires
- Studying a complex system (technical architecture, biological process, business model)
- Breaking a large project into tasks (the gaps between tasks are where estimation errors hide)
- Preparing to teach or explain something complex
- Any situation where you need to understand a system deeply enough to modify, debug, or extend it
Common Failure Mode
Decomposing without mapping the whole first. You dive straight into breaking the idea apart, producing a list of components that looks comprehensive but actually reflects your incomplete mental model. The parts you don't understand are missing from the list entirely — you can't decompose what you can't see. The whole-system map catches missing components before decomposition begins.
The Protocol
(1) Externalize the whole: draw, write, or diagram your current understanding of the complete idea — all components and relationships, however rough. (2) Decompose: for each component, explain how it works in your own words. (3) Mark stall points: wherever you can't explain clearly, mark with [GAP]. (4) Your [GAP] markers are a prioritized learning plan — each one is a specific piece of understanding you need to acquire. The gaps found through decomposition are far more specific and actionable than "I need to study this topic more."