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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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
LowLowMediumMedium
Timedifferent
30-120 min1-2 h60-120 min1-2 h
Participantsdifferent
2-63-102-84-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Observation Notes, Improvement IdeasArchitecture Canvas, Goals, Constraints, Quality AttributesCommunication Canvas, Stakeholder Messages, Architecture Communication PlanAlignment Map, Open Issues, Decision Questions
Tagsno overlap
LeanObservationProcessOperations
CanvasArchitectureAlignmentWorkshop
ArchitectureCommunicationStakeholdersCanvas
AlignmentStakeholdersStrategyFacilitation
Add more methods