Gernot Starke & Benjamin Wolf

Architecture Communication Canvas

Is your software documentation a 'denial of service attack'? Learn to capture an entire system's critical aspects on a single, pragmatic canvas.

Architecture Communication Canvas
#1about 3 minutes

The common problems with software architecture documentation

Most projects suffer from either no documentation, overwhelming documentation, or overly complex diagrams that are impossible to understand.

#2about 4 minutes

Understanding the canvas pattern for structured visualization

A canvas is a one-page, structured visualization tool that captures key elements of a complex topic, inspired by the Business Model Canvas.

#3about 3 minutes

A brief overview of the Arc42 documentation template

Arc42 is an open-source template with 12 chapters for structuring software architecture documentation, but it can still be too extensive for some teams.

#4about 5 minutes

Introducing the Architecture Communication Canvas

The Architecture Communication Canvas is a one-page tool structured into problem, solution, and risks sections to concisely communicate a system's design.

#5about 3 minutes

Three practical use cases for the canvas

The canvas can be used to kickstart system reviews, overcome the blank-page syndrome when starting documentation, and quickly capture essential knowledge in emergencies.

#6about 3 minutes

Real-world examples of the canvas in action

See examples of the canvas applied to a large CRM system, a small internal tool, and a simple link checker to show its scalability.

#7about 4 minutes

Team experiences and benefits of using the canvas

Teams report that creating a canvas is fast, fun, and leads to valuable insights and "aha" moments about their own system.

#8about 1 minute

Q&A on canvas implementation and maintenance

The most difficult section to write is often past "bad decisions," and the canvas should be reviewed periodically, such as every three months.

Related jobs
Jobs that call for the skills explored in this talk.

Matching moments

From ARC 42 to the Architecture Communication Canvas
02:24 MIN

From ARC 42 to the Architecture Communication Canvas

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons

Common challenges in architecture documentation
01:52 MIN

Common challenges in architecture documentation

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons

How different teams use the architecture canvas
02:45 MIN

How different teams use the architecture canvas

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons

Common pitfalls when using the architecture canvas
02:36 MIN

Common pitfalls when using the architecture canvas

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons

Using the arc42 template for lightweight documentation
03:21 MIN

Using the arc42 template for lightweight documentation

Work efficiently with Architecture Decision Records (ADRs)

Fostering alignment and documenting microservices
03:45 MIN

Fostering alignment and documenting microservices

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons

Why documenting architectural decisions is crucial
06:39 MIN

Why documenting architectural decisions is crucial

Work efficiently with Architecture Decision Records (ADRs)

User feedback on the benefits of the canvas
05:04 MIN

User feedback on the benefits of the canvas

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons

Featured Partners

Related Videos

See all videos
Communicate efficiently with Software Architecture Diagrams
28:11

Communicate efficiently with Software Architecture Diagrams

Simon Lasselsberger

We (don't) need a software architect!?!
24:52

We (don't) need a software architect!?!

Hendrik Lösch

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons
27:56

42 x 2 Canvases Later: Two Years, Two Minds, Many Lessons

Benjamin Wolf & Dr. Gernot Starke

Move fast with Software Architecture
42:02

Move fast with Software Architecture

Simon Lasselsberger

It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design
43:13

It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design

Carola Lilienthal

Wardley Maps for Software Developers
29:35

Wardley Maps for Software Developers

Markus Harrer

There is no such thing as future-proof architecture! Here is how to prepare for it.
30:14

There is no such thing as future-proof architecture! Here is how to prepare for it.

Eberhard Wolff

Introducing a Digital Service Catalog for speed and scale
20:28

Introducing a Digital Service Catalog for speed and scale

Bastian Heilemann & Akash Manjunath

Related Articles

View all articles
Benedikt Bischof
Humanizing Your Documentation
About the speaker:Carolyn Stransky is a journalist, software engineer, conference speaker and technical writer based in Berlin. This is how she describes herself on her website:Majority of the week, I'm a frontend engineer focused on accessibility, d...
Humanizing Your Documentation
Daniel Cranney
The real reason we document our code
The world of software development moves fast. Technology is constantly changing, as are the tools we use with it, and even the role of a programmer is itself constantly in flux. However, some aspects of software engineering are so foundational that w...
The real reason we document our code
Daniel Cranney, Chris Heilmann
Dev Digest 215: Agent Memory, JS2026, Googlebot Analysis & Canvas❤️HTML
Inside last week’s Dev Digest 215 . 🗿 Make AI talk like a caveman 🧠 A guide to context engineering for LLMs 🤖 Simon Willison on agentic engineering 🔐 Axios supply chain attack post mortem 🛡️ Designing AI agents to resist prompt injection 🎨 HTML in c...
Dev Digest 215: Agent Memory, JS2026, Googlebot Analysis & Canvas❤️HTML

From learning to earning

Jobs that call for the skills explored in this talk.

Solution Architect

Solution Architect

Public Cloud Group GmbH

Remote
Azure
Linux
Software Architecture
Amazon Web Services (AWS)