Back
Fixing a pharma platform that was already 75% built
3 min read
Case study: Hawkeye, a pharma serialization platform

Fixing a pharma platform that was already 75% built

My role
Product Designer (contract)Audit, design system, IA, interaction design
Team
One of six designers, then the only oneWorked with POs, BAs, engineers, architects and QA
Timeline
May 2025 to Oct 2026, 18 monthsFirst release designed and in testing, about to ship
Redesigned Hawkeye interface: a data table, navigation, role permissions and activity charts

01Summary

I joined Hawkeye, a pharma serialization platform, when it was about 75% built. The brief was to make it look modern and leave the workflows alone.

The dated look came from deeper problems, so I fixed what sat underneath too: a new visual language, a rebuilt design system and redesigns of many workflows.

I started as one of six designers and ended as the only one. The first major release is designed and in testing with a few customers.

02The product

Every pack of medicine runs a relay

Before a pack of medicine reaches a pharmacy, it gets a serial number no other pack has. Then it’s boxed, stored, sometimes repacked, and shipped, scanned at every stop.

The journey of a pack of medicine, from serialization to pharmacy

Those scans prove a medicine is real. Hawkeye records them, across 30+ connected tools.

Hawkeye's connected tools

A warehouse worker with a scanner and a manager at a desk need very different things.

My job was to make the product behave the same everywhere, without making it worse for any of them.

03The full story

What’s inside the full case study

Hawkeye is under NDA, so the screens and the detail sit behind a password. Here’s a summary of what you’ll find.

  1. 01Where I joinedA brief to make it look modern, and why I pushed for more than a fresh coat of paint.
  2. 02The planHow I phased the work so each win earned the trust for the next.
  3. 03A new identityFive directions, one choice, and the design system fixes underneath.
  4. 04Redesigned workflowsThe everyday flows I rebuilt end to end, with the thinking and the before and afters behind them.
  5. 05One of six, then the only oneHow my role grew from one designer on a team to owning the product’s design.
  6. 06What shippedWhat testing showed, and where my part ended.