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 of a Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h45-90 min30-120 min1-3 h
Participantsdifferent
2-81-62-63-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeLean Canvas, Core Assumptions, Experiment BacklogObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
StartupLeanAssumptionsBusiness model
LeanObservationProcessOperations
ProcessOperationsImprovement
Add more methods