The Title You Never Had
Startups are searching for a Clinical Product Owner. That person has been inside health systems for years.
Sunday Share: Somewhere in a health system right now, a Clinical Informaticist is doing product work and calling it something else.
They’re translating clinical workflow logic into build requirements. They’re synthesizing what physicians actually do versus what the EHR was designed to support. They’re sitting in rooms with engineers explaining why the order set has to work the way it does — not as a preference, but as a patient safety constraint. They’re prioritizing under resource constraints, making tradeoffs, owning outcomes.
A startup three miles away just posted a job for exactly that person.
The recruiter will pass the resume.
The Role That Was Never Named
There’s a music industry analogy that maps this well. The arranger who orchestrates a full session — who takes a sketch and translates it into something buildable, who knows which instruments carry which frequencies and why — is doing producer-level work. The title just hasn’t caught up. When someone finally hands them the session, nothing changes about their capability. Everything changes about what they’re accountable for.
Clinical Informaticists have been running sessions they didn’t own for a long time.
The aggregation of domain knowledge, the translation of clinical logic into system behavior, the sequencing of the build — that’s not support work. It’s product work. The title said otherwise. The vendor held the build. The IT governance process sat between the insight and the shipped thing. So the work happened, but the ownership stopped short.
I wrote about a version of this in The Explorers Who Finally Got to Make Their Own Maps — the idea that the mandatory translation layer between clinicians who understand problems and engineers who build solutions is dissolving. This essay is the same argument from the career side.
The Recognition Failure Isn’t About the Candidate
Film sets have a role called the First Assistant Director. The First AD runs the production. They manage the schedule, coordinate every department, translate the director’s vision into a shootable day, and absorb every constraint simultaneously. Studios spend years searching for directors who “understand production” — without looking at the person who has been doing exactly that job, every day, on every film they’ve made.
Startups building clinical products are running the same search.
The job posting asks for someone who understands clinical workflows deeply, can translate them into product requirements, manage technical teams, and prioritize under constraint. It lists a preference for clinical background. It mentions Epic as a plus. Then it filters for “product experience” — which usually means prior product titles at prior tech companies — and the informaticist doesn’t make the cut.
The recognition failure is in the hiring frame, not the candidate pool. The role was never missing. The mapping was.
What Changed — and Why It’s Urgent
The sell-side analyst always had the domain knowledge. The missing variable wasn’t intelligence — it was capital. When that analyst moved to the buy-side, nothing changed about what they knew. Everything changed about what they were responsible for.
For Clinical Informaticists, AI tools and modern development infrastructure are the fund.
The informaticist who couldn’t ship without an IT department and a six-month vendor contract two years ago can prototype in a weekend now. I documented my own version of this in Nobody Asked Me To — how the NerdMDs app went from a framework in my head to a thing people could actually use, built in the gaps between clinic shifts. The knowledge was never the gap. Access to production was. And that gap is closing fast.
This is also why the startup’s search problem is becoming more expensive by the month. The informaticist who was locked out of the build is now building. If the title recognition doesn’t catch up, the talent won’t wait.
What Changes When You Own the Outcome
Here’s the part worth being honest about.
The sabermetrician who becomes the GM doesn’t get a promotion in the celebratory sense. It’s a category change. You stop being right or wrong analytically. You start being right or wrong on outcomes. The GM who bets on the wrong player doesn’t get to say “but the model said.” Clinical Informatics stepping into product ownership means owning the result, not just the recommendation.
That’s harder. It’s also the only version of the role that matters.
Advisory coherence — knowing what should be built, being right about it, watching something adjacent get built instead — is the experience of most informaticists inside health systems. Build coherence is what happens when the person who understands the system controls what gets shipped. The startup Clinical Product Owner role is that. Not an elevated advisory position. An ownership position.
Nabla Just Showed How It’s Done
One company recently demonstrated what happens when the naming problem gets solved.
In February, Nabla announced that Dr. Matt Sakumoto is their new Chief Clinical Product Officer. He came from Sutter Health, where he served as Chief Medical Informatics Officer. Prior to that: UCSF, Teladoc Health, roles spanning clinical informatics, virtual care delivery, and AI integration inside regulated health system environments. A practicing internist. Dual-boarded. A clinical informaticist by training and by track record.
Nabla didn’t search for a traditional product leader and then send him to clinical shadowing. They recognized that the informatics credential was the product credential — and built a C-suite title to match work that already existed.
It’s worth noting that Nabla’s CEO is Alex LeBrun, and Yann LeCun is among their advisors. I wrote about both of them a few months ago in the context of what clinical AI architecture actually needs to do — that essay was about world models and the gap between language prediction and genuine clinical reasoning. This essay is about talent. The underlying argument runs parallel: clinical context isn’t a feature you add at the end. It has to be structural. Nabla seems to understand that in both directions.
The Sakumoto hire is the clearest public signal yet that some startups are reading the credential correctly. Most still aren’t.
The Startup That Figures Out the Naming Problem
Cities that solved congestion didn’t optimize roads. They built transit systems — infrastructure that moved people through different routes, reducing demand on the roads by making them less necessary. The Physicians Are the Lanes made that argument about clinical capacity. The same logic applies to clinical product talent.
The hire isn’t missing. The routing is.
The startup that learns to read a Clinical Informaticist resume the way Nabla read Sakumoto’s gets access to a talent pool everyone else is still trying to construct from scratch. Deep clinical workflow knowledge. Hard-won translation skills. Years of navigating the exact regulatory, political, and interoperability constraints their product has to survive.
The resume says Senior Clinical Informaticist. It lists Epic certifications and workflow optimization projects and EHR governance committee work.
Read it again.
If you’re a Clinical Informaticist who’s been doing this work without the title — or a founder who just recognized the hiring blind spot — drop it in the comments. Curious which side of this lands harder.