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 Risk Storming.
Architecture
Risk Storming
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Purposedifferent
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 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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.
Complexitydifferent
LowLowMediumLow
Timedifferent
60-90 min1-2 h90-180 min initial, dann laufend30-60 min
Participantsdifferent
4-123-103-82-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesKPI Tree, Owner ListCounter Metric List, Guardrail Definitions
Tagsno overlap
RiskArchitectureWorkshopValidation
CanvasArchitectureAlignmentWorkshop
MetricsStrategyAlignmentMeasurement
MetricsMeasurementStrategyExperiments
Add more methods