View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Visual ManagementFailure Mode and Effects AnalysisStart Stop ContinueSailboat Retrospective
| Criterion | ![]() Operations Visual Management | ![]() Operations Failure Mode and Effects Analysis | ![]() Agile Start Stop Continue | ![]() Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 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 | Low | High | Low | Low |
Timedifferent | Ongoing | 2-6 h | 30-60 min | 45-90 min |
Participantsdifferent | 1-20 | 3-10 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | FMEA Table, Risk Priority, Mitigation Actions | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | SignalsOperationsVisual management | RiskQualityOperationsRoot cause | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |



