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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
30 min Setup, dann laufend1-3 h30-60 min45–75 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-103-10Team members involved
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
RAID Log, Status Report SourceProcess Map, Handoff List, Improvement BacklogEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
ProcessOperationsImprovement
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods