View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Outcome-Driven InnovationFishbone DiagramArchitecture Decision RecordFailure Mode and Effects Analysis
| Criterion |  Product Discovery Outcome-Driven Innovation |  Operations Fishbone Diagram |  Architecture Architecture Decision Record |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | High | Low | Low | High |
Timedifferent | Mehrere Wochen | 30-60 min | 15-45 min | 2-6 h |
Participantsdifferent | 2-6 researchers plus sample | 2-8 | 1-3 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Fishbone Diagram, Cause Categories, Investigation Backlog | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | OutcomesInnovationResearchQuantitative | Root causeQualityOperations | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause |