A good process makes the work intentional. Mine has three steps, built on five principles.
My steps
01 Understand
I start by breaking down the product. I find what’s innovative and the core experience users repeat over and over. I dig into the users, their needs, and how the product solves their problem. Knowing where you’re innovating and where the core loops are shows where to focus the effort.
02 Zoom out
Once I understand the product, I can review it in context. When results aren’t coming, the instinct is to optimise harder. Tweak the button. Add a feature. The problem is usually higher up.
I map the full experience against what each part is trying to achieve, what data exists, and where we need more. That usually reveals the real problem. What to do now, next and later gets a lot clearer.
03 Move forward
With a clear picture, the question is how to act without creating new problems. I involve the whole team from the start, not just designers and PMs. I design and build in tandem. Engineers aren’t waiting on designs. Technical discoveries feed back into the design while it can still change. Everyone works from the same understanding. Changes stay incremental, so you can see what’s working before committing to more.
My principles
01 Understood
The best design process is one the team believes in, understands, and gets results from.
02 Flexible
It works for any timeframe, whether it’s an hour or a year.
03 Involves everyone
Involving the whole team early brings diverse thinking and skills. Designs meet user and business needs and are technically feasible.
04 Skipable
You can skip any step as long as you understand why.
05 Problem focused
Fall in love with the problem, not the solution.