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 Team Charter.
Facilitation
Team Charter
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.
Complexitydifferent
MediumMediumLow
Timedifferent
2-4 h30-90 min30-60 min
Participantssame
3-123-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Team Charter, Working Norms, Role NotesPostmortem Doc, Action Items, TimelineStart Stop Continue Board, Improvement Actions
Tagsno overlap
TeamAlignmentCollaboration
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveImprovementTeamReflection
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 for Sailboat Retrospective
Agile
Sailboat Retrospective