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
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
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 of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Purposedifferent
The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h Setup, laufend2-8 h45-90 min1-2 h
Participantsdifferent
15-122-82-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsAssumption List, Critical Assumptions, Learning PlanDomain Story, Glossary Notes, Process Narrative
Tagsno overlap
KnowledgeProductivityOrganization
Domain-Driven DesignEventsDiscoveryWorkshop
AssumptionsRiskDecisionDiscovery
KnowledgeDomain-Driven DesignProcess
Add more methods