I make complex health and technology products feel human.
I bring together a decade in healthcare product leadership, large-scale platform delivery and hands-on AI product building. The result is product judgement grounded in users, evidence and what engineering can deliver.
Concept→releaseDiscovery, build and App Store preparation
Health + AIDomain depth and hands-on build
Product perspective
From health tracking to useful guidance
More data is not the same as more understanding.
The next generation of health products should help people recognise what changed, understand why it may matter and prepare for a useful next step. That means unifying fragmented records, making uncertainty visible and grounding every explanation in evidence the user can inspect.
Signal over volumeEvidence before inferenceAction without overreach
Selected product work
Evidence of product thinking—not just output.
Independent builds and professional platforms that show how I frame problems, make trade-offs and bring technical and user needs together.
Health technologyiOS · Swift · AI Preparing for App Store release
01 / Featured case study
Health Record Ally
An independently designed and built iOS app that turns a fragmented health record into an understandable, source-attached view—helping people prepare for more informed NHS conversations. Live at healthrecordally.com.
Current stage
Health Record Ally is preparing for App Store release, with a defined one-time-unlock pricing model and a published privacy policy already live at healthrecordally.com.
The problem
Results, conditions, medicines and guidance live in different places. A person can have plenty of data and still struggle to understand what changed, what influenced it or what to discuss with a clinician.
My product approach
I designed and built an iOS experience that unifies clinical letters, results, medicines and Apple Health signals into one governed, patient-owned record—then turns confirmed facts and relevant NICE guidance into a Care Options Brief for the next appointment.
Key decisions
Keep every fact traceable to its original source and date—nothing floats free of its evidence.
Separate confirmed facts from potentially relevant guidance; never blur the two into a single claim.
Constrain AI to explaining structured facts—deterministic rules decide, the model only explains.
Design on-device by default, with no silent fallback to an external AI provider.
What it demonstrates
Consumer-health judgement, information architecture, mobile UX, technical fluency and a practical model for explainable AI in a high-trust setting.
Labs overviewStructured markers at a glanceLongitudinal viewTreatment context alongside trends
Health Record Ally screens · fictional demonstration data
A defining product decision
How can AI explain a health record without pretending to be a clinician?
01
Risk
An unconstrained model can sound authoritative even when it lacks the full clinical picture.
02
Decision
Ground every response only in confirmed facts and clearly sourced published guidance.
03
Trust mechanism
Keep source, date and criteria visible for every piece of guidance; label interpretation as interpretation.
04
Validation
Test comprehension, source confidence and whether the resulting questions are ones a clinician would recognise as reasonable.
AnswerInterpretation is explicitly labelled
Evidence, not magic
The useful part is the constraint.
The Care Options Brief is built around traceability, not an open-ended chatbot. Every confirmed fact and every piece of guidance keeps its source attached, so the person can take that evidence—not just an AI’s summary of it—into the room.
Consumer energyiOS · Swift · GraphQL Working prototype
02 / Connected-energy product
PowerPilot
A provider-neutral iOS energy companion that turns smart-tariff schedules, carbon intensity and connected-device data into clear charging decisions and practical automations.
The problem
Cheap-energy windows, charging schedules, device state and grid-carbon forecasts are fragmented across providers. Even when the data exists, households still have to work out when to act.
My product approach
I designed the journey around the next useful decision: when to charge, what it may save and whether a lower-carbon option exists. Octopus Energy is the first live provider integration, built behind a model that can support others.
Product and technical decisions
Use provider adapters rather than hard-coding the product around one tariff or supplier.
Lead with time until the next useful window, then reveal tariff and carbon detail.
Keep cost and carbon visible as separate signals instead of hiding them inside one score.
Offer reusable automation templates with explicit, safety-checked device actions.
Build with AI-assisted/agentic development (Claude, ChatGPT, Kiro) as a core part of the process, from the provider adapters to the mock service layer and test suite.
Demonstrates: consumer-product judgement, API integration, mobile information architecture, platform thinking and translating complex real-time data into understandable action.
Decision-first homeNext cheap window, savings and carbonCharging timelineHalf-hourly windows made navigableProvider-neutral automationReusable rules with explicit actions
Product operationsNext.js · APIs
03 / Product workflow
ProdLens
A focused workspace designed to help Product Owners connect delivery detail with the risks and decisions that matter.
Links Jira backlog items to product risks and outcomes
Brings Microsoft To Do actions into delivery context
Makes dependencies and decision points easier to surface
Demonstrates: first-hand user discovery, API integration and workflow design.
Consumer mobileConcept · MVP
04 / Consumer concept
ClosetLoop
A wardrobe and outfit-management concept built around reducing choice friction and helping people make more of what they own.
Frames the job around choosing, not cataloguing
Connects outfits, occasions and wardrobe availability
Uses MVP prioritisation to test the riskiest assumptions
Demonstrates: consumer intuition, journey design and lean validation.
Professional experience
Comfortable where complex technology meets real-world impact.
2023—Now
Jaguar Land Rover
Senior Product Owner
Leading connected-vehicle platform capabilities spanning large-file transfer, vehicle enablement and observability. I shape roadmaps, manage dependencies and align engineering delivery with product and operational outcomes.
Shaped clinical and operational software in a complex, regulated environment, translating the needs of clinicians and NHS stakeholders into deliverable product outcomes.
Health systemsClinical usersDiscoveryEnd-to-end delivery
Stakeholder range
I communicate at the right altitude.
From engineers working through implementation detail to consultant clinicians, CCOs, CTOs and senior leadership teams making strategic decisions.
How I work
Opinionated about outcomes. Curious about evidence.
01
Start with the real problem
I look beyond the feature request to understand the user need, operating constraint and outcome worth changing.
02
Make complexity navigable
I turn technical and organisational uncertainty into clear choices, prioritised work and visible dependencies.
03
Learn through delivery
I define the smallest useful release, measure behaviour and use feedback to improve the roadmap—not merely validate it.
Kelly Pearson · Product leader
Building useful products in health, AI and connected technology.
Based in the Wirral, working with teams across the UK.
