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 of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.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.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.
Complexitydifferent
LowLowMedium
Timedifferent
5-15 min45–75 minAs needed
Participantsdifferent
1-5Team members involved4-15
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step4Ls Board, Learning Themes, Improvement ActionsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
StartupValidationCompetition
RetrospectiveLearningReflectionTeam
IncidentOperationsReliability
Add more methods

Often compared together

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

Paper illustration for Learning Review.
Operations
Learning Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue