Mara Kestrel Booking from February 2027

7 min read

Designing for 3 a.m.

Most interfaces are designed at 11 in the morning by rested people. Some are used at 3 at night by exhausted ones. Here is what changes.

The person at the other end is tired

Fatigue narrows attention. A tired person reads less, scans more, and falls back on habit. They miss the third item in a list and the small grey text that explains the exception.

That is not a user failing. It is a condition, as real as low vision or a noisy room, and it can be designed for.

Put the next action first

At 3 a.m. nobody wants an overview. They want to know what to do next and how long they have. On Night Ward the most-used element was not the board of beds, but a plain list of the next sixty minutes, in time order.

If your product has a dashboard, ask what the person does after looking at it. Then consider showing that instead.

Nobody wants an overview at 3 a.m. They want the next thing.

Dark mode is not a style

For night work a dark theme is functional. Bright screens wake patients, ruin night vision and cause glare on glossy tablets. But dark themes are often designed last and tested least.

Design the dark version first if your product is used at night. Check contrast in both themes, and check it on the actual device in the actual room.

Make waiting a valid state

Many systems can only say “do this now”. Real work is full of things that can wait: a patient asleep, a delivery that is late but on its way. Give people a way to say “later”, record why, and stop asking.

Every alarm a system raises unnecessarily teaches people to ignore the next one.

— Mara

Reply by e-mail

More writing

The case for fewer alerts

Alert fatigue is a design problem, not a discipline problem. Four questions I ask before any notification ships.

6 min read Health · Process

Write the empty state first

The first screen most people see is an empty one. Designing it first makes the rest of the product clearer.

5 min read Process

Esc
Mara Kestrel
Work
Writing
About
CV
Speaking
Uses
Now
Contact
Night Ward A ward board for night-shift nurses that turns forty competing priorities into one calm list.
Tideline A public flood-warning service that shows how sure the forecast is, not only what it says.
Northline fares A fare finder that leads with the cheapest valid ticket and explains the rules in plain words.
Quire An accessible design system I maintain, where every colour pair ships with its contrast ratio.
Furrow An offline-first harvest log for small farms, designed for wet gloves and no signal.
Designing for 3 a.m. Most interfaces are designed at 11 in the morning by rested people. Some are used at 3 at night by exhausted ones. Here is what changes.
The case for fewer alerts Alert fatigue is a design problem, not a discipline problem. Four questions I ask before any notification ships.
Write the empty state first The first screen most people see is an empty one. Designing it first makes the rest of the product clearer.
Design tokens are a contract, not a palette A token named after a colour tells you what it looks like. A token named after a role tells you what it promises. Only one of those survives a redesign.
What a flood map taught me about uncertainty People trust forecasts more when you tell them how sure you are. Showing uncertainty is a design skill, and a public duty.
Switch theme
Turn margin notes on or off
Copy e-mail address hello@marakestrel.example
Print my CV

↑ ↓ to move · Enter to open · Esc to close