Before you build anything, ask: who is on the other end?

The question seems obvious. In practice, most people skip it. They start with what they want to make, what they want to say, what the deliverable needs to look like. The person receiving it is an abstraction: “users,” “audience,” “stakeholders.” The work gets built for a category, not a person.

Attunement starts with the specific. One person in front of you. What do they already know? What are they feeling right now? Where will they get stuck? What do they need from this moment that they can’t articulate?


I learned this on a dance floor before I learned it anywhere else. Late nineties, New York. Sasha and Digweed in the booth at Twilo on a Saturday night. The entire room moving as one system. The DJ reading the energy, knowing when to build, when to pull back, when the room needed a valley after a peak. The selection and sequencing weren’t random. Someone was doing this to a room full of people, deliberately, and the result was a shared somatic experience that nobody had to think about to be inside.

I learned it again in a classroom in Sunset Park. A kid named Eliar made a giant scene one day in the computer lab, loud enough to get himself written up. Everyone saw a behavior problem. I saw a kid pulling attention away from another student who was about to be humiliated. I told him I saw what he did. That moment built something between us because I read the room correctly and he knew it.

I learn it every night in the kitchen. Which kid had a hard day. Whose sensory threshold is lower tonight. Whether my son can handle the texture of the chicken or whether I need to reach for something else before he pushes the plate away.


Here’s the exercise. Pick something you’re building right now. A page, a product, a presentation, a meal. Before you make any decision about it, answer these questions:

Who is actually going to receive this? One specific person, not a category.

What do they already know about what you’re showing them? Start from their knowledge, not yours.

What are they feeling at the moment they encounter this? Rushed, curious, skeptical, depleted?

Where will they get stuck? What part of your work requires knowledge they don’t have, or attention they can’t spare?

What would make them feel like the thing was made for them, specifically, without anyone explaining it?


The answers change the work. A homepage designed for “visitors” is generic. A homepage designed for a specific recruiter who landed from a LinkedIn post, who has thirty seconds, who’s deciding whether this person is worth a deeper look, that homepage has different priorities. The hierarchy changes. The opening changes. What goes above the fold changes.

The exercise transfers to any medium. A prompt designed for “the AI” is abstract. A prompt designed for a system with a specific context window, specific attention characteristics, and specific failure modes at compound instructions is architecture.

Read the room first. Then build.