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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A paper-based illustration representing Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 h45-90 min30-60 min1-2 h
Participantsdifferent
3-103-102-84-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesContext canvas, Open questions, Shared context notesPower Interest Grid, Strategy per StakeholderAlignment Map, Open Issues, Decision Questions
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
ContextFramingRequirementsCanvas
StakeholdersFacilitationAlignmentPlanning
AlignmentStakeholdersStrategyFacilitation
Add more methods