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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception 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.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 decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.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.
Complexitysame
LowLowLowLow
Timedifferent
30-60 min1-2 h60-90 min1-2 h
Participantsdifferent
2-83-104-103-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesProblem Cluster, Prioritized Challenge, ExperimentInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
Root causeQualityOperations
CanvasArchitectureAlignmentWorkshop
FacilitationDecisionProblem solvingWorkshop
AlignmentArchitectureCanvas
Add more methods