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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck 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 Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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
LowMediumLowLow
Timedifferent
1-2 h1-3 h30-60 min45-90 min
Participantsdifferent
2-83-83-124-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeBottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
FlowMeasurementConstraints
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods