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
A paper-based illustration representing Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration of shared options, independently placed voting dots, and a highlighted shortlist.
Facilitation
Dot Voting
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
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 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 a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection.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
LowMediumLowLow
Timedifferent
45-90 min1-3 h5-15 min1-2 h
Participantsdifferent
3-105-303-203-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Context canvas, Open questions, Shared context notesConsensus Clusters, Theme Titles, Priority AreasRanked list, Consensus signal, ShortlistArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
ContextFramingRequirementsCanvas
FacilitationConsensusWorkshopAlignment
FacilitationVotingConsensusPrioritization
CanvasArchitectureAlignmentWorkshop
Add more methods