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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
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 Weekly Review.
Operations
Weekly Review
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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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 a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 h1-2 h Setup, laufend15-30 min30-60 min
Participantsdifferent
2-812-61
Formatdifferent
WorkshopAsyncWorkshopAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeAction Lists, Project List, Review RoutineRoot cause notes, CountermeasuresUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ProductivityPlanningTasksExecution
Root causeIncidentLeanProblem solving
ProductivityExecutionPlanning
Add more methods