Proposed and shipped Race Tracker — a feature nobody asked for that became a platform staple.

Senior Product Designer · Gaming

THE SITUATION
I joined the tournament team at ZED Run with a backlog of micro-interaction improvements and a Figma workspace that needed sorting. The improvements were moving things, but the deeper I looked at tournaments, the clearer it became that the real problem was engagement and visibility — users couldn't track their horses, understand standings, or make smart race decisions.

WHAT I DID
I stabilised the workspace with a lightweight design system, worked through the backlog, then proposed something bigger: architectural changes to tournament visibility, including a Race Tracker that makes entry recommendations based on a user's stable and tracks progress over a week-long tournament window. I walked it through the business, ran testing sessions, refined the concept, and it went to build. When a market downturn hit and most of the company was let go, Race Tracker was already in build. It shipped and became a core platform feature.

OUTCOMES

• Race Tracker shipped and embedded as a core platform staple

• 30+ micro-interaction improvements delivered across the tournament experience

• New icon set and component library built with the Design Systems Lead

"It started as a proposal nobody had asked for. That's usually where the most useful work begins."