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 of several people silently writing ideas and passing sheets around with arrows.
Innovation
Brainwriting
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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Purposedifferent
When loud voices or hierarchy distort the idea search, the method creates a quiet entry into joint development. It gives everyone thinking space and gathers contributions without social brakes, making diversity more visible and easier to build on.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.
Complexitydifferent
LowLowMedium
Timedifferent
15-30 min45–75 minOngoing
Participantsdifferent
3-12Team members involved2-20
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Idea sheets, Expanded concepts, Prioritized list4Ls Board, Learning Themes, Improvement ActionsChat Transcript, Action Log, Automations
Tagsno overlap
BrainstormingCollaborationInclusionIdeas
RetrospectiveLearningReflectionTeam
CollaborationEngineeringIncident
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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