methodatlas
Playbook

Lead Domain Discovery to Boundaries

Move from domain flow to language, events, bounded contexts, and first architecture boundaries.

Outcome

A domain-justified cut with events, terms, context boundaries, and open integration questions.

At the end you have

Event TimelineDomain StoryContext CanvasContext Map

Decision point

You can decide which domain boundaries, language, and integration relationships are relevant for next architectural work.

Next step

Validate boundaries with teams and stakeholders and move into architecture decisions or system slicing.

Ideal for

  • DDD initiatives
  • Monolith decomposition
  • functionally complex products

Not good for

  • small CRUD features
  • pure infrastructure topics
Preparation

What should be clear before you start

Roles

  • Domain experts
  • architect or tech lead
  • product and engineering representatives

Inputs

  • domain flow or problem space
  • known systems and teams
  • terms, events, or process examples

Setup

  • Limit domain slice
  • Invite participants with real process knowledge
  • Define documentation format for boundaries
Flow

Method path

0 methods
    Completion criteria
    Templates

    Artifacts for this playbook

    Artifacts stay collapsed until you actually need them.

    MarkdownShow template

    Event Storming Working Template

    Compact working template for Event Storming with context, input, output artifacts, and next step.

    # Event Storming Working Template
    
    ## Goal
    
    Rapid, visual domain exploration through Business Events, Commands, Policies, and Actors on a timeline.
    
    ## Context
    
    When and for what do we use this method?
    
    ## Input
    
    Which data, observations, decisions, or materials are available?
    
    ## Execution
    
    Short notes along the runsheet.
    
    ## Output artifacts
    - Event timeline:
    - Ubiquitous language:
    - Boundaries:
    - Open questions:
    
    ## Assumptions and open questions
    
    - ...
    
    ## Decision / next step
    
    Owner, date, and success signal.
    CanvasShow template

    Bounded Context Canvas Working Template

    Compact working template for Bounded Context Canvas with context, input, output artifacts, and next step.

    # Bounded Context Canvas Working Template
    
    ## Context
    
    What is this method used for?
    
    ## Core question
    
    Which question should be answered at the end?
    
    ## Input
    
    Which data, observations, or materials are available?
    
    ## Working area
    
    - Area 1:
    - Area 2:
    - Area 3:
    - Relationships / patterns:
    
    ## Output artifacts
    - Context Canvas:
    - Glossary:
    - Integration Notes:
    
    ## Open questions
    
    - ...
    
    ## Next step
    
    Owner, date, success signal.