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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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 a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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.
Complexitydifferent
LowHighLowLow
Timedifferent
30-60 min2-8 h1-2 h1-2 h
Participantsdifferent
2-82-83-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogProblem Analysis, Decision Analysis, Risk PlanInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
Root causeQualityOperations
Problem solvingRoot causeDecisionOperations
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods