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 Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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.
Complexitydifferent
LowHighMediumLow
Timedifferent
60-90 minHalf day1-2 h1-2 h
Participantsdifferent
4-123-84-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogStress Test Report, Action Plan per ScenarioAlignment Map, Open Issues, Decision QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
RiskArchitectureWorkshopValidation
StrategyBusiness modelRiskDiagnosis
AlignmentStakeholdersStrategyFacilitation
CanvasArchitectureAlignmentWorkshop
Add more methods