People often ask about my design process. I understand why, because process feels like something you can copy and apply. The truth is that after more than twenty years in design, I have learned that process is not a template. It is a way of thinking, a way of noticing, and a way of understanding the problem in front of you.
My work spans service design, product strategy, research, interaction design, and AI-driven experiences. When you operate across that range, you realise your process needs to be structured enough to create alignment and flexible enough to deal with reality. So this is not a linear framework. This is how I approach design in the real world.
1. Start with context, not wireframes
Before anything else, I look at context. What is the organisational reality. What constraints shape behaviour. What does the market expect. What is the team actually capable of delivering.
Good design does not start in Figma. It starts with understanding what success looks like for the business and what it feels like for the people using the product. That combination shapes every decision that follows.
2. Ask better questions
Strong design comes from strong questions.
Why this problem. Why now. Why does it persist. Who benefits if we solve it. Who loses. What assumptions are we carrying from past work. What could we remove instead of add.
My process is built around reframing. Because once the problem is framed clearly, the design almost always becomes simpler.
3. Research to understand the “why”
I lean heavily on research, but not for the sake of documentation. I research to understand behaviour, motivation, friction, and unintended side effects.
I bring together qualitative insight, data patterns, domain constraints, and organisational behaviour. The goal is to understand the system, not just the user. This is why my approach often feels closer to systems thinking than traditional UX. It gives you a much clearer picture of what you are actually designing for.
4. Design with both humans and systems in mind
Human-centred design is essential, but it is only half of the picture. Every product lives inside an ecosystem. A solution that improves one journey can create strain elsewhere, whether operational, environmental, or emotional.
I take a circular design approach. I look at how a decision impacts users, teams, processes, sustainability, and long-term behaviour. Good design should reduce friction, not shift it onto someone else.
5. Use patterns when they help, break them when they limit thinking
I am not precious about reinventing the wheel. If an established pattern is familiar and reduces cognitive load, use it. If the problem requires something new, go beyond the pattern library.
Inspiration rarely comes from similar apps. I tend to pull ideas from architecture, film, game mechanics, typography, and physical spaces. This helps me design experiences that feel intentional rather than derivative.
6. Work in public with teams, not alone in a corner
I do not believe in disappearing for two weeks and returning with a polished deck. I design collaboratively, with workshops, artefacts, service maps, and prototypes that people can react to.
Design becomes stronger when engineers, PMs, data people, and business stakeholders are part of the thinking early. It reduces rework and builds shared ownership, which is the foundation of good delivery.
7. Prototype, test, and simplify
My process is iterative. Prototype, test, simplify. Remove things that do not earn their place. Challenge the team to justify complexity. Decisions become clearer when you see the product in motion instead of on a slide.
8. Deliver with clarity and direction
Leadership in design is not just about creating flows. It is about creating clarity. That means clear documentation, alignment across teams, defined decision points, and a narrative that connects every choice back to the core objective.
Because design is only meaningful when it ships and when teams understand why it matters.
Why this process works for me
My process is shaped by years of working in complex environments with high stakes, cross-functional teams, and large-scale transformation. It is less about following a checklist and more about creating the right conditions for good work to happen.
Design, at its best, is the combination of curiosity, critical thinking, and the ability to hold both constraints and possibilities in the same hand. The process is simply how we get there.
If you want to know more or work together on something ambitious, I would love to talk.
