View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Agile 4Ls Retrospective |  Knowledge Modeling Knowledge Mapping |  Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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 | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 45–75 min | 1-3 h | 30-60 min |
Participantsdifferent | 3-8 | Team members involved | 3-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | 4Ls Board, Learning Themes, Improvement Actions | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Emotion Board, Themes, Action Items |
Tagsno overlap | FailureResilienceRisk | RetrospectiveLearningReflectionTeam | KnowledgeMappingRisk | RetrospectiveTeamReflection |