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 Standard Work Analysis.
Operations
Standard Work Analysis
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h30-60 min1-2 h60-90 min
Participantsdifferent
2-63-103-104-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Standard Work Sheet, Deviation List, Improved Standard, Training NeedsRisk Matrix, Top Risk ListArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
LeanProcessQuality
RiskDecisionPrioritizationAssessment
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
Add more methods