View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture Architecture Decision Record |  Delivery RAID Log |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | High | Low | Low | Low |
Timedifferent | Mehrere Wochen | 15-45 min | 30 min Setup, dann laufend | 1-2 Tage |
Participantsdifferent | 2-6 researchers plus sample | 1-3 | 1-3 maintaining, briefing for everyone | 1-4 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication |