Atomize

Purpose

Atomize is a decomposition technique that breaks an overwhelming challenge, feature, or goal into its smallest meaningful components — ‘atoms’. By making each piece small enough to understand and act on independently, teams reduce complexity, enable parallel work, and gain a clear picture of the total scope.

At a glance

• Group size: 3–8
• Duration: 20 minutes
• Difficulty: Beginner
• Facilitation style: Analytical, structured breakdown
• Setting: In-person or virtual

How to run

1. State the challenge (2 min). Write the big challenge, feature, or project on the board.
2. First-level breakdown (5 min). Ask: “What are the major pieces of this?” Break it into 3–7 sub-components.
3. Atomize each component (8 min). For each sub-component, ask: “Can this be broken down further?” Continue until each piece is small enough to be tackled by one person in one work session.
4. Validate atoms (3 min). Review: Is each atom independently understandable? Can it be completed without waiting for other atoms? Is it testable?
5. Organize (2 min). Arrange atoms by dependency, priority, or assignment.

Materials needed

• Large wall or digital whiteboard
• Sticky notes (different colours for different levels)
• Markers

Pitfalls & common mistakes

• Stopping too early. If an ‘atom’ would take a whole week, it’s not atomic enough.
• Atomizing without context. Everyone needs to understand the big picture before decomposing.
• Losing sight of the whole. Keep the original challenge visible as you decompose.

Inclusion & accessibility

• Explain each decomposition level aloud.
• Allow participants to contribute verbally while a scribe captures.
• Use colour coding to distinguish decomposition levels.

Variations

• User Story Mapping extension: Use atomized pieces as user story slices.
• Dependency mapping: After atomizing, draw dependency arrows to identify the critical path.
• Effort estimation: After atomizing, estimate each atom to build a bottom-up project estimate.

When NOT to use this

• When the challenge is already small and well-defined.
• When the team needs to explore the problem space first — atomizing a poorly understood problem produces meaningless pieces.

Source & further reading

• Gray, D., Brown, S., & Macanufo, J. (2010). *Gamestorming.* O’Reilly Media.
• Patton, J. (2014). *User Story Mapping.* O’Reilly Media.