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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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 a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowMediumMediumLow
Timedifferent
1-2 h1-3 h60-120 min1-2 h
Participantsdifferent
2-83-102-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeProcess Map, Handoff List, Improvement BacklogCommunication Canvas, Stakeholder Messages, Architecture Communication PlanInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ProcessOperationsImprovement
ArchitectureCommunicationStakeholdersCanvas
AlignmentArchitectureCanvas
Add more methods