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 ALPEN Method
Operations
ALPEN Method
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 Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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'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.
Complexitydifferent
LowLowMediumLow
Timedifferent
10-20 min daily30-60 minAs needed30-60 min
Participantsdifferent
13-124-153-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Daily Plan, Time Estimates, Review NotesStart Stop Continue Board, Improvement ActionsIncident Log, Action Tracker, Stakeholder UpdatesEmotion Board, Themes, Action Items
Tagsno overlap
PlanningTime managementProductivityOperations
RetrospectiveImprovementTeamReflection
IncidentOperationsReliability
RetrospectiveTeamReflection
Add more methods