Consistency at scale
Unified experiences across products and platforms.
Services / Product Architecture
Shape the structure behind complex products so teams can make better decisions, faster.
I clarify domains, journeys and system boundaries so the product can scale without accumulating avoidable complexity.
Unified experiences across products and platforms.
Reusable building blocks and clear patterns.
A shared language between design and engineering.
Systems that evolve with your product.
WHAT THE WORK CAN INVOLVE
Needs, behaviours and journeys
Capabilities, rules and ownership
Products, services and interactions
Responsibilities and delivery
Shared Product Language
BOUNDARY
ARCHITECTURE TRANSFORMATION
When the underlying product structure is unclear, friction appears across journeys, language and decisions.
WHAT PEOPLE EXPERIENCE
WHAT BECOMES POSSIBLE
APPROACH
Move from broad context into evidence-led investigation, then carry what you learn back into the map.
Bring the whole product into view.
Map products, users, journeys, domains and constraints.
Find where structure is creating the most friction.
Make structural tensions and areas of leverage visible.
Choose the problem where focused work can make the biggest difference.
Zoom in before deciding what to change.
Investigate the active structural problem with focused evidence.
Agree the boundaries, response and evidence for success.
Change the structure in its real product context.
Put the decision into practice across journeys, systems and teams.
Learn from the change and choose what deserves attention next.
Observe what changed and what the product reveals.
Return learning to the opportunity landscape and begin the next cycle.
Learning updates the landscape, so the next investigation starts with better context.
EVIDENCE
Selected work and thinking where product structure clarified journeys, boundaries and decisions.
ARTICLE
Most hiring processes are designed around the one person who gets the job. But everyone else leaves with an experience that can influence who applies next. What happens when we look at hiring as a service designed for everyone who participates in it?
CASE STUDY
A ground-up rebuild of the candidate screening experience, separating the constraints we had to respect from the legacy behaviours we no longer needed to inherit.
CASE STUDY
I helped modernise a fragmented legacy product by clarifying its core patterns, introducing reusable design-system foundations, and creating a more consistent way for teams to make and scale product decisions.
RECOGNITION
Journeys work independently, but they do not feel like parts of one product.
Navigation keeps growing through exceptions and special cases.
The same concept means different things in different areas of the product.
Adding functionality requires changes to unrelated parts of the product.
Teams disagree about where capabilities belong.
Nobody can confidently explain how the whole product fits together.
START WITH THE FRICTION
We can trace what sits underneath the complexity and work out where clearer structure would make the biggest difference.
Let's talk