View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Context CanvasFishbone DiagramArchitecture Decision RecordFailure Mode and Effects Analysis
| Criterion |  Product Discovery Context Canvas |  Operations Fishbone Diagram |  Architecture Architecture Decision Record |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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 | Low | Low | Low | High |
Timedifferent | 45-90 min | 30-60 min | 15-45 min | 2-6 h |
Participantsdifferent | 3-10 | 2-8 | 1-3 | 3-10 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | Fishbone Diagram, Cause Categories, Investigation Backlog | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ContextFramingRequirementsCanvas | Root causeQualityOperations | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause |