01
Fall in Love with the Problem
Customer first, always
The customer's problem is the starting point for everything. Not the feature request, not the stakeholder ask — the underlying problem the customer actually has. Customer signal is the most important data there is. Everything else is secondary.
Perri: start with the customer's problem, not the solution · Kahneman: observed behavior over stated preference
02
Diagnose Before You Prescribe
Understand first
Never jump to a solution before mapping the actual problem. Talk to users, read the data, audit the process. The presenting symptom is rarely the root cause.
Kahneman: System 2 thinking before System 1 reacts
03
Co-Create, Don't Impose
Build with, not for
Engineering, design, and commercial teams in the room early. I don't implement processes at teams — I build them with teams.
Perri: cross-functional discovery as operating model
04
Outcomes Not Output
Ship results, not features
Every roadmap item needs a clear hypothesis: if we build this, this metric moves. Product management is not a feature factory — it's outcome ownership.
Perri — Escaping the Build Trap: PMs own outcomes, not backlogs
05
Data Is Not Optional
Evidence over intuition
Gut instinct is a starting point, not a decision. If we don't have the data, we build the instrumentation first. Data is the operating system of a great product org.
Perri — Product Ops: data as operating system · Kahneman: bias makes intuition unreliable at scale
06
Design for How People Decide
Choice architecture matters
The way a choice is presented changes the choice made. Defaults, sequencing, framing — these are product decisions. Great commerce guides people toward better decisions without removing their autonomy.
Nudge: choice architecture as a product discipline, not just a UX one
07
Operational Excellence as Strategy
How you run it is the product
Operational rigor is a competitive advantage. Clean processes, clear ownership, and disciplined execution compound over time. Chaos doesn't scale — and clean ops are as valuable as clean code.
Perri — Product Ops: continuous planning and operational discipline
08
Build for Scale, Not Just Today
Design for what's next
Every architecture and org decision should be evaluated at 3x the current scale. Focused beachhead bets beat trying to serve everyone at once.
Crossing the Chasm: focused bets · Innovator's Dilemma: build for the emerging market
09
AI as Discipline Enabler
Apply where it earns its place
AI applied where there's genuine pain — not a default or a decoration. And AI is itself a user type: agentic interactions require intentional product design, not an afterthought.
AI agents are a distinct user type — designing for them requires the same intentionality as designing for humans
10
Product Is the Nervous System
Sense, connect, respond
Receives signals from engineering, design, business, and customers. Weaves them into a coherent picture and prioritizes the response. When something has no owner, you detect it and close it. A healthy nervous system is invisible. A missing one is catastrophic.
Perri: PM sits at the intersection of business, technology, and customer — and owns what falls between