How People Actually Work

Strip a working day down and almost everything people do falls into one of four modes, each with a distinct spatial need. Focus is concentrated individual work - writing, coding, analysis, reading - the demanding, heads-down thinking that needs quiet and a stretch of uninterrupted time. Collaboration is making something with others - the meeting, the whiteboard session, the quick huddle, the pair working through a problem - high-bandwidth, often noisy, and impossible to do well in dead silence. Learning is how people absorb a job and an organisation - watching how a senior colleague handles a client, overhearing how a problem gets solved, asking the small questions you would never put in an email. Much of it is informal and happens by proximity, which is exactly why it collapses when everyone is remote or scattered. Socialising is connection and belonging - the coffee, the lunch, the five minutes of genuine conversation that build the trust every other mode runs on.

These modes are not a ranking, and they are not alternatives. A healthy day uses all four, and they depend on each other: collaboration goes better between people who have socialised enough to trust one another; focus work is sharper when the learning and collaboration around it keep a person oriented. The mistake a floor plan makes is to assume one mode - usually focus, the desk - and treat the rest as interruptions to be minimised. In reality the 'interruptions' are often the highest-value work the office exists for.

The design consequence is direct and it runs through this whole course: a workplace must offer a setting that fits each mode. A wall of identical desks serves focus passably and the other three modes badly - so collaboration spills noisily across the open floor, learning thins out, and socialising has nowhere to land. The goal is not to pick the 'right' mode but to give every mode a good home, and to make moving between them easy. Before you count desks, count modes.

The second truth is that nobody spends the day in one mode. A real knowledge-work day is a braid: a block of focus, a meeting, a learning moment, a call, lunch, another meeting, a last push of focus. People switch modes many times a day, and each switch has a cost. When someone is interrupted mid-focus, research on attention suggests it takes a surprisingly long time - often many minutes - to fully re-immerse in the demanding task they left. Do that a dozen times a day and a large fraction of the available thinking time is spent not thinking but re-starting.

This reframes what 'productivity' means spatially. It is not about packing the most desks onto a floor; it is about reducing the friction of the day - making each mode easy to do well and the switch between modes cheap. Two failure patterns dominate real offices. The first is the all-open floor where there is nowhere to concentrate, so focus work is done in a haze of ambient conversation and notification, and the deep tasks either get taken home or done badly. The second is the over-celled floor where collaboration is expensive - you have to book a room, so the quick two-minute huddle that should just happen never does, and decisions slow down.

Good design holds the tension rather than resolving it in one direction. It offers genuinely quiet places for focus AND easy, unbooked places to collaborate, close enough together that moving between them is a few steps, not a trek to another floor. It accepts that the office is a noisy, social, collaborative instrument by nature - so it protects focus deliberately, with enclosed rooms and quiet zones, rather than pretending the open floor can be silent. The aim is a day where a person can drop into deep work, surface for a ten-minute huddle, take a call, grab a coffee and get back - without friction taxing every transition. When you study an office, watch the switches: where they are smooth, and where the building is fighting the day.

Cutting across the four modes is an older axis: how much of the work is individual and how much is collective. Different roles and different organisations sit in very different places on it. A team of researchers or writers may be seventy per cent heads-down focus; a design studio or a trading desk may be the reverse, alive with constant exchange. A software team swings between intense solo focus and intense pairing within the same hour. There is no universal right answer, which is exactly why you cannot design from a template - you have to learn the real balance for the real people.

The collective side of work depends heavily on proximity and visibility. Teams that sit together coordinate almost for free: a glance tells you someone is free, a question is answered without a calendar invite, a junior person learns by being in earshot. Pull those people apart - onto different floors, into distant zones, or home on different days - and that cheap coordination is replaced by expensive, scheduled, lower-bandwidth substitutes. This is why who-sits-near-whom (the subject of adjacencies in Module 2) is one of the highest-leverage decisions in a plan, and why it must follow the real lines of collaboration, not the org chart or the politics of who gets the window.

There is a balance to strike and it is genuinely hard. Too much proximity and the floor is so interactive that nobody can concentrate; too little and the team fragments into isolated individuals who happen to share an employer. The craft is to cluster the people who truly need each other close, give that cluster its own quiet and collaborative settings, and separate clusters that do not interact so one team's buzz is not another team's distraction. Notice, too, that individual focus work is the mode most portable to home - which is precisely why the in-office day increasingly tilts toward the collective modes that proximity makes possible. Understanding the individual-versus-team balance of your real users tells you how much of the floor should be desks at all, and how it should be clustered - the first real input to a plan.

All of this leads to the cardinal rule of Module 1: understand how people actually work before you draw anything. It is tempting, and common, to start from a layout - a desk grid, a standard ratio of meeting rooms, a template from the last project - and then ask people to fit into it. That is designing backwards. The layout is the answer; the real pattern of work is the question, and you cannot get the answer right if you never asked the question.

What does 'understanding the pattern' mean in practice? It means learning, for this specific organisation, the mix of modes across a typical day and week; the individual-versus-team balance by team; how much focus work really happens in the office versus at home; where collaboration clusters; how people move; and where the current space fights them. Some of that comes from listening to the organisation (Lesson 1.3) and some from measuring how the space is actually used (Lesson 1.4) - the two halves of evidence that this module is built to gather. The danger to guard against is designing for the idealised day rather than the real one - the tidy picture of everyone at focused desks, rather than the messy, social, mode-switching truth.

The pay-off is large. When the layout grows out of the real pattern of work, it feels, to the people using it, as though the building understands them: there is a quiet place when they need to think, somewhere easy to grab a colleague, a sense that the space is on their side. That feeling is not luck or lavish budget - it is what happens when design starts from people and what they do, and lets the plan follow. So this is where the course plants its flag: people first, desks last. Every later module - standards, settings, acoustics, hybrid - is in service of supporting the real modes of real people through a real day. Get the pattern right, and everything downstream gets easier.