Purpose
The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Architecture Canvas
Architecture Communication Canvas
Condenses an existing system into a compact overview for architecture communication.
A compact view of an existing system for communication: value, stakeholders, functions, quality, decisions, technologies, context, components and missing information.
What system information must these recipients understand, examine or communicate onward?
- Participants
- 2-8
- Time
- 60–120 minutes for a prepared overview; factual research is separate.
What system information must these recipients understand, examine or communicate onward?
Audience
Define audience and purpose
Name the system, author, recipients and date/iteration; decide why they need this compact view.
Context
Describe value and context
Fill official fields for value proposition, key stakeholders and business context.
Architecture
Summarize the existing system
Use official fields for functions, quality, decisions, technologies and components/modules.
Risks
Surface risks and information gaps
Use the official risks and missing information field to identify what readers need next.
Update the work record when new evidence, changed constraints or the planned review changes an assumption.
A good fit when
For architecture communication and shared orientation about an existing system. Not a replacement for detailed technical views or greenfield inception.
Ideal for
- Architecture Reviews
- Stakeholder Communication
- Decision Preparation
Not good for
- Pure technical detail modeling
- Communication without a clear audience
Outputs
Audience-focused canvas frame
The canvas frame contains the system, author, intended recipients, date or iteration, and the purpose of the compact view.
Shared system and stakeholder view
The overview contains official fields for value proposition, key stakeholders, and business context.
Compact architecture of existing system
The overview summarises functions, quality requirements, decisions, technologies, and components. It records both benefits and drawbacks of decisions.
Readable overview with knowledge gaps
The overview uses the official risks and missing information field and identifies what readers need next.
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.
First step
Use the official Architecture Communication Canvas field structure and name the intended audience.
Good to do first
Deep dive
How it works
The team first defines audiences, communication goals, and core messages. Then it chooses fitting artifacts, channels, and timing so content stays connectable. The result is a plan that doesn't just describe architecture but conveys it effectively.
In detail
The Architecture Communication Canvas translates architecture knowledge into audience-appropriate communication. Instead of treating all details equally, it connects stakeholders, their decisions, information needs, and suitable artifacts. This makes it visible which message should be carried by which model, diagram, or document. A focused communication plan emerges from scattered architecture information.
Facilitation
Prepare stakeholder groups, current architecture artifacts, and the communication occasion. Guide the team from goal and audience to message and format first. A common pitfall is too much technical detail; park details that are not decision-relevant for the current audience.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Sources
Architecture Communication Canvas (official PDF)canvas.arc42.orgThe official arc42 ACC template lists the nine fields represented here for communicating existing systems.Canvas overview | arc42canvas.arc42.orgThe official arc42 ACC template lists the nine fields represented here for communicating existing systems.
Artifact templates
Architecture Communication Canvas: WorksheetPlan a session or initiative to match the actual scope of work.canvas
Architecture Communication Canvas: WorksheetPlan a session or initiative to match the actual scope of work.
canvasarchitecture-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
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Architecture
C4 Model
Instead of Architecture Communication Canvas, when you want to explain architecture through clearly separated views for different audiences.
Architecture
Views and Beyond
Connects several views of large systems and keeps cross-view information for the overall picture.
Architecture
Software Architecture Canvas
Gathers system goals, constraints, and building blocks into a compact view for early architecture decisions.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Examines how architecture decisions support important quality goals and makes risks and trade-offs visible.
Architecture
LASR (Lightweight Approach for Software Reviews)
Helps a small team assess the main quality risks in its software and choose where to investigate further.
Architecture
SAAM (Software Architecture Analysis Method)
Uses concrete tasks to show how well an architecture supports use and change.
Constraints and origin
MediumWorkshop + async60-120 min
Profile
- Method form
- Canvas
- Participants
- 2-8
- Time
- 60-120 min
- Maturity
- Emerging
- Origin
- arc42 Community
Next up: Architecture Decision Record