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 Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper illustration for Time Blocking
Operations
Time Blocking
Purposedifferent
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.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.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.With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure.
Complexitydifferent
MediumLowLowLow
Timedifferent
2-6 h25 min Zyklen30-60 min15-30 min Planung, laufend
Participantsdifferent
2-8111
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsFocus Sessions, Task Progress, Interruption NotesUpdated Task System, Weekly Focus, Next ActionsBlocked Calendar, Capacity View, Focus Plan
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
FocusTime managementProductivityExecution
ProductivityExecutionPlanning
PlanningTime managementFocus
Add more methods