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 RAID Log | ![]() Product Discovery Outcome-Driven Innovation | ![]() Architecture Views and Beyond | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Low | High | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | Mehrere Wochen | 1-3 Tage | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 researchers plus sample | 1-4 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | OutcomesInnovationResearchQuantitative | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |



