View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Growth Hooked Model | ![]() Decision Making Constraint Analysis | ![]() Architecture C4 Model | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Multiple workshops over several weeks | 30-90 min | 1-4 h | 1-2 Tage |
Participantsdifferent | 2-8 | 2-8 | 1-5 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | GrowthBehaviorRetention | ConstraintsDecisionPlanningOptions | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |



