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 Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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 a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit.When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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
LowHighMediumMedium
Timedifferent
1-2 h0.5-2 Tage1-3 h1-2 h
Participantsdifferent
3-106-125-304-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesService Blueprint, Fail Points, Ownership MapConsensus Clusters, Theme Titles, Priority AreasAlignment Map, Open Issues, Decision Questions
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
Service designOperationsJourneyBlueprint
FacilitationConsensusWorkshopAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods