Twenty years of design,
seven of those in fintech.
I'm Myles. I'm a product designer based in South London. I take complex problems in fintech, enterprise SaaS and data heavy platforms and turn them into interfaces that hold up under real use.
The shape of it
I started in 2005. The studio I founded then is still my company today. Twenty years of work runs through it. Branding, then web, then product, then enterprise SaaS, then fintech, then Web3, then AI. The thread is consistent. Find the messy bit. Workshop it. Reframe it. Ship something usable. Repeat.
The titles changed along the way. Designer became Senior Designer became Product Designer became Senior Product Designer became Principal Product Designer became UX Lead. The work didn't change as much as the title implies. The stakes got higher, the systems got bigger, the politics got thicker, but the job is still the same. Take something a human is trying to do and make it not feel terrible.
I am most useful in three places. Zero to one product design, where the brief is a vague problem and a slide deck. Dense data and complex workflow UX, where the wrong design choice makes the right answer invisible. Design leadership inside scale-up product orgs, where you have to hold the line on craft while shipping at pace.
Where I'm coming from
I split my career between two modes. Full time roles inside product organisations, embedded in delivery, building systems and teams. Independent work alongside, on retainer or short engagements, often for founders who need someone to set the bar and walk away.
The full time roles get the big credits. Oracle, Deloitte, Chainalysis, Gravicus, Titanbay, Edgefolio, ISB Global, ArchCo. The independent work is the muscle. Twenty years of "this is broken, fix it" calls.
I'm British, based in London, comfortable across timezones from California to Singapore. Most of my recent product work has been for European fintech but I've shipped product for clients on five continents.
How I work
Research led. I start with the people who'll use the thing. Workshops, contextual interviews, sketches on the wall. The right interface usually falls out of the right conversation with the right operator.
Systems minded. Components are cheaper than screens. The design system is not a deliverable, it is the operating contract between design and engineering. I treat it that way.
AI fluent. AI is part of my daily practice, not a side topic. Agentic coding, image pipelines, local self hosted models, automation that takes care of the boring. I'm shipping interfaces today that have AI in the loop. The discipline matters more than the headline.
End to end. I'm comfortable from a discovery workshop on day one to QA notes in the sprint that ships. The handover is not a wall, it's a window.
Three things always.
The principles that turn up across every engagement, every client, every era. They are unglamorous on purpose. The best product work is.
Teams
Good work comes from good teams. Whether leading or in support, the relationships matter more than the org chart.
- Communication
- Mentoring
- Problem solving
- Trust
- Cross functional
Design
Design is subjective until it isn't. I try to keep both sides honest. Empathy for the user, evidence for the decision.
- Empathy
- Collaboration
- Data driven
- Pixel perfection
- Documentation
Execution
Knowing where you are in the delivery process keeps the surprises to a minimum. I stay close from strategy to ship.
- Roadmaps and KPIs
- Stack alignment
- Asynchronous
- Quality assurance
- Analytics
Every role since 2017.
The current era of full time roles, plus the principal independent engagements alongside.