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 Eat the Frog
Operations
Eat the Frog
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
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.The method protects energy and attention for the task that creates the largest progress and is often postponed.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.
Complexitysame
LowLowLowLow
Timedifferent
1-2 h15-90 min daily15-30 min30-60 min
Participantsdifferent
2-812-61-6
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativePriority Task, Completion Note, Daily FocusRoot cause notes, CountermeasuresPareto Chart, Top Causes, Focus List
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
PrioritizationProductivityFocusExecution
Root causeIncidentLeanProblem solving
PrioritizationQualityFocusRoot cause
Add more methods