methodatlas
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
Paper illustration of Double Diamond with its method-specific working model.
Innovation
Double Diamond
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Purposedifferent
For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
Wochen bis Monate2-6 h60-120 min1-6 Wochen
Participantsdifferent
3-123-102-84-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Problem Statement, Solution Options, Prototypes, Deliverables per PhaseFMEA Table, Risk Priority, Mitigation ActionsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
ProcessDivergenceInnovation
RiskQualityOperationsRoot cause
ArchitectureCommunicationStakeholdersCanvas
QualityProblem solvingRoot cause
Add more methods