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
How Might We
Innovation
How Might We
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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction.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.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.
Complexitysame
LowLowLowLow
Timedifferent
30–45 min45–75 min30-60 min45-90 min
Participantsdifferent
1-10Team members involved3-124-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea Prompts4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
FramingOpportunityIdeationQuestions
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods