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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
LowLowMediumLow
Timedifferent
Ongoing30-60 minAs needed45-90 min
Participantsdifferent
1-203-124-154-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Visual Board, Status Indicators, Exception CuesStart Stop Continue Board, Improvement ActionsIncident Log, Action Tracker, Stakeholder UpdatesSailboat Board, Risks, Improvement Actions
Tagsno overlap
SignalsOperationsVisual management
RetrospectiveImprovementTeamReflection
IncidentOperationsReliability
RetrospectiveTeamImprovement
Add more methods