The six conditions the office gave you for free

Sharing a space did quiet work no one wrote down. It coordinated through overheard conversation, surfaced recognition in the corridor, built trust in small reliable moments, manufactured belonging at the coffee machine, grew people by proximity, and paced the day by the simple fact of leaving. None of it appeared on a plan — so when a team goes distributed, the loss registers as a vague fraying rather than a missing system.

The reframe in Working Apart, Performing Together is blunt: distributed teams do not have a culture problem so much as a missing operating system. What the building did for free, you now have to do on purpose.

Each condition can be strong or threadbare independently, and treating the wrong one wastes the effort. A team low on trust is not helped by another social call; a team starved of recognition does not need clearer process. The figures below are illustrative of a common profile, not a measured average — the point is that the conditions move separately, so they have to be read separately.

Two conditions tend to thin first and complain least. Good work that no one sees stops feeling like good work, so recognition has to be engineered to replace the noticing the corridor used to do. And remote work erodes the boundaries that once paced a day, so always-on becomes the norm and the best people burn first. A distributed team that designs for everything except sustainability is building a sprint it can survive rather than a rhythm it can hold.