Task Decomposition / Work Breakdown Structure
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
Task Decomposition, formalized in project management as the work breakdown structure, recursively divides a deliverable into smaller work packages until each can be estimated, assigned, executed, and tracked. Its core proposition is that a task too large to estimate is too large to manage, so decomposition is the precondition for planning rather than a preliminary formality. The key qualifier is granularity: packages that are too coarse cannot be executed, while packages that are too fine cost more to administer than they deliver.
SCAFFOLDING EFFECT
Reduce cognitive load
- Recursive splitting: divide the deliverable until every resulting piece is estimable and directly assignable. - Granularity check: stop splitting when a package can be estimated and tracked in a short cycle. - Dependency labeling: mark the required order and the available parallelism between the resulting packages.
Anchor fast decisions
Estimation and progress tracking both fail on large undifferentiated chunks because the uncertainty inside them is invisible. Splitting until each package is small reduces the uncertainty in each estimate and makes partial completion observable. The hierarchy then allows coordination at the level where decisions are actually made.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Work_breakdown_structureverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS