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
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
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
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.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.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
HighMediumLowLow
Timedifferent
1-4 Wochen30-90 min30-60 min30-60 min
Participantsdifferent
6-30 Experten3-123-123-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Expert Forecast, Consensus Range, Assumption NotesPostmortem Doc, Action Items, TimelineStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
ForecastingExpertsDecisionStrategy
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods