Design process and philosophy
Years of designing products across industries have reinforced one principle: great products are built on context. Before designing, I seek to understand the product ecosystem, industry conventions, and familiar interaction patterns. I then pair those insights with a deep understanding of users, their environment, goals, behaviours, and motivations to design experiences that are intuitive, relevant, and impactful.
Key design principles
Context before creation
Designing within the right context leads to experiences that feel intuitive from day one.
Put people at the centre
Understand users' goals, behaviours, motivations, and the environments in which they use a product.
Simplify through iteration
The best experiences are rarely the first idea. Validate assumptions, embrace feedback, and refine designs continuously to reduce complexity and create products that are clear, accessible, and scalable.
Design with business impact
Every design decision should contribute to product adoption, engagement, accessibility, or business growth
Product design process
Every project is different. My approach evolves based on the product's maturity, what has already been validated, stakeholder priorities, and delivery constraints. These phases are flexible and iterative rather than fixed.
01
Discovery
-
Research users and stakeholders
-
Explore the product ecosystem
-
Review business goals and data
-
Identify opportunities and constraints
02
Clarity
-
Synthesize research insights
-
Map user journeys and pain points
-
Align business and user needs
-
Prioritise opportunities
03
Explore Ideas
-
Brainstorm concepts
-
Sketch user flows and wireframes
-
Compare approaches
-
Collaborate with cross-functional teams
04
Design & iterate
-
Design high-fidelity interfaces
-
Prototype interactions
-
Ensure accessibility and consistency
-
Build scalable design systems
05
Test & iterate
-
Conduct usability testing
-
Gather stakeholder feedback
-
Measure product outcomes
-
Refine based on insights
Design doesn't happen in isolation
Ask questions early: No question is too simple. Early discussions uncover assumptions, reduce ambiguity, and prevent costly rework.
Clear communication: Bring cross-functional teams together to align on the problem, user needs, and product direction. Encourage ideas and feedback throughout the process.
​
Validate from the start: Instead of treating testing as a final step, share work frequently with the internal team and stakeholders, gathering feedback throughout the process to reduce risk and make better product decisions.