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 Kepner-Tregoe
Operations
Kepner-Tregoe
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
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 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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
HighLowMediumLow
Timedifferent
2-8 h1-2 h45-90 min1-2 h
Participantsdifferent
2-83-102-53-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Problem Analysis, Decision Analysis, Risk PlanArchitecture Canvas, Goals, Constraints, Quality AttributesA3 Report, Action Plan, Root Cause AnalysisInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
Problem solvingRoot causeDecisionOperations
CanvasArchitectureAlignmentWorkshop
LeanProblem solvingCoachingOperations
AlignmentArchitectureCanvas
Add more methods