Distributed and Co-located Team Spaces

Physical and virtual team space design is tested as a deliberate PM decision, not background scenery. A well-designed space cuts down on the formal status meetings a team needs, because most small misunderstandings get caught and corrected informally, long before they turn into rework.

Osmotic communication — this is Alistair Cockburn's term for information that reaches team members "by osmosis," simply by being in earshot of a relevant conversation. A developer overhears a teammate debugging a shared module and jumps in before a mistake compounds — no meeting required. It's the single biggest advantage a co-located team has, and PMI expects you to recognize when a scenario is describing its absence.

Caves and commons — the standard co-located layout pairs a shared open "commons" area (for spontaneous conversation, pairing, and ambient awareness) with quiet "caves" nearby for focused, heads-down work. Neither alone is sufficient — an all-commons space kills deep work, an all-caves space kills osmotic communication.

Distributed teams need a deliberate substitute for both. An always-on video or audio link between subgroups recreates the "commons"; a shared, always-visible information radiator (a live dashboard, a shared build-status board) recreates the ambient awareness a shared office gives away for free. Chat channels function as a written commons, but they require someone to actually be watching them.

Pair programming and swarming seating — co-located teams that pair or swarm typically use adjustable desks, shared monitors, and side-by-side seating so two or more people can work one problem together without friction; distributed teams recreate this with dedicated pairing tools and low-latency screen sharing rather than generic video calls.

Study focus: when a question describes a distributed team missing informal cues that a co-located team would have caught automatically, the correct answer is almost always to recreate osmotic communication deliberately (always-on links, shared radiators) — not to add more formal, scheduled reporting.