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 C4 Model |
|---|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 30–60 min per interview | 1-2 Tage | 1-4 h |
Participantsdifferent | 2-4 pro Pitch | 1 participant per interview | 1-4 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Interview Notes, Themes, Insight Summary | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | PlanningDeliveryAutonomy | QualitativeResearchCustomerDiscovery | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |



