Distributed Architecture Workshops: Making Remote Collaboration Work

When every client engagement went remote in 2020, the conventional wisdom was that architecture workshops couldn't work distributed. Whiteboarding, sticky notes, the informal hallway conversation that unblocks a stalled decision — these were supposedly impossible via video call. We disagree. Distributed architecture workshops can be as effective as in-person ones, but they require deliberate design.

The Three Things That Break in Remote Workshops

First: diverging attention. In-person, you know who's engaged. Remote, you don't. Our fix: no passive observers. Every participant has a defined role and deliverable during every session segment. If someone doesn't have something to contribute to a specific activity, they don't attend that segment.

Second: decision quality. Remote workshops surface agreement more easily than disagreement. People are less likely to challenge a decision on a video call than in a room. We use structured decision protocols — Roman vote, anonymous confidence scoring via Miro — that surface dissent explicitly.

Third: documentation lag. In-person workshops produce a whiteboard photo. Remote workshops produce... a Miro board that nobody looks at again. We built a workshop closing ritual: the last 20 minutes of every session are spent documenting decisions, actions, and open questions into the project ADR log in real time. This prevents the "we decided something, but nobody remembers what" failure mode.

Our Distributed Workshop Stack

Miro for visual collaboration (C4 diagrams, capability maps, dependency mapping), Teams/Zoom for video, Confluence for structured documentation, and GitHub for ADRs. The most important tool is the pre-work async brief: every workshop participant receives a 2-page brief explaining what will be decided, what information they need to bring, and what the workshop will not cover.