Stakeholder requirements to production.
I own the whole delivery.

Technical product manager at a clinical diagnostics lab. Technical lead for a 9-person team across a five-product portfolio, supporting 15+ stakeholders across engineering teams in the US, Pakistan, and Egypt.

Clinical diagnostics·Epic and SMART on FHIR·HIPAA·Python

Impact

Numbers I can defend in the room.

0%
Delivery growth, 20.6 to 38.4 resolved issues a month
0.00x
Release and hotfix sprints, 26 in 15 months against 8 the year before
0%
Faster median resolution on Client Portal, 5 days to 1
0%
Faster EMR integration scoping, across 10+ clients

Selected work

Six problems, each one older than the software that fixed it.

01

Two people ran a coffee cart at a 300-person bazaar by hand, writing orders on cups and apologising to a 20-minute queue. The vendors who needed help most were the least likely to ask for it.

Next.js · Supabase · Stripe Connect · built solo
Live at bizzar.app
02

An external freelancer left the accessioning hub mid-build with no product owner, no written requirements, and a production LIS that had changed drastically underneath the original spec.

React · Spring Boot · 5 engineers · 9 months, ongoing
136 items delivered in 9 months
4 days median cycle time
Read →
03

Admin module

in development

Physicians were losing access to their own cases because of manual overrides scattered through the legacy system, the biggest HIPAA and compliance risk in Tiger LIS, and there was no dedicated module to manage it.

Angular · Spring Boot · in final QA · 4.5 months
81 of 86 items through development and QA
Read →
04

Lab managers tracked technician productivity by hand in a shared spreadsheet, so throughput problems only surfaced a week after they happened.

Python · HIPAA · shipped in 9 weeks
6 days → live, reporting lag
14 managers on it weekly
Read →
05

Clinicians were retyping lab results into their own charts, and every client site wanted a different file drop instead of an interface.

SMART on FHIR · Epic · 4 client sites in phase one
0 workflow changes asked of clinicians
Read →
06

Requisitions arrived as faxes and scans, and two staff spent their mornings keying them into the LIS before any sample could be run.

Python · document AI · scope to be confirmed
Read →

How I work

Discovery through release, one lifecycle.

01
Discovery in the workflow

I sit with the people doing the work and size the problem before anyone writes a ticket.

02
Stories and a written scope

Acceptance criteria, and an explicit list of what is deliberately not being built.

03
Sprints across three time zones

Async by default, one overlapping hour a day, specs that survive being read alone.

04
UAT and release

I run the UAT pass with real users, coordinate the release, and own what happens after it.

Elsewhere

What I do when I am not shipping.

I compete in judo and Brazilian jiu jitsu, taught me the importance of consistency and discipline

I teach a youth class on weekends and am passionate about the upbringing of children and fostering of leaders

Through my interest for economics, I am always talking and writing about the market and the ability of computer systems

More about me →