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 |  Delivery RAID Log |  Architecture Risk Storming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | High | Low | Low | Low |
Timedifferent | Mehrere Wochen | 30 min Setup, dann laufend | 60-90 min | 15-45 min |
Participantsdifferent | 2-6 researchers plus sample | 1-3 maintaining, briefing for everyone | 4-12 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale |
Tagsno overlap | OutcomesInnovationResearchQuantitative | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance |