The Product Leaders Library

Almost every second leader we coach arrives with the same sentence about the level above them: "They just don't get it." It feels like a comprehension problem. It almost never is and treating it as one quietly costs organizations their most forward-thinking minds.

Most product organizations don't think they have a conflict problem. The expensive ones are the quiet disagreements.

Business, product, and development sit in the same meetings, use the same tools, and still work past each other. The result looks like a delivery problem, but it is usually an unresolved conflict. Why cold conflicts are so expensive, and what it takes to make them workable again.

After one and a half years of AI-coding, I’m convinced, the future belongs to better specs, not bigger teams.

Double-digit million-euro investment on the line. Eighteen months later, the question had changed.

AI looks like a tools story. It isn't.

AI is transforming product development at unprecedented speed.

Your board looks healthy. Tickets move, refinement happens, sprints fill, items get marked "ready." From the outside, the system is working. But what if that movement is hiding something?

When was the last time you actually switched off — not the laptop, but your head? 62% of the 24 senior leaders in our latest assessment cohort can't anymore. And almost none of them would describe themselves as struggling.

How a public-sector IT organization nearly doubled weekly delivery.

Why are so many capable leaders running on empty — and what actually helps? A candid look at leadership fatigue, the Gallup data behind it, and the way out.

Most product organizations do not struggle because people lack skill, motivation, or good intentions. They struggle because the organization behind the product is not creating sustainable, reliable, and value-driven product outcomes.