Engineer first. Product by choice.
Story
I started in engineering. Building things taught me how much depends on choosing the right thing to build, so I moved closer to product: discovery, metrics and experiments.
Today I lead both verticals. I run product and mobile engineering including how mobile apps are tested and shipped. Working across both keeps me close to the people using the product and the people building it. Over 6+ years I’ve worked in banking, payments, financial infrastructure, web3 and stablecoins, e-commerce, logistics and edtech.
Leadership
How I lead teams.
- 1
Agree what success means before design starts.
On Teams and Sub-Accounts I set adoption and support-ticket targets with leadership before any screens existed. We beat the adoption target (38% against 25%) and could prove it.
- 2
Make the people who build it own its quality.
I removed the separate QA handoff so each product’s engineers own their tests. It cost about 6 weeks of slower delivery while they learned the tooling, and it’s why we can release weekly.
- 3
Give context, not instructions.
It gives people the clarity to make sound decisions independently, rather than creating a culture where they wait for instructions. It builds ownership, encourages critical thinking, and allows people to solve problems with a deeper understanding of the goal, not just execute tasks.
- 4
Measure before changing anything.
On Send and Receive we lost 3 weeks adding analytics mid-project to prove the baseline. Next time, instrumenting the old flow comes first.
Decisions
How I make decisions.
Prioritisation
I start with who benefits and how much their experience changes, then weigh business impact, evidence, effort, risk and what we’ll learn. I don’t pick the feature with the best story. I pick the one with the strongest case.
Example: We launched USSD for receiving money before sending. Receiving reached people without data straight away; sending carried more fraud risk and compliance work, so it waited.
Discovery
People first, then the problem, then the feature. I talk to customers and support teams, check behaviour and data, test the riskiest assumption, and build the smallest useful thing. Discovery isn’t done when the feature ships; it’s done when it changed something.
Example: Fourteen interviews and a ticket analysis showed SME owners didn’t want more accounts. They thought in budgets, not people, so we built purpose-based sub-accounts instead of per-employee wallets.
Trust and safety
Trust, safety and compliance.
I’ve worked closely with Compliance, Support and Legal on KYC, account controls and transaction safeguards. The job is to take a rule that makes sense on paper and turn it into a flow a real person can get through, without weakening the rule.
In practice: sub-accounts share the parent business’s KYC so owners face no new onboarding; approval limits give control without approving every small payment; and the partner console shipped with a full audit trail in version one.
AI
How I use AI.
I use AI as a thinking partner and an accelerator, not as a substitute for my judgement. ChatGPT helps me challenge assumptions and analyse feedback; Gemini, Claude Code and Copilot help me understand code and debug.
Outside work
- Music and film. I watch football analytically.
- Running, walking and working out.
- Travel and art exhibitions. I was valedictorian of my graduating class.
Contact
Have a product that needs to ship well?
I’m open to global roles leading product, mobile engineering, or both. Email is the fastest way to reach me.