Five mechanics · Evidence over adjectives
Why me?
I understand the forces around design—not only the design itself. Change, teams, collaboration, measurement, and hands-on execution are the mechanics I use to turn ambitious ideas into outcomes people can adopt and organisations can sustain.
- Start with the mechanic closest to your role or challenge.
- Read the principle and the practices I apply.
- Open the linked portfolio evidence to inspect the decisions in context.
Protect continuity while creating the new.
Starting again can feel intuitive for a new product, user, or deal. Existing users experience that reset as lost fluency, broken habits, and new risk.
I treat change aversion as useful information—not resistance to dismiss. Across Freshworks, Athenahealth, and other transformation work, I have preserved recognisable mental models, introduced change progressively, and built evidence strong enough to help teams move without abandoning the people already depending on the product.
- Map existing user habits before changing structure
- Separate what must change from what should remain familiar
- Use staged adoption, language continuity, and visible transition cues
Stay close to the work—and make strong work repeatable.
I have contributed inside excellent teams and built teams of my own. That gives me empathy for both the person doing the work and the system surrounding them.
As an IC and manager, I stay close enough to the action to offer useful judgement, provide air cover when teams need it, and remove organisational friction without taking ownership away. I have created and applied competency frameworks, career systems, critique practices, research access, and clearer performance conversations to improve quality, growth, and retention.
- Give designers clarity, context, critique, and room to own
- Make expectations visible through competencies and evidence
- Build operating systems that survive beyond individual heroics
Create one decision space for different experts.
Complex products are rarely solved by design alone. Product, engineering, operations, research, sales, support, legal, finance, and domain experts each see a different part of the system.
My role is to make those perspectives usable together: establish shared language, expose assumptions, turn disagreements into testable choices, and keep the customer outcome visible while constraints are negotiated. Experience across healthcare, procurement, AI, wealth, equity, and enterprise planning helps me enter unfamiliar domains without pretending expertise I have not earned.
- Translate specialist knowledge into shared models
- Make assumptions and trade-offs inspectable
- Use artefacts to improve the conversation—not merely document it
Define done, define value, then prove what changed.
Measurement starts before delivery. A team needs to know what must be true for the work to be complete, valuable, and successful in the market.
I combine research evidence, behavioural and product analytics, operational measures, and post-release quantitative signals. I help teams distinguish delivery metrics from value metrics: definition of done from definition of value, and feature completion from adoption, comprehension, efficiency, retention, conversion, or commercial impact.
- Use research to establish the problem and baseline
- Choose leading and lagging measures before implementation
- Connect product evidence to operational, marketing, or business outcomes
I love being hands-on—and doing the extra work that makes it real.
Leadership does not remove me from the material of the product. I still frame, sketch, prototype, write, test, critique, and build when that is what progress requires.
What energises me most is the distance between a persuasive concept and something that works under real conditions. I enjoy the extended effort: resolving edge cases, clarifying language, aligning implementation, testing the awkward states, and improving the system around the screen so the intended experience survives contact with reality.
- Prototype decisions, not just presentation
- Follow the work through edge cases and implementation
- Raise craft while keeping momentum and ownership distributed
Leadership close enough to improve the work—and broad enough to improve the system.
If you are evaluating fit, use the case-study links above to challenge the claim. Each principle should be visible in decisions, trade-offs, artefacts, and outcomes—not only in this summary.