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 Product Canvas with its core stages and visible working result.
Product Strategy
Product Canvas
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Purposedifferent
When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point.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 a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.
Complexitydifferent
MediumMediumHigh
Timedifferent
1-2 h2-6 h2-8 h
Participantssame
2-82-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesEvent Model, UI Flow, Commands, Read ModelsProblem Analysis, Decision Analysis, Risk Plan
Tagsno overlap
CanvasDiscoveryScope
EventsBlueprintDomain-Driven DesignBehavior
Problem solvingRoot causeDecisionOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving