The Startup
Published in

The Startup

The Three Product Owner “No”’s

Saying “No” is the most important job of the product owner. It’s really the reason d’etre for this role. But there are lots of different ways and reasons to say “No”. This is my stab at categorizing three important “No”’s a product owner can deliver.

A typical SCRUM backlog, colors imply different projects or feature areas. All images by the author.

I still like the definition of a product owner as “if you’re responsible for building a product in a company using scrum, then you’re a product owner.” Or to say…




Get smarter at building your thing. Follow to join The Startup’s +8 million monthly readers & +756K followers.

Recommended from Medium

5 Reasons why digital products fail?

Optimizing Your Critical Incidents Management Process

A basic framework for PM

Chapter 11 — The Fuzzy Front End and Problem Definition

Informational Interview with Vaheed Gaffari about Product Management

Like a lotus leaf

Lotus leaf has a unique non-stick quality. Water doesn’t adhere to it. It doesn’t absorb water. But, it must stay in the water to live.

You’re a Gem! A first look at our Rotational Product Engineering Program for new graduates

Thriving in the Midst of Product Team Turnover

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Sven Balnojan

Sven Balnojan

Ph.D., Product Manager, DevOps & Data enthusiast, and author of “Three Data Point Thursday” &

More from Medium

Why Product & Engineering Can’t Be Separate Islands

Transitioning from a Scrum Product Owner to a PMTK Product Manager

The Product Led Organisation, an actionable definition.

OKRs ≠ Strategy