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 Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitydifferent
MediumLowMedium
Timedifferent
1-3 h30-60 min1-3 h
Participantsdifferent
3-83-123-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Failure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsStart Stop Continue Board, Improvement ActionsKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
FailureResilienceRisk
RetrospectiveImprovementTeamReflection
KnowledgeMappingRisk
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective