Listening to the Organisation

The first decision in building a brief is whose voices to gather, and the common mistake is to listen only upward. Leadership is essential - and we will come to why - but a workplace is used by everyone in the organisation, and the people who know most about how the work actually happens are very often not in the executive suite. A brief built from the top alone captures the vision and the budget but misses the texture: how a particular team really collaborates, where the current space fails every day, what the night shift or the client-facing staff or the new joiners need. So the rule is to listen both widely and deeply - across levels, teams, functions and working patterns - not just to the few who commissioned you.

Three groups matter in particular. Leadership sets the direction: the business goals behind the project, the culture the organisation wants, the appetite for change, the budget and the non-negotiables. Without a clear read of leadership vision you risk designing a lovely space that does not serve where the organisation is going - so this input is indispensable and usually comes first. Team leads and managers know how their groups actually work, who needs to sit near whom, the peaks and rhythms, the real pain points of the current space. The broader staff - the people who will live in the space daily - hold the ground truth: where they go to concentrate, where they cannot, what they wish existed, how they move through a day. Ignore them and you both miss vital information and, just as damaging, signal that their experience does not matter - which poisons the change before it begins.

There is a participation dividend here that is easy to underrate. Involving people in shaping their own workplace is not only a way to gather better information; it is the beginning of the change-management that determines whether a new office succeeds (Module 10). People accept and embrace a space they helped shape far more readily than one imposed on them. So 'who to listen to' is answered by: leadership for direction, managers for how work flows, and a genuine cross-section of staff for lived reality - gathered in ways that make people feel heard, because being heard is itself part of the design working.

Different questions need different methods, and a good discovery phase uses several in combination, because each reveals something the others miss. Stakeholder interviews - one-to-one or small-group conversations, especially with leadership and team leads - are where you get depth, candour and the things people will say privately but not in a crowd: the real tensions, the sacred cows, the quiet worry about the move. They are irreplaceable for understanding vision and nuance, and for building the trust the project will need. Come with prepared questions but follow the interesting threads; you are listening for the need beneath the stated want.

Workshops bring groups together to do something - map how they work, sort priorities, react to options, imagine the future office. Their value is twofold: they surface how teams think collectively and where they disagree, and they build buy-in, because people who shape ideas together own the outcome. A good workshop is structured and active - sorting cards, marking up plans, ranking trade-offs - not a meeting where the loudest person talks. Surveys reach everyone and give you breadth and a degree of quantification: what proportion find it too noisy to focus, how people rate the current meeting rooms, how many days a week they expect to come in, what they most want. They are cheap, inclusive and good for spotting patterns across a large population, but shallow - they tell you what and how many, rarely why - so they complement interviews and workshops rather than replacing them.

The craft is to triangulate: use interviews for depth, workshops for collective sense-making and buy-in, surveys for breadth, and look for where they agree and where they conflict. And crucially, this listening pairs with the hard evidence of the next lesson - what people say about how they use space and what the data shows are often different, and the truth usually lives between them. Two more disciplines matter. First, manage expectations honestly: asking people what they want raises hopes, so be clear that not everything can be delivered, or you breed resentment. Second, listen for the unspoken - the workaround that reveals a missing setting, the hesitation that hides a real concern. Good listening is active, structured and genuinely curious, not a box-ticking consultation.

Everything you gather has to be filtered through one essential distinction: needs versus wants. People, quite naturally, tell you wants - specific, often borrowed solutions: 'we want a ping-pong table', 'we need more meeting rooms', 'give us an open plan like that startup'. Your job is not to transcribe these into a shopping list but to find the need underneath each one, because the stated solution is frequently the wrong answer to a real problem. 'We need more meeting rooms' often means 'we can never find anywhere to talk without booking days ahead' - and the real need might be met better by easy unbooked huddle spaces than by more formal bookable rooms. 'We want an open plan' may express a genuine desire for more connection that open plan could actually worsen. The want is a clue; the need is the target.

This is one of the most valuable services a skilled designer provides, and it takes tact. You are not dismissing what people ask for - dismissing it breaks trust fast - but probing gently to understand the real problem, then solving that. The technique is to keep asking, in effect, 'what would that let you do?' or 'what is the problem you are trying to solve?' until you reach the underlying need. A loud, specific want that turns out to solve a minor real problem can be politely deferred; a quiet, barely-voiced frustration that turns out to block real work every day is a high-priority need, even though nobody demanded a fix. Sorting what you hear by *real impact* rather than *volume of demand* is the heart of it.

Leadership vision deserves the same treatment, with extra weight. A CEO's 'I want it to feel like a five-star hotel' is a want encoding a need - perhaps for a sense of care, or status, or a draw to bring people back - and your job is to understand that need and meet it appropriately, not to literally reproduce a hotel. Because leadership holds the direction and the budget, their needs carry particular weight, but they are still needs to be understood, not instructions to be copied. The output of this filtering is a prioritised, honest picture: the real needs ranked by impact, the wants understood and either addressed or gently set aside, and a clear-eyed view of what this organisation's workplace must actually do - which is exactly what the strategy and brief are built from.

Listening is only half the job; the other half is translation - turning everything you have heard into a workplace strategy and a written brief that will steer the whole project. A workplace strategy is the high-level direction: the handful of clear statements about what this workplace is fundamentally trying to do and be - for example, 'a destination that draws a hybrid workforce back for collaboration and culture, flatter than the current office, with serious focus provision and a social heart'. It is the through-line that keeps a thousand later decisions coherent, and it connects the workplace explicitly to the organisation's goals, so the project can be justified and judged.

From the strategy flows the brief - the more detailed, written statement of requirements that the design will answer and be measured against. A good workplace brief typically captures: the strategic goals and success criteria (how we will know it worked); the numbers (headcount now and projected, the mix of settings, approximate areas - treated as calibrated starting points, not fixed rules); the kinds of work settings required and the rough balance between them; key adjacencies and which teams must be near which; the cultural and brand intentions (Lesson 1.2); the special requirements - prayer and parent rooms, labs, confidential functions, accessibility commitments; and the constraints of budget, programme and the building itself. It is, in the language of architectural programming, the problem definition that design then solves.

Two disciplines make the brief actually useful rather than a document that gathers dust. First, it must be agreed and signed off - shared back with the stakeholders, confirmed as a true reflection of what was heard, and endorsed by leadership - so that it becomes a shared reference everyone is committed to, not the designer's private assumptions. This protects the project later: when priorities are tested or budgets squeezed, the agreed brief is what you return to. Second, it should stay honest about its numbers - every density, ratio and area in it is an illustrative benchmark to be calibrated against the real evidence of the next lesson and verified against current practice, not a rule copied from a book. A brief built this way - from wide and deep listening, honest needs-versus-wants filtering, and clear translation into strategy and a signed-off written document - is the single most valuable thing you can bring to a workplace project. It turns a vague wish into a testable intention, and it is the foundation everything in Modules 2 through 10 is built upon.