World Congress 2023 • Sep 21, 2023

Architecture Communication Canvas

Gernot Starke , Benjamin Wolf

Complex architecture doesn't require hundred-page wikis. The Architecture Communication Canvas distills massive systems into a single page. Map your technical debt in under two hours.

Pause
Mute Enter Fullscreen
#1 about 3 min

Common pitfalls in standard architecture documentation

Traditional architecture documentation suffers from being entirely missing, overwhelmingly long, or incomprehensibly detailed.

#2 about 5 min

Adapting visual canvases for software engineering

The canvas concept provides a structured, single-page facility to limit scope and highlight key elements of a software system.

#3 about 4 min

Structuring documentation with the arc42 template

The arc42 framework provides foundational views like quality goals and system context but faces adoption friction due to perceived length.

#4 about 3 min

Defining the architecture communication canvas core structure

The canvas distills system constraints into three mandatory areas covering the business problem, proposed solution, and associated technical risks.

#5 about 4 min

Constraining documentation output via forced technical brevity

Limiting answers to core architectural questions forces development teams to focus solely on the most critical stakeholders and implementation choices.

#6 about 3 min

Applying the canvas across practical engineering scenarios

A predefined canvas structure accelerates technical audits, prevents writer's block, and provides baseline system clarity under emergency conditions.

#7 about 4 min

Scaling the canvas format across diverse architectures

Visual layouts spanning enterprise platforms, internal tooling, and single-developer scripts demonstrate structural flexibility across varying project sizes.

#8 about 4 min

Observing team execution and collaborative artifact implementation

Teams filling out physical or digital canvases collaboratively routinely uncover forgotten decisions and align on architectural intent within hours.

#9 about 2 min

Managing structural updates and highlighting poor decisions

Engineering teams must cultivate psychological safety to document flawed choices and review canvas artifacts quarterly against comprehensive architecture wikis.

Matching moments

2:23 min

Condensing the ARC 42 framework into one page

Benjamin Wolf Benjamin Wolf +1 · World Congress 2025

1:28 min

Documenting microservice architectures with the architecture canvas

Benjamin Wolf Benjamin Wolf +1 · World Congress 2025

1:44 min

Aligning agile teams and stakeholders using architecture diagrams

Simon Lasselsberger · World Congress 2022

1:40 min

Introduction to documenting architecture decisions in agile teams

Johannes Dienst · LIVE

4:30 min

Converting visual software architecture into accessible text representations

Artur Ortega · A11y + AI

2:53 min

Real-world examples of architecture canvases in projects

Benjamin Wolf Benjamin Wolf +1 · World Congress 2025