Knowing your audience was never just about the end user

Many, many times, especially early in my career, I'd build a deck for a pitch, a client presentation, or a design review that I was genuinely proud of. I'd done the research, covered the data, crafted a clean narrative arc, beautifully designed the slides, a slide near the end that laid out the ROI so plainly a spreadsheet could have wept with joy. I would walk in convinced the logic alone would carry the room, certain I'd be walking out with a yes. But more often than not, I'd walk out with a "let's park this for now." Which is polite corporate for 'no'. The deck wasn't wrong. Logically, I wasn't wrong; I'd just built an argument for a person who doesn't exist in any boardroom I've ever sat in: someone who makes decisions purely on merit, with no fear of looking foolish, no territory to protect, and no boss of their own to answer to.

Dale Carnegie wrote it in 1936, long before anyone had a Figma file open in a client call: "When dealing with people, remember you are not dealing with creatures of logic, but creatures of emotion." Designers tend to apply that thinking to the person using the product and stop there. That's only half the job. The same law governs every conversation a designer has on the way to shipping anything: the junior you're critiquing, the client defending their gut instinct, the stakeholder guarding their roadmap, the exec deciding whether backing you makes them look sharp or exposed. None of them are creatures of logic either. They're just wearing different emotions to the meeting.

Junior designers aren't hearing your feedback; they're hearing a verdict on whether they're good enough. You can deliver a technically flawless critique, "this fails contrast guidelines, that hierarchy is unclear," and still watch someone shut down in front of you, because what they're actually processing isn't the feedback, it's whether they're about to be found out as a fraud. I've done this before, listing the issues as if I'm marking an exam, and the redesign came back worse and more timid. The logic was correct. The person on the other end of it wasn't logic-shaped.

Clients rarely reject the work. They reject the feeling of being overruled in front of their boss. I've sat across from a client pushing back hard on a decision I could defend with research and testing. A fairly watertight rationale, and realised halfway through that none of it mattered, because the actual problem was that my confident "here's why you're wrong" made them feel small in a room where they needed to feel capable, ideally in front of the one colleague they'd specifically brought along to watch them look capable. Once I started leading with what their instinct had got right before getting to what needed to change, the exact same recommendation landed. Nothing about the logic moved. Everything about the emotion in the room did.

The C-suite isn't weighing your argument; it's weighing its own exposure. An executive backing your proposal is quietly asking a question you'll never see on the agenda: if this goes wrong, how does it reflect on me? That's not cynicism; it's just what sitting at that altitude does to a person, and no amount of chart-based reassurance answers a fear rather than a fact. The pitches that land aren't always the most rigorous ones. They're the ones that make the decision feel safe, obvious, and somehow already theirs, ideally with a slide they can screenshot and forward to their own boss as evidence of vision.

Stakeholders defend territory, not tickets. Ask an engineer to rework a flow "because it's more logical," and don't be surprised when you get resistance dressed up as a technical objection. Nobody wants to hear that six weeks of their work is being reconsidered. Frame it as their expertise solving a real constraint rather than your idea overriding their build, and the "technical objection" has a funny way of resolving itself in an afternoon.

We'd never scope a project without researching the user. Most of us scope one without researching the room. Before kickoff, I'll happily spend a week understanding who the end user is, what keeps them up at night, what they've been burned by before. Then I'll walk into the first stakeholder meeting having done precisely none of that homework on the actual named humans I'm about to spend three months negotiating with. Who's the exec with something to prove this quarter? Who's the client who got badly let down by the last agency and is testing whether you're about to do it again? Who's the engineer who built that one module themselves and will hear "let's simplify this" as "let's throw out my work." That's not office gossip; it's the same discipline as a user interview, just aimed at the room instead of the interface, and it changes how you open every single one of those conversations before you've said a word about the work itself.

So what does this actually tell us? That "know your audience" isn't a soft skill you bolt onto good design thinking; it's the same skill, aimed in a direction most of us stop applying it a few metres too early. The brief doesn't end at the interface. It extends to every person you need on side to get that interface built, and every one of them is, infuriatingly and wonderfully, a creature of emotion first.

I still build the logical case. I just don't lead with it, and I don't mistake it for the whole job anymore. The research, the data, the narrative: all of it matters.

The room matters just as much. Usually more.