View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Shape Up | ![]() UX Research User Interviews | ![]() Architecture arc42 | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 30–60 min per interview | 1-2 Tage | 15-45 min |
Participantsdifferent | 2-4 pro Pitch | 1 participant per interview | 1-4 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Interview Notes, Themes, Insight Summary | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | PlanningDeliveryAutonomy | QualitativeResearchCustomerDiscovery | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |



