How I work
From the first question to the shipped interface.
Teams bring me in when the product is complex, the users are experts and getting it wrong is expensive. I lead the design end to end and stay hands-on throughout.
What I offer
-
Embedded design lead
I join your product team as a staff or lead designer and own a product area: working in your rituals and tools, partnering closely with product and engineering, and raising the bar for the designers around me.
-
Zero-to-one concepts
When the problem is still fuzzy, I run focused sprints that turn it into a direction the team can commit to: research, a clear concept and a prototype people can actually use, in weeks rather than quarters.
-
High-stakes interfaces
Ground control, order entry, in-car systems: dense, real-time interfaces where a mistake is expensive. I design for the expert under pressure, then prove it holds up with the people who will use it.
Process
- 01
Understand
I start with the people who will use it and the constraints around them: operators, stakeholders, the data, the hardware, the regulations. The goal is to find the decisions that really matter.
- 02
Frame
A clear point of view on the problem, what success looks like and what we will leave out. Flows and rough concepts go in front of the team early, so we argue about the right things.
- 03
Prototype
Working, high-fidelity prototypes with realistic data, often built in code, in front of real users as soon as possible. A prototype settles in a day what a meeting can’t settle in a month.
- 04
Ship
Specs, components and design system work engineers can build from directly. I stay close through release to keep the details intact, then measure what changed.
Have something with a lot riding on it?
A quick intro: tell me what you’re building and we’ll see if it’s a fit. Prefer email? paul@paulz.design