01About02Builds03Writing
Work with me
27 Aug 20262 min read

Design for the person holding the day

In every small business there is one person the whole day rests on. Build around them and everyone else's work gets lighter.

Walk into a small clinic at ten in the morning and watch the front desk. Patients arriving, the phone ringing, a token to call, a payment to take, a doctor asking whether last month’s prescription came in. One person is keeping all of it in their head and in a notebook.

I once heard of a receptionist who lost that notebook. It held a week of the clinic’s money and visits, and it nearly cost them the job. Nothing about it was careless. The whole day had been written down in one place that could be dropped.

Who should a product be built around?

The obvious answer is the person who pays for it, or the person whose name is on the door. In a clinic that is the doctor. Most clinic software is designed from that chair, and it shows.

The better answer is the person whose day the product actually governs. In a clinic that is the front desk. On a house being built it is the owner on site, paying the crew in cash and keeping every bill. In a design studio it is whoever is chasing the approval and the invoice in the same week.

Build around that person and the others benefit without trying. The doctor sees last visit’s notes because the desk had somewhere to put them. The family at home sees what was spent because the owner wrote it down while the crew was still standing there.

How do you find them?

Sit in the room for a whole morning. Watch where the paper goes, who gets asked the questions, who stays late on Saturday adding up the week in a spreadsheet.

Then ask what they would stop doing if they could. What comes back usually sounds like relief: not having to write the same number twice, not having to answer the same question for the fourth time before lunch.

What changes when you design for them?

The interface gets quieter. The person holding the day has no time for a dashboard. They need the next thing, large, and the confidence that nothing behind it has been lost.

That is the work in both onrounds and Manekatti, and it is the first question I ask on any product brief. Whose afternoon is this going to change? If nobody in the room can name them, the product does not know what it is for yet.

I do my best work while it is still being decided.

A name, a product, the AI inside it: each is easiest to get right before launch.