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 of Strategy Map with its method-specific working model.
Business Strategy
Strategy Map
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results.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 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
MediumLowMediumMedium
Timedifferent
2-4 h workshop plus review1-2 h1-3 h1-2 h
Participantsdifferent
4-103-105-304-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Strategy Map, Objective Set, Cause-Effect HypothesesArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority AreasAlignment Map, Open Issues, Decision Questions
Tags1 shared
AlignmentExecutionGoalsCausality
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods