Lesson 5.2Lesson 5.2
Feedback that's useful vs feedback that's noise
Hearing the signal in what people say about your design
The hookYou show the family your concept and reactions pour in: 'I love it!' ... 'The kitchen feels small.' ... 'Can we add more storage?' ... 'My sister's house has a lovely island.' Six pieces in thirty seconds — and a beginner treats them all as equal instructions, producing a Frankenstein design pulled in six directions. They're not equal. One points at a real flaw. One is politeness. One is a solution hiding a need.
The feedback you get is not the feedback you need
People are unreliable narrators of their reactions, just as they are of their needs (Lesson 1.1 at the test stage). Feedback arrives as the tip of an iceberg, filtered through politeness, limited vocabulary, and the instinct to offer solutions. 'The kitchen feels small' is the surface; underneath might be 'circulation is cramped' or 'the upper cabinets feel oppressive.' Don't act on the words — dig for the need beneath. The feedback is data to interpret, never an instruction to obey. You're not a waiter taking an order; you're a diagnostician reading symptoms.
The four kinds of feedback
The real flaw — gold, a genuine problem even when mis-diagnosed ('the kitchen feels small' is a real signal something is wrong; the explanation may be incorrect); investigate the cause, don't obey the literal instruction. The solution-in-disguise — a need wearing a solution ('add more storage' hides 'storage for what?'); ask why, find the real need, solve that. Politeness — warmth, not data ('I love it!', especially where directness toward a professional feels rude, often covers a more honest critical reaction); probe past it. Personal taste / borrowed wants — 'my sister has an island' might be a real need or copying; weigh it against everything you know about them, and sometimes set it gently aside.
Separate the problem from the prescribed solution
The single most important move: trust the problem while questioning the solution. 'The kitchen feels small, let's knock down this wall' gives you a problem ('feels small' — usually trustworthy) and a solution ('knock down this wall' — usually not their expertise). Honour the problem and reconsider the solution: 'You're right it feels tight — let me look at why; it might be the cabinets or the lighting, not the wall.' The client is the world's leading expert on how the space feels to them; they're usually not the expert on how to fix it. Honour their diagnosis of the symptom; own the treatment.
How to draw out honest feedback
Ask about specifics, not the whole ('walk me through your morning here'). Give explicit permission to criticise ('I want to find the problems now, while it's cheap to change'). Watch reactions, not just words — the frown at the corner, the silence at the prayer space. And embrace the silence — the most honest reaction comes after the pause you didn't rush to fill.
The source matters as much as the content — Lakshmi on the prayer dais's comfort is near-unchallengeable signal (her body, her prayer); Lakshmi on a cantilever's feasibility is outside her domain. Route each piece to the circle it informs (desirability from users, feasibility from builders, viability from the budget) and weight it by whether the speaker owns that circle. Patterns beat individual voices — when three people independently stumble at the same corner, that convergence overrides any one articulate opinion. And protect against your own defensiveness — the flaw they found is a gift (you found it on paper, not in concrete); defending the design against its test is choosing your ego over the inhabitant's life. When criticised, get curious ('tell me more about that'), because the criticism that stings most often points at the realest flaw.
1. Show your design to two or three people and write down every reaction verbatim, including the vague and polite. Sort each into the four kinds. For each real flaw and solution-in-disguise, split the problem (trust it) from the prescribed solution (question it) and write the real need underneath. Note any reaction that repeated across people — your strongest signal. Then find the one piece of feedback that made you most defensive and write honestly whether it might point at a real flaw you don't want to see.
Check yourself
3 quick questions — pick an answer to see why.
Q1What is the 'master move' for feedback like 'the kitchen feels small, let's knock down this wall'?
Q2How should you treat 'I love it!' from a client who finds directness rude?
Q3Why do patterns in feedback beat individual articulate voices?
Key terms
- Solution-in-disguise
- Feedback that states a fix while hiding the real need beneath it — like 'add more storage' — requiring you to ask why and solve the underlying need.
- Feedback as data, not instruction
- The principle that people are unreliable narrators, so feedback is an iceberg-tip to interpret diagnostically, never an order to obey.
- Owning the circle
- Weighting feedback by whether the speaker has authority over it — desirability from users, feasibility from builders, viability from the budget.
We've tested against people — their bodies, routines, reactions. But there's a more brutal tester that gives no polite feedback: reality itself. The monsoon will come, the dust will blow, the power will cut, the knees will age. How do you stress-test against the unforgiving conditions of Indian life?