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
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.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
LowMediumMediumMedium
Timedifferent
1-2 h15-60 min je Zyklus1-2 h60-120 min
Participantsdifferent
3-101-84-122-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesSituation Assessment, Decision Loop, Action UpdatesAlignment Map, Open Issues, Decision QuestionsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
DecisionChangeLearningStrategy
AlignmentStakeholdersStrategyFacilitation
ArchitectureCommunicationStakeholdersCanvas
Add more methods