methodatlas
Session Builder

Plan my session

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

Method session60-90 minWorkshop or asyncContext Diagram

Session: C4 Model

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 1-5. 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 Diagram. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Section 1: Context

    15 min

    Describe the system boundary, the primary users, and the external systems around it. Capture the main interactions in one context view. Hint: If the boundary is unclear, the diagram becomes a map of everything. Keep the focus on one system and its environment.

    FacilitatorContext Diagram
  2. 2

    Section 2: Containers

    15 min

    Identify the main containers that deliver or store the system's behavior, such as apps, services, databases, or queues. Hint: Do not list every technical detail yet. Containers are the stable building blocks, not the implementation rabbit hole.

    FacilitatorContainer Diagram
  3. 3

    Section 3: Components

    20 min

    Break down only the containers that matter most. Show the key responsibilities and how the parts interact. Hint: Only zoom in where the audience needs more detail. A good C4 diagram avoids over-explaining the whole system.

    FacilitatorComponent Diagram
  4. 4

    Section 4: Code-level detail

    10 min

    Add code-level detail only where a decision depends on it. Keep this part optional and tightly scoped. Hint: If the conversation stays at component level, stop there. Code detail is a tool, not the default.

    FacilitatorContext Diagram
  5. 5

    Section 5: Review and handoff

    10 min

    Review the diagram with the audience, capture open questions, and agree which C4 level should be shared or stored next. Hint: A diagram that nobody can use is unfinished. Check whether the next audience needs the context, container, or component view.

    OwnerContainer Diagram
  6. 6

    Publish artifact

    10 min

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

    OwnerContext Diagram
Usable artifact

Session Brief

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

session-brief.md

Session Brief: C4 Model

Goal

Artifact: Context Diagram

Working Question

How can the system be described at the right level of detail for communication and decisions?

Context

Scope of the system, important users and external dependencies, known container names, and any constraints that should already appear in the diagram.

Setup

  • Format: Method session
  • Duration: 60-90 min
  • Mode: Workshop or async
  • Participants: One facilitator; one architect or technical lead; one domain expert; one to four additional participants who know the system and its users.
  • Owner: One facilitator
  • 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 Diagram. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or digital canvas; C4 template; sticky notes; existing architecture notes or diagrams; markers; optional deployment context sketch.

Preparation

Start with the context view, then zoom into containers, then into components only where needed. Keep each level visible before moving to the next one.

Agenda

  1. Section 1: Context (15 min) Owner: Facilitator Action: Describe the system boundary, the primary users, and the external systems around it. Capture the main interactions in one context view. Hint: If the boundary is unclear, the diagram becomes a map of everything. Keep the focus on one system and its environment. Output: Context Diagram

  2. Section 2: Containers (15 min) Owner: Facilitator Action: Identify the main containers that deliver or store the system's behavior, such as apps, services, databases, or queues. Hint: Do not list every technical detail yet. Containers are the stable building blocks, not the implementation rabbit hole. Output: Container Diagram

  3. Section 3: Components (20 min) Owner: Facilitator Action: Break down only the containers that matter most. Show the key responsibilities and how the parts interact. Hint: Only zoom in where the audience needs more detail. A good C4 diagram avoids over-explaining the whole system. Output: Component Diagram

  4. Section 4: Code-level detail (10 min) Owner: Facilitator Action: Add code-level detail only where a decision depends on it. Keep this part optional and tightly scoped. Hint: If the conversation stays at component level, stop there. Code detail is a tool, not the default. Output: Context Diagram

  5. Section 5: Review and handoff (10 min) Owner: Owner Action: Review the diagram with the audience, capture open questions, and agree which C4 level should be shared or stored next. Hint: A diagram that nobody can use is unfinished. Check whether the next audience needs the context, container, or component view. Output: Container Diagram

  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 Diagram

Closeout

  • Update result artifact: Context Diagram
  • 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 Diagram: C4 Model

Working Question

How can the system be described at the right level of detail for communication and decisions?

Context

Scope of the system, important users and external dependencies, known container names, and any constraints that should already appear in the diagram.

Participants

  • Owner: One facilitator
  • Participants: One facilitator; one architect or technical lead; one domain expert; one to four additional participants who know the system and its users.

Input

Whiteboard or digital canvas; C4 template; sticky notes; existing architecture notes or diagrams; markers; optional deployment context sketch.

Template

C4 Model 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 Diagram:
  • Container Diagram:
  • Component Diagram:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Context Diagram 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

C4 Model Working Template

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

c4-model-working-template.md

Compact working template for C4 Model with context, input, output artifacts, and next step.

C4 Model 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 Diagram:
  • Container Diagram:
  • Component Diagram:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Context Diagram.
  • Store the diagram with date, system name, and audience. Keep context, container, and component versions separate so the right zoom level can be reused later.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet