I understood products only after I became a founder.
Running a startup—especially in a domain as unforgiving as healthcare—compresses years of product learning into months.
There’s no buffer. No hierarchy to hide behind. No “next quarter” to fix mistakes. Every decision has consequences, fast.
Looking back, there are a few lessons founders internalize early—lessons many PMs encounter much later in their careers, sometimes painfully so.
There’s More to Decision-Making Than Product Metrics
PMs often optimize for features, flows, or elegance—frequently in service of improving product metrics or, bluntly, meeting KPIs and KRAs.
Founders think differently.
Their decisions are anchored in one question: does this tangibly make life easier for the user?
That doesn’t mean metrics don’t matter.
Founders use KPIs to communicate, align teams, and track progress—but not to replace judgment. Metrics are instruments, not the compass.
The real driver is an almost obsessive focus on reducing user effort, friction, and cognitive load.
It’s tempting to assume this mindset only needs to exist at the founding layer.
But if Product Managers are truly the bridge between users and developers, this responsibility sits squarely with them too.
Without a strong user-first lens, metrics risk becoming a proxy for value—rather than a reflection of it.
Constraints Are Not Blockers. They Are Design Inputs.
Founders live inside constraints: limited capital, limited time, limited trust, limited second chances.
You don’t ask, “What’s the best solution?”
You ask, “What’s the best solution given reality?”
In practice, this changes how problems are framed.
Legacy systems, regulatory boundaries, incomplete data, or unclear requirements stop being reasons to pause.
They become inputs into design.
Many strong product decisions emerge not from eliminating constraints, but from acknowledging them early—and designing with them rather than around them.
You Can’t Hide Behind Ambiguity When It’s Your Money
As a founder, vague ideas are expensive.
“Let’s see how users respond” isn’t a strategy when runway is finite.
You’re forced to:
- Define success early
- Decide what not to build
- Say no before evidence feels comfortably complete
This is especially relevant in AI-led products, where the temptation to treat the technology as a black box is high.
Powerful tools can create the illusion of progress without clarity.
A founder’s lens teaches the opposite lesson:
the more powerful the technology, the more discipline the product needs.
Clear inputs, explicit expectations, and guardrails aren’t constraints on creativity—they’re what make outcomes reliable.
Ownership Changes the Quality of Your Decisions
When you’re a founder, every decision has consequences—emotional, financial, and reputational.
That weight sharpens judgment.
Carrying that sense of ownership into product roles changes how decisions are made:
- Stakeholder trust becomes something you actively protect
- Long-term impact matters more than short-term optics
- Outcomes matter more than activity
Founders don’t ask, “Is this my responsibility?”
They ask, “What breaks if I don’t act?”
That single shift reframes how problems are owned and resolved.
Closing Thought
Product management teaches you how to build products.
Founding teaches you why most products don’t survive.
Somewhere between the two, real product judgment forms.
Not every PM needs to be a founder.
But thinking like one—about users, constraints, ambiguity, and ownership—becomes increasingly important, especially in a world where AI accelerates both good decisions and bad ones.
And once you’ve experienced that responsibility firsthand, it quietly changes how you approach every product problem after.