Complex systems design
I specialise in making complicated workflows feel simple. Most of my work has been in environments where the stakes are high and the users have no tolerance for confusion: government platforms, financial services, enterprise SaaS. I map how things actually work before I design how they should work.
Research and discovery
I ask a lot of questions before I touch a design tool. Stakeholder workshops, user research, workflow mapping; these aren't process steps I tick off, they're how I figure out what problem I'm actually solving. My case studies show what that looks like in practice.
Design systems
I've built and maintained design systems for regulated, multi-team environments. The goal is always the same: give engineers what they need to move fast without introducing inconsistency. I've seen what happens when systems aren't maintained; I design them to be used, not just documented.
Design leadership
I've worked with and guided junior and mid-weight designers across distributed teams. I bridge design, product, and engineering; not by sitting in meetings, but by making sure everyone is looking at the same problem.
Design-to-code workflow
I use Claude Code, Cursor, and Figma to prototype and contribute directly to codebases. This isn't a novelty, it closes the gap between what designers intend and what users get, and it makes me a more effective collaborator with engineering teams.
Where I've worked
Regulated, mission-critical platforms across government and civic technology, enterprise SaaS, and financial services. I know how procurement-driven adoption works, how legacy dependencies constrain decisions, and how to design for low digital literacy without dumbing things down.