View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture arc42 | ![]() UX Research Surveys | ![]() Architecture Architecture Decision Record | ![]() Product Discovery Outcome-Driven Innovation |
|---|---|---|---|---|
Purposedifferent | 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. | When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal. | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 1-2 Tage | 3-14 Tage | 15-45 min | Mehrere Wochen |
Participantsdifferent | 1-4 | 50+ | 1-3 | 2-6 researchers plus sample |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Survey Results, Charts, Segment Insights | ADR File, Decision Log, Rationale | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | ArchitectureDocumentationCommunication | QuantitativeResearchValidation | ArchitectureRationaleDocumentationGovernance | OutcomesInnovationResearchQuantitative |



