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
Paper illustration for Diary Study.
UX Research
Diary Study
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Bucket System.
Agile
Bucket System
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Purposedifferent
When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory.When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-4 Wochen1-3 h30-90 min2-6 h
Participantsdifferent
5-203-83-122-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineContext Canvas, Glossary, Integration NotesBucketed Backlog, Relative Estimates, Split CandidatesEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
UX researchTrackingBehavior
Domain-Driven DesignBoundariesModeling
EstimationBacklogRelative sizing
EventsBlueprintDomain-Driven DesignBehavior
Add more methods