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
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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
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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.
Complexitysame
LowLowLowLow
Timedifferent
30 min Setup, dann laufend45-90 min30-60 min30-60 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-123-123-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
RAID Log, Status Report SourceExpectation Map, Alignment Notes, AgreementsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RiskTrackingStakeholdersGovernance
AlignmentStakeholdersTeam
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods