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 arc42 with its core stages and visible working result.
Architecture
arc42
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage20-60 min30-60 min30-60 min
Participantsdifferent
1-41-43-123-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRunbook, Checklist, Escalation PathStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
ArchitectureDocumentationCommunication
OperationsReliabilityDocumentation
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods