Product in Healthtech

There are a handful of genuinely useful, concrete ideas - CEO-as-product-owner, named tools (Lovable, V0), the Switchboard Labs separation, and multi-day prototype cycles - but they are surrounded by substantial filler, mutual affirmation, and restatements of common startup wisdom. The insight rate is low relative to runtime.

“I fly to Florida tomorrow, I'm going to learn a bunch in the two days that I'm running around down there, I'm going to come back, we're going to have one meeting and decide on at least one thing that we're going to build on a prototype on that'll probably be measured in days, not weeks. And then we're back at the client six days later with a real clickable application”

“Yeah, yeah. And you kind of, you got recruited kind of through the venture process to run this company, correct?”

The core argument - dissolve the traditional PM role, have the CEO own product decisions, and use AI prototyping tools to compress cycles - is timely but increasingly common in 2024-2025 discourse. There is no genuinely contrarian or first-principles argument; the 'lines between engineering, UX, and PM will collapse' observation is widely circulated.

“I think the way that you organize around that just needs to be very different in 2025 than it was even two years ago”

“I think successful product people will um, be able to thrive as the kind of lines between engineering UX and traditional product management. Like those lines are already blurring. I think they're going to collapse altogether.”

Derek Baird is a genuine practitioner with two decades in digital health and a working company, which is a positive signal, but Switchboard Health is a 12-person seed-stage startup with limited demonstrated scale. He is not a career podcast guest, but the depth of operational experience discussable at this company size is inherently limited.

“I've been in digital health my whole career. I stumbled into it before I even graduated from college. And so that was a few years ago. Uh, and I've spent a couple decades now trying to use technology to improve how care is delivered”

“Look, we're a 12 person company. I mean a lot of this is like we're all together on the line riffing on this”

The episode contains some concrete specifics - named tools (Lovable, V0), a named acquisition (Conduce Health), named investor (Route 66 Ventures), prototype cycle times measured in days, and a 40% patient drop-off statistic - but there are no revenue figures, customer counts, model performance data, or sourced research to validate claims.

“about 40% of patients then just give up along the way because they don't know what a rheumatologist is or they don't know what in network means”

“we're back at the client six days later with a real clickable application saying, did we hit the bullseye or not? And they'll probably say no, but you're on the dartboard. And then the next cycle's three days.”

The host asks reasonable follow-up questions (how work gets dispersed, the trust/Labs question) but consistently validates rather than challenges, often inserting his own lengthy opinions instead of drawing the guest out further. No claim is meaningfully pushed back on and several opportunities for deeper follow-up (e.g., what has actually failed in this approach, specific metrics on speed gains) are missed.

“Oh, for sure. Well, and also, I think you're really tapping into this cost control nature.”

“Well, I think every company, regardless of size. We've seen this a lot at Vinyl when we work with Fortune 500s.”