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
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
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.For easily distracted solo work, the method sets clear time boundaries for concentrated work. It protects attention when large tasks would otherwise fall apart into small avoidance moves.
Complexitysame
LowLowLowLow
Timedifferent
1-2 h15-90 min daily15-30 min25 min Zyklen
Participantsdifferent
2-812-61
Formatdifferent
WorkshopAsyncWorkshopAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativePriority Task, Completion Note, Daily FocusRoot cause notes, CountermeasuresFocus Sessions, Task Progress, Interruption Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
PrioritizationProductivityFocusExecution
Root causeIncidentLeanProblem solving
FocusTime managementProductivityExecution
Add more methods