View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy 5-Minuten VC-Check | ![]() DevOps Incident Command | ![]() Agile Sailboat Retrospective | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 5-15 min | As needed | 45-90 min | 45-90 min |
Participantsdifferent | 1-5 | 4-15 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Incident Log, Action Tracker, Stakeholder Updates | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | StartupValidationCompetition | IncidentOperationsReliability | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |



