Observation Is a Design Tool

The most important design tool we use isn't Figma. It's attention. Watching people use software — without intervening, without explaining, without defending our design decisions — is how we learn what's actually true about the product. Everything else is a guess.

Observation is hard for a specific reason: it requires you to do nothing. The instinct, when you watch someone struggle with something you made, is to jump in — to explain, to guide, to defend the decision that is failing in front of you. Every one of those instincts destroys the data. The moment you intervene, you are no longer watching the product; you are watching yourself.

Most design failures are observation failures. We designed for the user we imagined, not the user who exists. The remedy isn't better design taste. It's more time watching people struggle, and less time assuming we know why.

The gap between the imagined user and the real one is where products go wrong, and it is invisible from inside the team. You cannot reason your way across it, because the whole problem is that your reasoning is built on the imagined user. Only observation closes the gap — and only the kind that lets people struggle without rescue.

So the practice is deceptively simple: put the real thing in front of a real person, ask them to use it, and then be quiet. Watch where they hesitate, what they misread, what they never find. The discomfort of saying nothing is the price of learning what is actually true.