Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion	Operations Fishbone Diagram	Innovation Design Thinking	Architecture Architecture Decision Record	Operations Failure Mode and Effects Analysis
Purposedifferent	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.	For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.	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	High	Low	High
Timedifferent	30-60 min	1 Tag bis mehrere Wochen	15-45 min	2-6 h
Participantsdifferent	2-8	4-10	1-3	3-10
Formatdifferent	Workshop	Workshop	Async	Workshop
Outputdifferent	Fishbone Diagram, Cause Categories, Investigation Backlog	Problem Statement, Prototype, Test Learnings	ADR File, Decision Log, Rationale	FMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap	Root causeQualityOperations	InnovationPrototypeResearch	ArchitectureRationaleDocumentationGovernance	RiskQualityOperationsRoot cause