Product designer & design engineer, Edinburgh

I design calm software for hard jobs.

calm: fewer alarms, clearer next steps. hard jobs. night shifts, floods, rush hour, harvest.

I’m Mara, an independent product designer who also writes the front-end code. For twelve years I’ve worked on tools people use under pressure, and I think they deserve the same care as anything sold in a shiny shop.

Now: designing a rota tool for community nurses

Selected work

Three projects, three hard jobs

Each one started by watching the work, not by opening a design tool.

01Health · 2025

Night Ward

A ward board for night-shift nurses that turns forty competing priorities into one calm list.

Role
Lead product designer, front-end prototypes
Client
Corrie Bay Hospitals (sample client)

22 → 14 min average handover time

Read the case study: Night Ward
  1. a moon, not an alarm: obs can wait till 4
  2. one list, in time order. no hunting
  3. the clock that matters at 3 a.m.

02Climate · 2024

Tideline

A public flood-warning service that shows how sure the forecast is, not only what it says.

Role
Product designer and front-end lead
Client
Port Ellery Council (sample client)

3× more residents signed up for alerts

Read the case study: Tideline
  1. a range, not a false-precise number
  2. hatching still reads in greyscale
  3. the action word comes first

03Transport · 2023

Northline fares

A fare finder that leads with the cheapest valid ticket and explains the rules in plain words.

Role
Senior product designer (contract)
Client
Northline Rail (sample client)

+18% off-peak tickets bought

Read the case study: Northline fares
  1. lead with the answer people came for
  2. rules in plain words, not fare codes
  3. offered, never forced

How I work

From the night shift to the shipped code

  1. Watch the work

    Shadow shifts, ride along, read the call logs. The real product is usually a paper list in someone’s pocket.

  2. Sketch in the open

    Rough sketches on the wall where the team works, so nurses and drivers correct them before they harden.

  3. Prototype in code

    Real prototypes on real devices from week three, tested where the work happens: wards, platforms, fields.

    I bring the code, not just the screens.
  4. Measure the calm

    Fewer alerts, shorter handovers, fewer wrong tickets. Numbers the people doing the job care about.

Writing

Notes from the margin

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.

7 min read Health · Accessibility

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

Kind words

What people say about working together

  • Mara spent a week of nights on our wards before she drew a single screen. The nurses noticed, and so did the result.

    Director of nursing, a hospital group

  • She writes the code for her own designs, which means the details survive the hand-off. There is no hand-off.

    Engineering manager, a rail operator

  • Calm, clear and very hard to argue with, because everything comes with evidence.

    Head of resilience, a coastal council

Sample quotes, written for this template.

Next talk 19 November 2026 Calm by default Interface North 2026 · Newcastle All talks and workshops →
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