Subdividing means breaking a large, complex problem into smaller, more manageable parts so each piece can be understood and solved on its own.
The idea
Big problems are often too complex to hold in mind or attack all at once. Subdividing splits them into smaller sub-problems — by component, by time period, by cause, or by owner — that are each simple enough to reason about individually. Solving (or at least understanding) the pieces usually makes the whole more tractable than trying to solve it in one pass, and it also makes it easier to parallelize work or assign different parts to different people.
When to use it
- A problem or project feels too large or vague to start on directly.
- Different parts of a problem have different causes, owners, or timelines.
- You need to estimate or plan work that is currently one big unknown.
How to apply it
- State the overall problem clearly.
- Split it into parts that are as independent of each other as possible.
- Solve, estimate, or assign each part separately.
- Recombine the parts and check that solving them together actually resolves the original problem.
Watch out for
- Subdividing along the wrong lines can hide dependencies between the parts, so solving each piece doesn’t add up to solving the whole.
- Over-subdividing turns one manageable problem into many small coordination problems.
- It addresses complexity, not ambiguity — a poorly defined problem needs Problem Definition first.
Related models
- Problem Definition — defining the problem before subdividing it.
- Root Cause Analysis — a related technique for breaking a problem down by cause.
- Chunking — the same grouping principle applied to memory rather than problem-solving.