About
I work on the adoption layer of healthcare technology, where clinical workflow, trust, and institutional constraints determine whether a product actually gets used
I help healthcare teams move from impressive demos to deployable systems: workflows clinicians can trust, decisions organizations can stand behind, and operating models that handle the real conditions of healthcare delivery.
The point isn't to add process. It's to remove the ambiguity that actually slows teams down — so they can ship faster, with fewer surprises.
Quick version · 30 seconds
Configured EHR workflows, reduced alert fatigue.
Led Dialer — grew to 110M+ visits from 300K+ clinicians.
Directed digital products — 30MM annual visitors, bounce rate −25%.
Led care-navigation across surgery, oncology, behavioral health.
Co-founded, raised $240K, grew to 1,200+ physician users.
Evidence-review systems for disputed healthcare claims.
Patients don't answer calls from unknown numbers — that single observation drove Doximity Dialer. As early product lead, I shaped a HIPAA-conscious calling tool that showed the doctor's office number instead of a personal one, preserved carrier identity rules, and routed missed calls through verified fallback paths. iOS app reviews climbed from 3.7 to 4.8 stars during mobile product work. Dialer went on to power 110M+ video and audio visits from 300K+ active clinicians.
At CancerCompass / CTCA Marketplace, I led digital products for an oncology navigation platform serving 30MM annual visitors. CTCA was later acquired by City of Hope. Product changes cut bounce rate by 25% and lifted chat conversions 267%.
At Transcarent, I directed product across value-based specialty-care and care-navigation programs: Surgery, Urgent Care, Behavioral Health, and Oncology Care. Managed product managers and senior product managers across all programs.
Co-founded Andwise and served as CEO. Raised $240K in initial funding, grew to 1,200+ physician users and a 700-member community, and convened a 50+ physician medical advisory board.
At Epic, I configured EHR workflows where a single misrouted alert could bury a critical lab result. As an Implementation Engineer, I supported clinical workflow configuration, rollout, training, and quality-measurement design — reducing alert fatigue without compromising safety. The workflow around the clinician was usually the constraint, not the clinician.
At Georgia Tech, I studied RNA folding dynamics and sRNA-mRNA interactions in Roger Wartell's lab — modeling the free energy barriers that determine whether a reaction proceeds or stalls. I co-authored a book chapter in the ACS Symposium Series on sRNA-mRNA interactions and Hfq at 19, and spent a summer on thoracic surgery outcomes at Memorial Sloan Kettering.
The earliest trace: I created a Wikipedia account in fall 2004 and seeded my high school's page. By the next day, classmates were posting disciplinary incidents and edit-warring over the college list. The pattern was there before I had language for it — build something, watch people fill it, try to keep it true.
Across every layer — molecular biology, EHR configuration, clinician communication, oncology navigation, care navigation, physician financial support — one pattern held: the higher the stakes, the harder it was to trace, question, or undo a decision. My strongest product pattern is making hidden operating logic visible: who owns the next step, what evidence supports the action, when to raise a concern, and how the system recovers when the default path fails. The point isn't to add process — it's to remove the ambiguity that actually slows teams down. I build products where the interface is not the hard part. The hard part is usually trust, workflow fit, evidence, and recovery. I specialize in decision-support products where the support layer — evidence basis, workflow fit, override, documentation — is as important as the recommendation.
NextConsensus produces source-traced evidence briefs for disputed healthcare claims — each brief maps one claim, one decision window, and one source-backed answer. Coverage, formulary, and market-access teams use them to review decisions in the gap before institutional consensus forms. I write on institutional burden and system failure at The Crumple Zone and develop Ethotechnics, a product method for safe exits and correction loops. Based in Chicago.
See also
Milestones
Wikipedia editing begins
First Wikipedia account at 14. Editing local pages and seeding the high school article.
How I approach product work
Care as default
If a workflow requires someone to remember a step at 3AM, the step is the problem, not the person.
Evidence over lore
Watch how operators actually work. Instrument what matters — not what's easy to measure.
Trustworthy automation
Every automated decision needs a visible override path. Every override needs an audit trail.
Areas of focus
Education
B.S. Biomedical Engineering (with honors)
Georgia Institute of Technology
Human-centered clinical systems, pairing biomechanics and design research.
MBA
NYU Stern School of Business
Finance and technology focus, paired with product leadership in regulated markets.