Caves & Commons Space Strategy

---

Origins

The phrase caves and commons comes from anthropologist Edward T. Hall and was adapted to office design by Alan Cooper in The Inmates Are Running the Asylum (1999) and later by Alistair Cockburn in his work on agile team rooms.¹ The framing crystallized a then-novel observation: developers and designers need both deep, uninterrupted solo focus and frictionless conversation with their team — and most office layouts get one at the expense of the other.

The closed-office of the 1980s gave caves but no commons. The open-plan of the 2000s gave commons but no caves. Neither produced the dual conditions creative knowledge work actually needs. Caves & commons is the design pattern that gives a team both, deliberately.

The Two Modes

Most knowledge work alternates between two modes:

• Focus (caves). Solo deep work — writing code, designing, debugging hard problems, thinking carefully about a decision. Requires uninterrupted blocks, low ambient noise, and a sense of not being watched.
• Collaboration (commons). Pairing, mobbing, refinement, ad-hoc problem-solving, casual knowledge exchange. Requires proximity, visibility, low-friction conversation, and shared surfaces (whiteboards, screens).

The mistake most workspaces make is assuming a person should be in one mode all day. The reality is that the modes alternate hour by hour, sometimes minute by minute. The space has to support the switch.

What the Pattern Looks Like

A well-designed caves-and-commons workspace has identifiable territory for each mode:

Commons (the team room)

• Shared desks or tables where the team works together.
• Whiteboards on multiple walls.
• Easily reconfigurable furniture — tables that can be pushed together, chairs that can rotate.
• Ambient sound is not silent. Conversation is expected.
• Visible artifacts: story walls, burn-up charts, team agreements.

Caves (focus rooms or zones)

• Small enclosed rooms — one or two people — for deep focus.
• Quiet zones in the larger space, with explicit "do not interrupt" signaling.
• Headphones-on areas where conversation is implicitly off-limits.
• Library norms: low light, low sound, no calls.

The transition zone

• Casual seating, coffee, snacks. Where impromptu conversation actually happens.
• Often the most valuable real estate in the entire space.

The Distributed Version

For remote and hybrid teams, the same principle applies but the space is virtual:

• Commons: always-on team voice channel (Discord, Tuple, Around) for casual presence; shared docs and boards for visible state; pairing tools for working together.
• Caves: calendar blocks marked as focus time; explicit "do not disturb" status; norms about asynchronous communication for non-urgent matters.
• Transition zone: a casual channel that isn't work-focused; team rituals (virtual coffees, watercoolers) that don't require an agenda.

The translation is imperfect — virtual commons does not match the bandwidth of physical commons — but the same dual-mode design principle holds.

Common Failure Modes

• All commons, no caves. The classic open-plan failure. Everyone is interrupted constantly; focused work happens at home or after hours.
• All caves, no commons. The classic enterprise floor with cubicle walls. Conversation is friction-heavy; collaboration migrates to scheduled meetings.
• No norms about mode-switching. Even with both kinds of space, if everyone defaults to the same one, the other goes unused. The team needs explicit signals — headphones, status indicators, "in the cave / in the commons" language.
• The caves are status symbols. If only senior people get the enclosed rooms, the format reinforces hierarchy instead of work-mode. Caves should belong to whoever needs focus, not to whoever has the title.
• The commons becomes a noise zone, not a working zone. If the commons is full of phone calls and unrelated chatter, it stops being collaborative and becomes just loud. Active management of commons norms matters.

The Underlying Pattern

The caves-and-commons pattern is one specific case of a more general principle: environments shape the work that happens in them. A room with whiteboards on every wall produces more drawings than a room with none. A space without enclosed rooms produces fewer hard-thinking sessions. The pattern asks teams to be intentional about what behaviors their space encourages and discourages — and to design for both modes of the work, not just one.

Coaching Tips

Audit your current space.

Walk through. Count the caves. Count the commons. Most teams discover they have a lot of one and none of the other.

Make mode-switching visible.

Headphones-on, hand-raise, do-not-disturb signals. Norms around "I'm in the cave" let teammates respect focus without checking.

Don't let the commons become loud.

Active conversation is fine; phone calls and unrelated chatter aren't. Norms about what belongs in the commons matter.

Invest in the transition zone.

Where the team meets accidentally is where most cross-pollination happens. Coffee, snacks, comfortable seating — small investments, big effect.

Translate the pattern remotely.

Always-on voice channels for commons, calendar blocks and DND for caves, casual non-work channels for transition. Same pattern, different medium.

Watch for caves-as-status.

If the enclosed offices are only for managers, the format has been hijacked. Make caves available based on work mode, not title.

Summary

Caves and commons is a small, specific design pattern with disproportionate effects on how a team works. By designing space for both modes of work — focused solitary thinking and easy collaborative exchange — and by making the transition between them explicit, teams remove much of the friction that one-mode workspaces inadvertently impose. The pattern translates to physical, hybrid, and fully-remote contexts with minor modification: the underlying principle is that environments shape behavior, and that knowledge work needs two different environments to do its best.

Back to Guided Collaboration