methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Flywheel.
Growth
Flywheel
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Purposedifferent
The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.
Complexitydifferent
LowLowMediumMedium
Timedifferent
1-4 h15-45 min60-120 minMultiple workshops over several weeks
Participantsdifferent
1-51-33-82-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramADR File, Decision Log, RationaleFlywheel Map, Friction Points, Growth Levers, Experiment BacklogHooked loop, Trigger map, Reward design, Ethics check
Tagsno overlap
ArchitectureCommunicationVisualization
ArchitectureRationaleDocumentationGovernance
GrowthRetentionConversion
GrowthBehaviorRetention
Add more methods