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 for PDCA Cycle.
Operations
PDCA Cycle
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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 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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowLowMediumMedium
Timedifferent
1 h bis mehrere Wochen1-2 h1-2 h60-120 min
Participantsdifferent
1-83-104-122-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeArchitecture Canvas, Goals, Constraints, Quality AttributesAlignment Map, Open Issues, Decision QuestionsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
Continuous improvementLeanExperiments
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersStrategyFacilitation
ArchitectureCommunicationStakeholdersCanvas
Add more methods