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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Purposedifferent
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 a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
MediumLowLowLow
Timedifferent
60-120 min30-60 min15-45 min45–75 min
Participantsdifferent
2-83-101-3Team members involved
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanEmotion Board, Themes, Action ItemsADR File, Decision Log, Rationale4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ArchitectureCommunicationStakeholdersCanvas
RetrospectiveTeamReflection
ArchitectureRationaleDocumentationGovernance
RetrospectiveLearningReflectionTeam
Add more methods