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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.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.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.
Complexitydifferent
LowMediumLow
Timedifferent
30-60 minAs needed10-20 min daily
Participantsdifferent
3-104-151
Formatdifferent
WorkshopWorkshop + asyncAsync
Outputdifferent
Emotion Board, Themes, Action ItemsIncident Log, Action Tracker, Stakeholder UpdatesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
RetrospectiveTeamReflection
IncidentOperationsReliability
PlanningTime managementProductivityOperations
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
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem