Method guideArchitecture

Architecture Communication Canvas

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time60-120 min

Participants2-8

FormatWorkshop + async

MaturityEmerging

Plan the work

Prerequisite

What needs to be finished first

Complete firstClear working frame

Use the official Architecture Communication Canvas field structure and name the intended audience.

Without a bounded question or checkable evidence, the result will be unclear.

Preparation

What needs to be ready before start

Materials

Official ACC, verified architecture material and a concrete communication question.

People / roles

System owner · architecture · intended readers; involve domain owners to resolve gaps.

Pre-read

Choose materials, data access and participants to fit the research or decision question.

Time needed

60–120 minutes for a prepared overview; factual research is separate.

Setup

Open the method-specific structure. Fictional examples are for orientation only; keep the blank worksheet separate from actual findings.

Core question

The one question this method answers

What system information must these recipients understand, examine or communicate onward?

Flow

Phases with goal, actions, output and pitfall

A compact view of an existing system for communication: value, stakeholders, functions, quality, decisions, technologies, context, components and missing information.

Architecture Communication Canvas fields from the published template

Fictional example

Source-defined fields only; use the linked version. The example is fictional and the working canvas begins empty.

Value Proposition

What value does the existing system deliver?

Make reservations visible in one place.

Key Stakeholder

Who uses, funds, operates or contributes to the system?

Customers use it; operations runs it; confirm responsibility.

Core Functions

What are its most important functions?

Show availability and record a reservation.

Quality Requirements

Which quality concerns matter?

Status consistency matters; no numeric target without evidence.

Core Decisions - Good or Bad

Which decisions shaped the current system?

Use of a payment adapter is an example to verify.

Technologies

Which technologies are used for development and operation?

Leave unknown until repository or owner verifies.

Business Context

What are important external interfaces or neighbor systems?

Payment service is a neighboring system.

Components / Modules

What are the major building blocks?

Reservation service and booking module.

Core Risks and Missing Information

What risks or missing facts impede understanding?

Timeout recovery and authoritative availability source need research.

Architecture Communication Canvas (official PDF)

1
Audience
Define audience and purpose
Goal
Write a concrete communication question.
Inputs for this step
- Use the official Architecture Communication Canvas field structure and name the intended audience.
- Official ACC, verified architecture material and a concrete communication question.
Actions
- Name the system, author, recipients and date/iteration; decide why they need this compact view.
- Record Audience-focused canvas frame with its evidence status, source or open verification need.
Output
Audience-focused canvas frame
Audience-focused canvas frame
Quality check
Is the use case concrete?
Pitfall
Canvas is made without an intended reader. Name recipients and intended use.
Timing: About 10–20 minutes; schedule data or clarification work separately.
2
Context
Describe value and context
Goal
Distinguish users, payers, operators and neighboring systems.
Inputs for this step
- Audience-focused canvas frame
- Official ACC, verified architecture material and a concrete communication question.
Actions
- Fill official fields for value proposition, key stakeholders and business context.
- Record Shared system and stakeholder view with its evidence status, source or open verification need.
Output
Shared system and stakeholder view
Shared system and stakeholder view
Quality check
Are stakeholder roles distinct?
Pitfall
Stakeholders are listed without relationships. Name each role and source.
Timing: About 10–20 minutes; schedule data or clarification work separately.
3
Architecture
Summarize the existing system
Goal
Include good and bad consequences of core decisions; mark unknown technologies.
Inputs for this step
- Shared system and stakeholder view
- Official ACC, verified architecture material and a concrete communication question.
Actions
- Use official fields for functions, quality, decisions, technologies and components/modules.
- Record Compact architecture of existing system with its evidence status, source or open verification need.
Output
Compact architecture of existing system
Compact architecture of existing system
Quality check
Is unknown information labelled?
Pitfall
Technology is guessed or boxes are overfilled. Mark unknown and link to deeper evidence.
Timing: About 10–20 minutes; schedule data or clarification work separately.
4
Risks
Surface risks and information gaps
Goal
Prioritize open questions and assign a follow-up owner.
Inputs for this step
- Compact architecture of existing system
- Official ACC, verified architecture material and a concrete communication question.
Actions
- Use the official risks and missing information field to identify what readers need next.
- Record Readable overview with knowledge gaps with its evidence status, source or open verification need.
Output
Readable overview with knowledge gaps
Readable overview with knowledge gaps
Quality check
Can recipients derive a useful next step?
Pitfall
Missing facts are filled with guesses. Label unknowns and assign research.
Timing: About 10–20 minutes; schedule data or clarification work separately.

Artifact

What comes out at the end

Sketch: what the artifact looks like

Architecture Communication Canvas · ZielgruppenkommunikationStakeholder-Fragen, Botschaften, Artefakte und Formate gezielt verbinden

Form

Versioned record of question, evidence, result, uncertainty, owners and next review date.

Versioning / ownership

Track date, scope, sources, assumptions and changes; assign an owner and review for ongoing practice or initiatives.

Tool alternatives

Paper and pens
Whiteboard or simple table

architecture-communication-canvas-working-template.md

Plan a session or initiative to match the actual scope of work.

Architecture Communication Canvas: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Prepare the full method Time: 60–120 minutes for a prepared overview; factual research is separate.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Official ACC, verified architecture material and a concrete communication question.
Roles: System owner · architecture · intended readers; involve domain owners to resolve gaps.
Advance information: Choose materials, data access and participants to fit the research or decision question.
Overall time needed: 60–120 minutes for a prepared overview; factual research is separate.
Setup: Open the method-specific structure. Fictional examples are for orientation only; keep the blank worksheet separate from actual findings.

Prepare for the work steps

Audience: Define audience and purpose

Use the official Architecture Communication Canvas field structure and name the intended audience.
Official ACC, verified architecture material and a concrete communication question.

Context: Describe value and context

Audience-focused canvas frame
Official ACC, verified architecture material and a concrete communication question.

Architecture: Summarize the existing system

Shared system and stakeholder view
Official ACC, verified architecture material and a concrete communication question.

Risks: Surface risks and information gaps

Compact architecture of existing system
Official ACC, verified architecture material and a concrete communication question.

Architecture Communication Canvas fields from the published template

Value Proposition

What value does the existing system deliver?

...

Key Stakeholder

Who uses, funds, operates or contributes to the system?

...

Core Functions

What are its most important functions?

...

Quality Requirements

Which quality concerns matter?

...

Core Decisions - Good or Bad

Which decisions shaped the current system?

...

Technologies

Which technologies are used for development and operation?

...

Business Context

What are important external interfaces or neighbor systems?

...

Components / Modules

What are the major building blocks?

...

Core Risks and Missing Information

What risks or missing facts impede understanding?

...

Architecture Communication Canvas (official PDF)

Audience: Define audience and purpose

Expected artifact: Audience-focused canvas frame

Audience-focused canvas frame

Entry:

...

Is the use case concrete?

Context: Describe value and context

Expected artifact: Shared system and stakeholder view

Shared system and stakeholder view

Entry:

...

Are stakeholder roles distinct?

Architecture: Summarize the existing system

Expected artifact: Compact architecture of existing system

Compact architecture of existing system

Entry:

...

Is unknown information labelled?

Risks: Surface risks and information gaps

Expected artifact: Readable overview with knowledge gaps

Readable overview with knowledge gaps

Entry:

...

Can recipients derive a useful next step?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/architecture-communication-canvas/run-sheet

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

architecture-communication-canvas-beispiel.md

Concrete filled scenario, fictional example

Fictional example: existing reservation service

Value proposition: Make reservations visible in one place.

Key stakeholders: Operations team, customers and payment service; confirm these roles with the system owner.

Core functions: Show availability and record reservations.

Quality requirements: Check status consistency during concurrent requests; add no numeric threshold without operational evidence.

Technologies: Left unknown until verified.

Business context/components: Reservation service, payment service and booking module.

Risks/missing information: Investigate timeout behavior and source of availability status.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Define audience and purposeCanvas is made without an intended reader.View in phase
Describe value and contextStakeholders are listed without relationships.View in phase
Summarize the existing systemTechnology is guessed or boxes are overfilled.View in phase
Surface risks and information gapsMissing facts are filled with guesses.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Mark unverified facts as unknown and investigate. ACC is a specific arc42 model for communicating existing systems; do not reinterpret its fields as a universal template.

Where to go next?

Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.

Architecture

Architecture Decision Record

Turns a named open knowledge gap into the subject of a decision.

Architecture

Quality Attribute Workshop

Deepens a named quality requirement field into checkable scenarios.

View in playbookBuild Architecture DocumentationMove from scattered architecture knowledge to views, decisions, and communicable documentation.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods