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 PDCA Cycle.
Operations
PDCA Cycle
Paper illustration for Risk Storming.
Architecture
Risk Storming
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
For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.
Complexitysame
LowLowLowLow
Timedifferent
1 h bis mehrere Wochen60-90 min1-2 h1-2 h
Participantsdifferent
1-84-123-83-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeAnnotated Diagram, Prioritized Risk List, Action BacklogInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
Continuous improvementLeanExperiments
RiskArchitectureWorkshopValidation
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods