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 for DMAIC.
Operations
DMAIC
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Purposedifferent
For a process problem with fluctuating performance, the method brings analysis and improvement into a disciplined sequence. It creates a framework in which numbers, causes, and control come together.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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.
Complexitydifferent
HighHighLowLow
Timedifferent
2-12 Wochen2-6 h1-2 h30-60 min
Participantsdifferent
3-103-103-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Project Charter, Measurement Plan, Cause Analysis, Control PlanFMEA Table, Risk Priority, Mitigation ActionsArchitecture Canvas, Goals, Constraints, Quality AttributesFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Continuous improvementQualityProcess improvement
RiskQualityOperationsRoot cause
CanvasArchitectureAlignmentWorkshop
Root causeQualityOperations
Add more methods