DESIGN PROCESS process I follow
I approach product design as the structuring of decision environments rather than the optimisation of individual interfaces. My work typically begins by reframing ambiguous problem spaces into coherent experience architectures that support user behaviour, business goals, and delivery constraints simultaneously.
While grounded in Design Thinking principles, my process operates as a continuous system-level loop spanning discovery, structure, validation, and delivery alignment.
Understand the decision environment
I begin by understanding how users interpret information, prioritise signals, and move from observation to action across complex workflows.
This involves:
Behavioural workflow mapping.
Stakeholder interviews across product, engineering, and operations.
Analysis of existing navigation and interaction structures.
Identification of cognitive friction across decision paths.
Review of technical constraints shaping delivery feasibility
Rather than focusing only on user needs, I focus on how systems influence user reasoning.
Frame the right problem
Instead of starting with feature requests, I define structural product questions:
Where does interpretation break down?
Where does navigation diverge from user reasoning?
Where does the system introduce uncertainty or delay decisions?
This allows teams to shift from incremental UI improvements to platform-level clarity.
At this stage I typically produce:
Decision-flow models
Information hierarchy structures
Interaction architecture hypotheses
Experience strategy principles
These create alignment before solution exploration begins.
Shape the experience architecture
Once the problem space is structured, I define interaction models that support predictable movement through complex workflows.
This includes:
Information architecture redesign
Navigation model definition
Cross-surface interaction consistency
Decision-support workflow modelling
Experience hierarchy across signals, context, and actions
Rather than designing screens, I design the environment in which decisions happen.
Prototype to align teams early
Prototyping is used as a collaboration tool, not just a validation artifact.
I create structured prototypes that help:
Test workflow assumptions
Align product and engineering direction
Evaluate feasibility early
Reduce ambiguity before implementation
Accelerate stakeholder confidence
This compresses concept-to-delivery cycles and improves roadmap clarity.
Validate behaviour, not opinions
Testing focuses on how users interpret signals and move through workflows rather than whether they “like” a design.
Typical evaluation signals include:
Task success across complex workflows
Time-to-decision improvements
Navigation predictability
Error-rate reduction
Drop-off points across multi-step flows
Insights from validation directly inform prioritisation and sequencing decisions across delivery streams.
Enable scalable delivery
A critical part of my process is ensuring experience improvements can scale across the product.
This involves:
Design system creation aligned with engineering implementation
Component reuse strategies
Interaction pattern standardisation
Design governance practices
Implementation QA and delivery alignment
The goal is not just better interfaces, but faster and more reliable product evolution.
Operate as a continuous system
Although often described as sequential, this process operates as a continuous loop.
Research informs structure
Structure informs interaction models
Interaction models inform prototypes
Prototypes inform roadmap decisions
Delivery informs the next iteration cycle
This allows teams to adapt quickly while maintaining a coherent experience direction across complex platforms.
Where this process creates impact
I typically apply this approach when:
Platform navigation has grown organically without structure
Data-rich environments overwhelm interpretation
Multiple workflows operate in isolation
Engineering delivery lacks reusable interaction patterns
Teams need alignment around experience direction
Products are scaling beyond their initial architecture
In these contexts, design becomes a structural layer supporting product clarity, delivery velocity, and long-term platform evolution.