BitMEXDesign leadership

From pixel polish to product partner.

Rebuilding a design culture in a year, from one junior designer chasing a moving target to a respected team that shapes what gets built, and an AI-ready foundation to scale it.

Role
Head of UX
Timeline
Dec 2024 – Mar 2026
Scope
Exchange trading terminal, design culture
Leadership
Team, process, design system

Overview

A new terminal needed a new way of working.

As Head of UX at BitMEX, I led the redesign of the exchange trading terminal, keeping the grassroots community spirit that made BitMEX great. Underneath that redesign was a bigger job: changing how design worked with the business and with engineering.

Problem

Design was decoration, added at the last minute.

When I arrived there was one junior UX designer. Design was seen as the team that made UIs look pretty, tapped on the shoulder at the 11th hour to polish what had been built over months around what the business thought users wanted.

Requirements moved constantly, and it was taking on average three sprints for development to meet requirements and expectations.

Fail
We love product design, you guys make our UIs look pretty. It's great we can tap you on the shoulder at the 11th hour.
The business, Q1. Design seen as decoration, brought in at the last minute.

Research & Discovery

Design it first.

I introduced a "let's design it first" policy: clear requirements extraction, design, consideration of technical constraints and validation with users, all before any code is cut.

ExtractClear requirements from the business
DesignWorkflows built around how traders really work
ConstrainTechnical constraints considered early
ValidateTested with users before build
Build togetherDesigner and developer, hand in glove

Design Approach

I said no to UX handovers.

Beautiful documentation, annotated workflows, design tokens and interactive prototypes can still produce a coded result that is wildly wrong. "Here's the spec, see you in two weeks" is passing the buck.

Instead, designers work hand in glove with developers, with frequent check-ins to correct designs before they go rogue.

33%average saving in dev sprints after introducing "design it first"
3sprints, on average, it used to take to meet requirements

Rapid Prototyping

"Can't we just use AI?" Of course. Foundations first.

AI can speed design up, but only if the agents are trained on the right context and a human stays in the loop as a quality gate.

So we made the design system and mockups of key areas of the platform AI-ready: machine-readable, full of context and connected to code. A robust, well-documented design system and a Storybook holding component variants alongside wikis of contextual knowledge made that possible.

Machine-readableDesign system and key mockups structured for AI agents to read and use.
Connected to codeStorybook component variants linked to the design system.
Human in the loopA design quality gate on everything the agents produce.

Growing the Team Leadership

"Why does my trade ticket look like a hotel booking form?"

Unless you've seen an analyst or trader setup, been on a trading floor or really understand the lifecycle of a trade, you'll probably build a sparse, whitespace-heavy, best-practice hotel booking form. Those best practices come from retail users, not a fast-moving market persona where every second can mean hundreds of thousands of dollars in price movement.

So I hired designers who understood that culture and didn't need hours of explanation to see the world through a trader's eyes. Together we re-skilled the team around a new, consistent and responsive design ecosystem.

Win!
We love you guys. We need to increase our trade volumes. Can you run a workshop to find the pain points in our current workflows? We had a great time in the last one you ran!
The business, Q4. Design trusted to shape what gets built.

Outcome

Mutual respect. Efficient delivery. Better accuracy.

33% saved in dev sprintsAn average saving across dev sprints with a design-first process.
The glue of the product teamDesigners sit between product managers and developers, not after them.
Validated before codeTechniques to extract requirements efficiently and test with users first.
AI-ready foundationsA documented design system and Storybook connected to code, with a human quality gate.