Break apart perceptual chunks that may be blocking you
If a problem object looks like one thing, try perceiving it as separate parts with separate functions.
Why it works
Knoblich et al. showed that one source of constraint in insight problems is "chunk tightness" — the degree to which a perceptual unit (an object, a process, a word) is encoded as a fixed whole. When the solution requires using part of that whole in a new way, solvers are blocked because the chunk is encoded as indivisible. Deliberately decomposing chunks into their constituent parts makes the sub-parts available as independent solution elements.
How to do it
- Identify the objects, processes, or concepts in your problem that you’re treating as unified wholes.
- For each, list its component parts as if you’ve never seen the whole before.
- Ask: "Could any single component be used, moved, removed, or repurposed independently of the rest?"
- Generate solutions using the components rather than the wholes.
Evidence
Chunk decomposition was experimentally demonstrated by Knoblich et al. (1999, 2001) in studies of Roman numeral matchstick problems: problems requiring decomposition of tight operators were reliably harder than those requiring only looser constraint relaxation. The 2001 eye-movement study (Knoblich, Ohlsson, & Raney) added process-level evidence, showing that solvers’ gaze lingered on the tightly-chunked elements before insight, tracing the decomposition as it happened. (observational)
The evidence is robust for well-defined insight problems; the practical instruction to "decompose chunks" in open-ended work is a principled extrapolation rather than a directly tested intervention.
Sources
- Knoblich et al. (1999, 2001), chunk decomposition and insight, Journal of Experimental Psychology
- Knoblich, G., Ohlsson, S., Haider, H., & Rhenius, D. (1999). Constraint relaxation and chunk decomposition in insight problem solving. Journal of Experimental Psychology: Learning, Memory, and Cognition, 25(6), 1534-1555.
- Knoblich, G., Ohlsson, S., & Raney, G. E. (2001). An eye movement study of insight problem solving. Memory & Cognition, 29(7), 1000-1009.
Common mistake
Only decomposing the explicitly named elements of a problem while leaving the framing structure — what constitutes a valid approach — unexamined and intact.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Constraint Relaxation: Escaping the Walls You Built Yourself
- Make your constraints explicit before solving
Write out every assumption and rule you are treating as fixed — most problem-solvers carry invisible constraints they never surface.
- Question what moves and operations are permitted
Challenge the implicit rules about which actions are allowed — often the "forbidden" move is the solution.
- Schedule deliberate breaks to trigger unconscious constraint relaxation
Step away from a stuck problem with a clear intention to return — breaks allow representational change to happen below awareness.
- Seek analogies from maximally distant domains
The further the analogy’s domain from your problem, the more likely it is to break your current representation.
- Treat failed attempts as constraint-locators rather than dead ends
Each failed approach tells you precisely where the active constraint lives — mine that information before trying again.
Related concepts
- Problem Reframing: Solving the Right Problem First
Why the problem you first name is rarely the problem worth solving
- TRIZ: Systematic Invention and the Logic of Contradictions
Contradiction mapping, inventive principles, and why the best solutions eliminate trade-offs rather than manage them
- Osborn’s Brainstorming Rules, Made Practical
The original four rules, the mechanisms behind them, and what the research actually shows