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 Mad Sad Glad
Agile
Mad Sad Glad
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
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.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.
Complexitysame
LowLowLow
Timedifferent
30-60 min1-4 h1-2 h
Participantsdifferent
3-101-53-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Emotion Board, Themes, Action ItemsContext Diagram, Container Diagram, Component DiagramArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
RetrospectiveTeamReflection
ArchitectureCommunicationVisualization
CanvasArchitectureAlignmentWorkshop
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue