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 |  Knowledge Modeling Knowledge Mapping |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|---|
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. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 h | 45-90 min | 45-90 min |
Participantsdifferent | 3-8 | 3-12 | 4-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | FailureResilienceRisk | KnowledgeMappingRisk | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |