First Designer
Why I Wrote "First Designer”
Earlier this year, I was sitting in a job interview when I was hit with a question I didn't have a real answer for. It wasn’t about typography, user research, or Figma components. It was a question of brutal maths:
"We have twenty-seven engineers. They all want design work done. How do you manage that?"
Like any seasoned designer, I gave the corporate-acceptable response: rigorous prioritisation, strict triage, and learning to say no.
But on the commute home, the truth set in. That answer was a reactive lie. Under a 27-to-1 ratio, traditional design processes don't just bend—they completely disintegrate. If you try to work the traditional way, you quickly become a burnt-out, bottlenecked design vending machine.
I wrote First Designer because I needed a better answer.
Designing When You're Outnumbered
This book is a distillation of over nine years spent shipping digital products at FTSE 100 companies and complex technical organisations. It’s written specifically for solo designers, small teams, and heads of design operating in environments where engineering massively outweighs design.
Instead of treating design as a reactive creative service, this book is about building systems that protect your time and scale your impact. It covers the exact frameworks I use to survive and thrive when outnumbered by development teams:
The Demand Routing Layer: A 3-tier traffic protocol to decide what deserves your deep, bespoke attention, what can be decentralised, and what can be automated via engineering self-service.
The Quality Supply Chain: Structural methods to bake design tokens and intent directly into the development pipeline, ensuring quality persists even when you aren’t in the room.
Knowledge Infrastructure: A lightweight system to ensure user insights route automatically into engineering decisions without turning you into a meeting-room bottleneck.
The 90-Day Deployment Playbook: A step-by-step roadmap to move from day-one overwhelm to an optimised, respected engineering partnership.
Stop Trying to Outwork the Queue
You cannot outwork a massive engineering department through sheer effort. It’s time to stop reacting to the chaos and start building the operating environment that routes the demand, buys back your time, and permanently embeds design into the engine room of the business
Why I Wrote "First Designer”
Earlier this year, I was sitting in a job interview when I was hit with a question I didn't have a real answer for. It wasn’t about typography, user research, or Figma components. It was a question of brutal maths:
"We have twenty-seven engineers. They all want design work done. How do you manage that?"
Like any seasoned designer, I gave the corporate-acceptable response: rigorous prioritisation, strict triage, and learning to say no.
But on the commute home, the truth set in. That answer was a reactive lie. Under a 27-to-1 ratio, traditional design processes don't just bend—they completely disintegrate. If you try to work the traditional way, you quickly become a burnt-out, bottlenecked design vending machine.
I wrote First Designer because I needed a better answer.
Designing When You're Outnumbered
This book is a distillation of over nine years spent shipping digital products at FTSE 100 companies and complex technical organisations. It’s written specifically for solo designers, small teams, and heads of design operating in environments where engineering massively outweighs design.
Instead of treating design as a reactive creative service, this book is about building systems that protect your time and scale your impact. It covers the exact frameworks I use to survive and thrive when outnumbered by development teams:
The Demand Routing Layer: A 3-tier traffic protocol to decide what deserves your deep, bespoke attention, what can be decentralised, and what can be automated via engineering self-service.
The Quality Supply Chain: Structural methods to bake design tokens and intent directly into the development pipeline, ensuring quality persists even when you aren’t in the room.
Knowledge Infrastructure: A lightweight system to ensure user insights route automatically into engineering decisions without turning you into a meeting-room bottleneck.
The 90-Day Deployment Playbook: A step-by-step roadmap to move from day-one overwhelm to an optimised, respected engineering partnership.
Stop Trying to Outwork the Queue
You cannot outwork a massive engineering department through sheer effort. It’s time to stop reacting to the chaos and start building the operating environment that routes the demand, buys back your time, and permanently embeds design into the engine room of the business