Currently: Lead Product Designer @ Reviver
Designing Tools That Turn Noise Into Signal
I'm Hayden, a product designer who turns messy workflows and dense data into interfaces people actually want to use. I've led design end-to-end across automotive, e-commerce, education, and agency teams: research, systems, and shipped outcomes that move the metrics that matter.
Several of those projects ship with AI built into the product. I designed, managed, and shipped those flows myself, and I use AI in my own process to speed up handoff and cut back-and-forth with engineering.
Companies I've worked with
SAM
Case studies from the field
Real products, real constraints, measurable outcomes. Each project below breaks down the problem, my process, and the results.
Reviver Design System
Reviver had UI elements, not a design system. I led the initiative to build one source of truth: shared tokens and a component library that RFleet is built on end to end.
Plate Workout Tracker
My training program lived in a note that couldn't track progress. I designed, built and shipped an app that runs it and raises my targets automatically.
Fleet Dashboard & Registration Management
Fleet compliance work that scaled with every vehicle added, until shift-start paperwork dropped from 89 minutes to 9.
Amazon FBA Seller Onboarding
Sellers were stalling out before they ever connected an account. Redesigned around real competitor research, seller outreach, and usability testing.
Skills & Tools
Strategy & Research
Design Execution
Collaboration
Experience
Your Questions, Answered
The questions hiring managers and collaborators usually ask first.
Complex, data-heavy B2B products: fleet management, onboarding flows, and internal dashboards, where the real challenge is turning dense operational data into clear, actionable interfaces. Recent work spans automotive fleet tech, e-commerce automation, and AI-guided analytics.
Four phases: Define (align on the real problem with research and stakeholders), Ideate (sketch and flowchart multiple directions), Design (low-fi to high-fi in Figma), and Validate (usability testing before handoff). I stay close to engineering throughout so what ships matches what's designed.
Yes, it's built into the process, not outsourced. For Mayan I ran surveys and interviews with 40 sellers before touching a wireframe; for the Reviver dashboard I worked directly from support tickets and fleet manager interviews. I'd rather validate a hunch with a handful of real users than debate it in a meeting.
As an embedded design lead, not a downstream resource. I partner with PMs to scope what's actually feasible, and with engineers early to understand technical constraints before designing around them. That's how projects like the Reviver dashboard shipped in two weeks with a single engineer.
RFleet, Reviver's fleet operations platform. Clerical cost was scaling directly with fleet size, and shift-start compliance work was eating up to 89 minutes per batch. I rebuilt it as a single platform across nine modules, which cut that to 9 minutes and flattened the cost curve by 92% as fleets grow. It's live, running on real customer fleets today.
I lead with business outcomes, not just interfaces. Every case study on this site ships with a measurable result, because I treat design as a lever for the metrics leadership actually cares about: activation, support load, compliance, conversion.