methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session3-4 h for medium domains, 1 day for complex domainsWorkshop or asyncContext Map

Session: Context Map

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 2-8. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Context Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Inventory Contexts

    30 min

    Place all known Bounded Contexts as circles on the wall. Assign an owner team and short responsibility per Context. Mark duplication or overlap explicitly. Hint: If 25 Contexts appear, granularity is too fine. Focus on strategic level, do not include technical modules as separate Contexts.

    FacilitatorContext Map
  2. 2

    Phase 2: Identify Relationships

    60 min

    Ask for each Context pair: is there a relationship (data, events, API). If yes, draw an arrow (upstream to downstream). Record strength and type of the relationship. Hint: If every Context is connected to every other context, modularization has failed or the map is too coarse. Make both visible and avoid overpainting.

    FacilitatorIntegration Patterns
  3. 3

    Phase 3: Assign Patterns

    60 min

    Choose the matching pattern for each relationship: Partnership (equal standing), Shared Kernel (shared code), Customer-Supplier (downstream negotiates), Conformist (downstream accepts), ACL (downstream protects itself), Open Host Service, Published Language, Big Ball of Mud (anti-pattern). Hint: Patterns are not wishes, they are diagnostics. If the current reality is a Big Ball of Mud, mark it honestly. Document target patterns separately.

    FacilitatorBoundary Notes
  4. 4

    Phase 4: Pain Points and Target State

    45 min

    Mark pain points on relationships (long releases, bug risk, duplicate models). For each top 3 pain point, define a target relationship type and measures. Hint: Target state is not 100% clean, it is a pragmatic improvement within 6-12 months. Introducing ACL is often the first step.

    FacilitatorContext Map
  5. 5

    Phase 5: Strategy and follow-ups

    30 min

    Derive strategic consequences: which teams take over which relationship, which refactorings are needed, and which platform capabilities are missing. Add the top three measures with owner and deadline. Hint: A Context Map without follow-up actions is map tourism. Define at least three measures with success indicators and a 3-month deadline.

    OwnerIntegration Patterns
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerContext Map
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Context Map

Goal

Artifact: Context Map

Working Question

Which Bounded Contexts exist, how are they integrated, where does friction and model drift occur, and which relationship patterns are appropriate?

Context

List of known Bounded Contexts with short descriptions; existing integrations (API, events, databases); known pain points (rework, inconsistencies, long release cycles); team organization per Context.

Setup

  • Format: Method session
  • Duration: 3-4 h for medium domains, 1 day for complex domains
  • Mode: Workshop or async
  • Participants: One facilitator with DDD experience; architect(s) with system overview; one Tech Lead per Context; Product Owner per Context; one scribe.
  • Owner: One facilitator with DDD experience
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Context Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with space for 5-15 Contexts; symbol set for DDD relationship patterns (Partnership, Shared Kernel, Customer-Supplier, Conformist, Anti-Corruption Layer, Open Host Service, Published Language, Big Ball of Mud); relationship lines with direction; note stickies for pain points.

Preparation

Place Contexts as circles on the wall. Show a legend with the patterns. Announce the rule: relationships are asymmetrical, arrows point from downstream to upstream (dependency).

Agenda

  1. Phase 1: Inventory Contexts (30 min) Owner: Facilitator Action: Place all known Bounded Contexts as circles on the wall. Assign an owner team and short responsibility per Context. Mark duplication or overlap explicitly. Hint: If 25 Contexts appear, granularity is too fine. Focus on strategic level, do not include technical modules as separate Contexts. Output: Context Map

  2. Phase 2: Identify Relationships (60 min) Owner: Facilitator Action: Ask for each Context pair: is there a relationship (data, events, API). If yes, draw an arrow (upstream to downstream). Record strength and type of the relationship. Hint: If every Context is connected to every other context, modularization has failed or the map is too coarse. Make both visible and avoid overpainting. Output: Integration Patterns

  3. Phase 3: Assign Patterns (60 min) Owner: Facilitator Action: Choose the matching pattern for each relationship: Partnership (equal standing), Shared Kernel (shared code), Customer-Supplier (downstream negotiates), Conformist (downstream accepts), ACL (downstream protects itself), Open Host Service, Published Language, Big Ball of Mud (anti-pattern). Hint: Patterns are not wishes, they are diagnostics. If the current reality is a Big Ball of Mud, mark it honestly. Document target patterns separately. Output: Boundary Notes

  4. Phase 4: Pain Points and Target State (45 min) Owner: Facilitator Action: Mark pain points on relationships (long releases, bug risk, duplicate models). For each top 3 pain point, define a target relationship type and measures. Hint: Target state is not 100% clean, it is a pragmatic improvement within 6-12 months. Introducing ACL is often the first step. Output: Context Map

  5. Phase 5: Strategy and follow-ups (30 min) Owner: Owner Action: Derive strategic consequences: which teams take over which relationship, which refactorings are needed, and which platform capabilities are missing. Add the top three measures with owner and deadline. Hint: A Context Map without follow-up actions is map tourism. Define at least three measures with success indicators and a 3-month deadline. Output: Integration Patterns

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Context Map

Closeout

  • Update result artifact: Context Map
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Context Map: Context Map

Working Question

Which Bounded Contexts exist, how are they integrated, where does friction and model drift occur, and which relationship patterns are appropriate?

Context

List of known Bounded Contexts with short descriptions; existing integrations (API, events, databases); known pain points (rework, inconsistencies, long release cycles); team organization per Context.

Participants

  • Owner: One facilitator with DDD experience
  • Participants: One facilitator with DDD experience; architect(s) with system overview; one Tech Lead per Context; Product Owner per Context; one scribe.

Input

Whiteboard or Miro board with space for 5-15 Contexts; symbol set for DDD relationship patterns (Partnership, Shared Kernel, Customer-Supplier, Conformist, Anti-Corruption Layer, Open Host Service, Published Language, Big Ball of Mud); relationship lines with direction; note stickies for pain points.

Template

Context Map Canvas

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 Map:
  • Integration Patterns:
  • Boundary Notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Context Map is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Context Map Working Template

View templateCompact working template for Context Map with context, input, output artifacts, and next step.
canvas

context-map-working-template.md

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

Context Map Canvas

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 Map:
  • Integration Patterns:
  • Boundary Notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Context Map.
  • Create one version per iteration with a date. Archive the previous version. Document changes to relationship types with rationale. Linking to ADRs is required.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet