Jordan Ames

Taking projects from November 2026

Product designer / developer tools / Leeds and remote

I design the tools engineers open at three in the morning, when clarity is the only feature that matters.

Eleven years on dashboards, APIs, command lines and the first ten minutes of a product. I work with small teams who would rather ship something plain that works than something clever that nobody can read under pressure.

Now
Design lead, Kestrel CI
Before
Ferrous, Loam, Tallyhouse
Shipped
40+ releases to production

Selected work

Six projects from the last three years. Each opens as a short case study: the problem, what I did and what changed.

  • 01Kestrel CI2025

    Median time to find a failure fell from 4 min 10 s to 40 s.

  • 02Ferrous2025

    Support tickets about authentication fell by 31%.

  • 03Loam2024

    Teams that reached a first sync rose from 22% to 35%.

  • 04Tallyhouse2024

    Post-incident reviews took one meeting instead of three.

  • 05Brightwater SDK2023

    Two in three errors now end with the command that fixes them.

  • 06Pennant2023

    Trials with three or more people doubled, to 44%.

How I work

Four habits that have survived eleven years and a lot of production incidents.

  1. Sit with the person on call

    Before I draw anything I watch someone use the current tool for real, ideally during an incident. Most of the brief comes from that hour.

  2. Design in the real data

    Mock-ups use real log lines, real error text and real names that are far too long. Pretty placeholder data hides every problem that matters.

  3. Ship the plain version first

    The first release is the smallest change that fixes the problem. Polish comes second, once we know the change was right.

  4. Measure the before

    Every project starts by timing the task as it is today. Without that number, "better" is only an opinion.

About

I started as a front-end developer, which is why my designs come with notes on how to build them.

Since 2015 I have designed for teams that build infrastructure: build systems, payment APIs, observability and data tools. I like work where the user is an expert, the stakes are high and nobody reads the manual.

Outside work I teach an evening course on interface writing, and I am slowly restoring a 1970s road bike.

Experience

  1. 2024 to nowDesign lead, Kestrel CI
  2. 2021 to 2024Senior product designer, Ferrous
  3. 2018 to 2021Product designer, Loam
  4. 2015 to 2018Front-end developer, Tallyhouse

What people say

Jordan asked to join our on-call rota for a week before designing anything. The redesign that came out of it is the first one our engineers asked for more of.

Amara Lindqvist, VP Engineering, Kestrel CI

Every design arrived with the edge cases already drawn: the empty state, the error, the name that is 80 characters long.

Tomasz Brenner, Staff engineer, Ferrous

Tell me about the tool your team is stuck with.

I reply to every message within two working days. I take on two projects at a time, and the next opening is in November 2026.

What do you need?

A few sentences is plenty. Who uses the tool, and what do they get stuck on?

800 characters left

Demo page: nothing is sent.

Case study 1 of 6