Inside the Book

Frameworks help you think. Judgement decides.

As a CPO, you've probably been asked: "What do you actually own?" When that happened to me, I answered too quickly. This book is what it took to answer it honestly.

At Givted, a social group-gifting startup I launched in the US, thousands of users loved our product and our NPS was above 80. But when I looked at revenue per user versus burn rate, the math was devastating. We couldn't afford the love. That's when I learned what no playbook can prepare you for: frameworks tell you what to measure; judgement tells you what matters.

From Dassault Systèmes to Amazon, then CPO at two European scale-ups, VisionTech and FinCredit, plus a US startup that failed. The CPO role has been one of the highest-leverage jobs I've held, and one of the most misunderstood.

Why? The Product team sits where user needs, technical constraints and business outcomes collide. Marketing drives demand. Sales converts it. Finance measures it. Engineering builds it. The CPO ensures all four align around what gets built. When that alignment breaks, everything gets harder.

This is for CPOs and senior product leaders at late-stage startups, IPOs and beyond. Places where decisions are costly to reverse, trade-offs are political, and accountability doesn't disappear after the roadmap is approved. If you're still figuring out what to build, this isn't your book yet. If you're carrying the weight of those decisions, keep reading.

Every executive faces hard choices. But as CPO, you're making calls that physically change what the company builds, what features ship, which platforms get prioritised, how we serve the markets the CEO chooses to enter. Some of those decisions are permanent. You can shift budgets next quarter, change org charts, pivot messaging. You can't unbuild a product architecture or undo 18 months of engineering work.

Every CPO eventually discovers that Product isn't magical; it's political, human and shaped by incentives as much as insights.

At FinCredit, a regulated consumer-loan company, I experienced it first-hand. Picture this: choosing between upgrading Portugal to your new platform versus launching a new product line for Italy. Portugal needed investment. Italy meant meaningful new revenue. We could only do one in the next six months. Sometimes the answer is simple, but the politics aren't. We chose Italy. No framework made the call. We did.

Decisions like that are what this prepares you for. You'll get decision patterns tested under pressure. They won't all work for you. You'll hear stories about where the theory didn't hold, and what we changed. The problems we couldn't solve, because boundaries matter. The messy successes, not case studies.

I'm writing from the chair, not the classroom. No seven-step playbook. Zero 4×4 matrices in sight. Just the calls.

Product leadership is judgement under constraint: time, capital, talent, ambiguous data, politics and compliance.

The most useful insights in this book didn't come from having the answers. They came from sitting with the right questions, longer than was comfortable.

If you're ready for that kind of work, let's begin.