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
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.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.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.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
60-90 min30-60 min1-2 h1-2 h
Participantsdifferent
4-122-63-103-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogCounter Metric List, Guardrail DefinitionsArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
RiskArchitectureWorkshopValidation
MetricsMeasurementStrategyExperiments
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods