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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitysame
LowLowLowLow
Timedifferent
1-4 h30-60 min30-60 min1-2 Tage
Participantsdifferent
1-53-103-121-4
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramEmotion Board, Themes, Action ItemsStart Stop Continue Board, Improvement ActionsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureCommunicationVisualization
RetrospectiveTeamReflection
RetrospectiveImprovementTeamReflection
ArchitectureDocumentationCommunication
Add more methods