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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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 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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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
LowHighLowLow
Timedifferent
45-90 min1-6 Wochen30-60 min30-60 min
Participantsdifferent
3-124-103-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, Agreements8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
AlignmentStakeholdersTeam
QualityProblem solvingRoot cause
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods