Lesson 1.1

Design Thinking/Module 1 · Empathise — reading the inhabitant

Lesson 1.1

The brief is a lie

What clients say vs what they actually need

6 min Lesson 5 of 32

The hook
A client says 'I want a bigger kitchen.' Three questions later you learn her kids do homework at the dining table while she cooks and she feels cut off from them for two hours every evening. She doesn't need a bigger kitchen. She needs to not be alone while she cooks. Different problems — and she'll never say the second sentence aloud.

Why 'the brief is a lie' — and why it's not an insult

The client isn't deceiving you; they're handing you a solution dressed up as a need — usually the first, most expensive, often wrong one. This happens because people speak in solutions not problems, don't know what's possible (so ask for more of what they have), can't access their own emotional needs, and give the socially acceptable version ('a guest room' can mean 'space so my mother-in-law and I stop fighting').

The three layers, and the five whys

Beneath the stated request is the real need, and beneath that the deep driver. The deeper you dig, the more — and better, and cheaper — design answers you earn. The tool is the 'five whys': take the stated request and ask why, gently, until you reach something emotional or fundamental.

Worked example: 'I want a separate formal living room for guests.' Why? — the house should look proper. Why does that matter? — people judge a family by their home. Why is that important to you? — I don't want my in-laws to think we've 'come down.' The real driver is respect and status — which can be satisfied without building a dead formal room used 360 days a year for being looked at.

Digging is not overruling

'The brief is a lie' does not mean impose what you've decided is their real need — that's arrogance wearing empathy's clothes. Some statements are surface wants to improve past; others are bedrock values and constraints to build around (a pooja orientation may be non-negotiable). Empathy is the skill of telling which is which. After digging, the client should feel more understood, not overruled.

Worked example: the Hubballi 2BHK, revisited

Designer B from Lesson 0.1 treated 'modern, Instagram-worthy' as the tip of the iceberg and went diving — uncovering the unstated brief: a compact room that flexes between a young couple's aesthetic life and a dignified space for elderly parents two months a year. The client never said that sentence. B excavated it.

The five whys descends from the stated request to the real need to the deep driver. Most designers stop at the top layer.

Go deeper — for practitioners & students

A formal distinction underlies this: need vs want vs constraint. A need is a problem that must be solved for success (the mother must not feel cut off). A want is a preferred solution (a bigger kitchen; marble) — negotiable, improvable. A constraint is a fixed boundary (budget, plot, pooja orientation). Beginners treat everything as a need and freeze; experts sort each statement into one of the three buckets. Much of what looks like talent in brief-taking is disciplined sorting — and the five whys is the tool that does it.

Try it

1. Catch a stated request (from family, friend, or yourself). Ask why at least three times. At the stated layer write the one obvious answer; at the deepest layer write three different answers that satisfy the real driver. Then label each thing you heard as need, want, or constraint.

Check yourself

3 quick questions — pick an answer to see why.

Q1A client says 'I want a separate formal living room for guests.' Using the five whys, the designer reaches 'I don't want my in-laws to think we've come down.' What does this reveal?

Q2Why is the phrase 'the brief is a lie' NOT an insult to the client?

Q3In the need/want/constraint framework, which statement is a constraint?

Key terms

The five whys: A questioning tool that takes a client's stated request and gently asks 'why' repeatedly until it opens into the real need and the deep driver beneath it.
Need vs want vs constraint: A sorting framework where a need is a problem that must be solved, a want is a preferred (negotiable) solution, and a constraint is a fixed boundary like budget or pooja orientation.
Digging is not overruling: The principle that excavating a client's deeper need means understanding them more fully, never imposing the designer's own idea of what they 'really' want.

Recap

The brief is the tip of an iceberg — a solution dressed as a need, shaped by what the client can picture, articulate, and is comfortable saying. Get below the waterline with the five whys: ask why until the stated request opens into the real need and deep driver. But digging is understanding more deeply, never overruling — empathy is the skill of telling a want to improve past from a bedrock need or constraint.

Carry forward →

If the most important brief is the one never said aloud, and you can't just ask 'what do you really need?', how do you run the conversation — what do you ask, and what do you watch?