methodatlas
Session Builder

Plan my session

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

Method session2-3 hWorkshop or asyncCommunication Canvas

Session: Architecture Communication Canvas

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

  1. 1

    Phase 1: Segment target groups

    30 min

    List target groups (Exec, Eng teams, Operations, Security, external partners, customers). Add role, need, and existing knowledge level per group. Hint: If everyone ends up in one target group, the communication is not differentiated. There should be at least three target groups.

    FacilitatorCommunication Canvas
  2. 2

    Phase 2: Messages per target group

    45 min

    Write the central message for each target group in 1-2 sentences (outcome, not technology). Add secondary messages. What should they understand and what should they do? Hint: Execs need business outcome, not architecture patterns. Engineering needs patterns and trade-offs. The message must be differentiated.

    FacilitatorStakeholder Messages
  3. 3

    Phase 3: Format and channel

    30 min

    Choose a suitable format per target group (brief, ADR, diagram, demo, Q-and-A, talk) and channel (email, wiki, workshop, all-hands). Define frequency. Hint: The format should fit the attention span. Execs read a one-pager, not an ADR. Engineering wants code proximity.

    FacilitatorArchitecture Communication Plan
  4. 4

    Phase 4: Responsibility and cadence

    30 min

    Define an owner for communication, frequency, and success criterion per target group, for example acceptance rate or feedback count. Put dates in the calendar. Hint: Communication without an owner will drift, and nobody will feel responsible. The owner must have access to the target group.

    FacilitatorCommunication Canvas
  5. 5

    Phase 5: Pilot and feedback

    15 min

    Run the first iteration as a pilot with one target group. Add a feedback mechanism, for example Q-and-A or survey. Review after 2 weeks. Hint: Pilot before scaling prevents large waste. If the pilot group does not understand the message, iteration is needed.

    OwnerStakeholder Messages
  6. 6

    Publish artifact

    10 min

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

    OwnerCommunication Canvas
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Architecture Communication Canvas

Goal

Artifact: Communication Canvas

Working Question

Which architecture message reaches which target group in which format, so that decisions, acceptance, or implementation are supported?

Context

Stakeholder list with roles; existing communication formats; known stakeholder expectations, for example detail level, language, technical level; communication failures from the past.

Setup

  • Format: Method session
  • Duration: 2-3 h
  • Mode: Workshop or async
  • Participants: One architect; one communications owner, for example PMO, Product Marketing, or Engineering Lead; 2-4 participants from Engineering, Product, and stakeholder areas; scribe.
  • Owner: One architect
  • 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 Communication Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro with canvas fields (target groups, messages, format, channel, frequency, responsibility, success criterion); template; examples of existing architecture artifacts (ADR, diagrams, whitepaper).

Preparation

Put the canvas on the wall. One line per target group. Rule: each target group gets a tailored combination of message, format, and channel.

Agenda

  1. Phase 1: Segment target groups (30 min) Owner: Facilitator Action: List target groups (Exec, Eng teams, Operations, Security, external partners, customers). Add role, need, and existing knowledge level per group. Hint: If everyone ends up in one target group, the communication is not differentiated. There should be at least three target groups. Output: Communication Canvas

  2. Phase 2: Messages per target group (45 min) Owner: Facilitator Action: Write the central message for each target group in 1-2 sentences (outcome, not technology). Add secondary messages. What should they understand and what should they do? Hint: Execs need business outcome, not architecture patterns. Engineering needs patterns and trade-offs. The message must be differentiated. Output: Stakeholder Messages

  3. Phase 3: Format and channel (30 min) Owner: Facilitator Action: Choose a suitable format per target group (brief, ADR, diagram, demo, Q-and-A, talk) and channel (email, wiki, workshop, all-hands). Define frequency. Hint: The format should fit the attention span. Execs read a one-pager, not an ADR. Engineering wants code proximity. Output: Architecture Communication Plan

  4. Phase 4: Responsibility and cadence (30 min) Owner: Facilitator Action: Define an owner for communication, frequency, and success criterion per target group, for example acceptance rate or feedback count. Put dates in the calendar. Hint: Communication without an owner will drift, and nobody will feel responsible. The owner must have access to the target group. Output: Communication Canvas

  5. Phase 5: Pilot and feedback (15 min) Owner: Owner Action: Run the first iteration as a pilot with one target group. Add a feedback mechanism, for example Q-and-A or survey. Review after 2 weeks. Hint: Pilot before scaling prevents large waste. If the pilot group does not understand the message, iteration is needed. Output: Stakeholder Messages

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

Closeout

  • Update result artifact: Communication Canvas
  • 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

Communication Canvas: Architecture Communication Canvas

Working Question

Which architecture message reaches which target group in which format, so that decisions, acceptance, or implementation are supported?

Context

Stakeholder list with roles; existing communication formats; known stakeholder expectations, for example detail level, language, technical level; communication failures from the past.

Participants

  • Owner: One architect
  • Participants: One architect; one communications owner, for example PMO, Product Marketing, or Engineering Lead; 2-4 participants from Engineering, Product, and stakeholder areas; scribe.

Input

Whiteboard or Miro with canvas fields (target groups, messages, format, channel, frequency, responsibility, success criterion); template; examples of existing architecture artifacts (ADR, diagrams, whitepaper).

Template

Architecture Communication Canvas 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

  • Communication Canvas:
  • Stakeholder Messages:
  • Architecture Communication Plan:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Communication Canvas 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

Architecture Communication Canvas Working Template

View templateCompact working template for Architecture Communication Canvas with context, input, output artifacts, and next step.
canvas

architecture-communication-canvas-working-template.md

Compact working template for Architecture Communication Canvas with context, input, output artifacts, and next step.

Architecture Communication Canvas 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

  • Communication Canvas:
  • Stakeholder Messages:
  • Architecture Communication Plan:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Communication Canvas.
  • Canvas with date, version, and owner. Changes to messages or channels need a rationale. Add success metrics, such as acceptance and feedback, per iteration.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet