Why Product Owners Shouldn’t Exist: Industrial-Age vs Intelligence-Age
Traditional Product Owners gum up the works. See why Intelligence-age Product Owners define intent, judge output, and own the outcomes instead.
By Daniel Keith · 5 min read
Expand imageYou will see why the traditional Product Owner gums up the works, what an Intelligence-Age Product Owner looks like, and what to do on Monday with the Product Owner you have today.
We have an incredible relationship with a client. Well, had. We were building new functionality and new capabilities and churning them out on an almost daily basis. Then there was a change in leadership, and the new CIO brought in a cadre of project managers and product owners and all of the traditional resources that you know and do not love. Yes, the title of this post is provocative. What I’m really doing is drawing a distinction between Industrial-Age Product Owners and Intelligence-Age Product Owners. One is a complete waste of time and money. The other is a true owner, fully accountable for the outcomes. But, it’s more than that. It’s a realization that in the Intelligence-Age, the ways of working are dramatically different, and there’s no place in modern companies for Product Owners who spend everyone’s energy keeping the hamster wheel spinning at full speed.
The Story
The traditional Product Owner is half Project Manager and half Solutions Architect. They coordinate meetings between the actual owners (e.g. the head of a department) and the builders. They serve as the glue, which sounds great, but all they actually do is gum up the works. That is exactly what happened with our client.
Before the change, we operated with true agility, and new value was produced on a daily basis. In a week, we could produce something, get it out for use, and get feedback from the end users. Even when it was far from perfect, the users could experience it and tell us how to make it better for them.
Then the new Product Owner injected themselves into the middle of the deliverables. The number of meetings increased by a factor of 10 (no exaggeration!). Instead of producing new value weekly (sometimes daily), it was a challenge to produce anything at all.
When something was produced, it was months in the making and three to four times over budget. And it was never any better than the functionality we had built in a matter of days or weeks. The Product Owner let perfection be the enemy of good, yet the end result was no more perfect than what they could have done with far less time, far less effort, and far less expense.
Key Moments
The Eureka Moment
The new Product Owner didn’t add ownership. They added a layer. The actual owners were still the heads of the departments, and the builders were still the builders. Now every deliverable passed through someone in the middle whose job was to coordinate meetings between them. That’s the glue, and the glue doesn’t hold anything together. It just gums up the works. The meetings multiplied, and the users got nothing better for it.
The ROI Moment
The cost was easy to measure. Meetings went up by a factor of 10. A week from building something to getting end-user feedback turned into months. The work came in three to four times over budget. And what finally shipped was never any better than what had been built in days or weeks. Far less time, far less effort, and far less expense would have produced the same result.
Continuous Everything
Tenger’s approach is in our name: Modern Ways. In fact, these modern practices are part of our MVVP (mission, vision, values, and practices). Our core practice is “continuous everything”: continuous design, continuous build, continuous deployment. In fact, the only thing we don’t do continuously is the release. We deploy continuously and release on demand. With clients who embrace that mentality, time to value drops from months to days or even hours.
The Strongest Counterargument
The strongest argument for a traditional Product Owner is that you need someone who oversees the engagement and has authority to organize across departments and groups. None of that is actually true. You don’t need someone who oversees the engagement. You need someone who owns the outcomes. You don’t need someone with authority to organize across departments. You need to empower those departments to work amongst themselves, driving together toward outcomes defined by the vision of the organization.
“You don’t need someone who oversees the engagement. You need someone who owns the outcomes.”
Industrial-Age PO vs Intelligence-Age PO
Here’s how the role changes across 10 dimensions.
| Dimension | Industrial-Age PO | Intelligence-Age PO |
|---|---|---|
| Primary constraint | Engineering capacity | Judgment, attention, and risk |
| Core artifact | User stories and backlog | Executable specs, intent, constraints, acceptance criteria, evals, and guardrails |
| Cadence | Two-week sprints | Continuous. Hours from idea to deployed variant. |
| Prioritization | What fits in the sprint | What’s worth doing at all, and what not to ship |
| Acceptance | Demo review, checking the acceptance criteria | Evaluation of the design, defining how correctness is measured, and audit of the AI-generated tests |
| Team interface | Translates between business and developers | Directs humans plus agent systems. Humans become reviewers and exception handlers. |
| Discovery | Interviews, then building an MVP over weeks and months | Building several real variants in days, then testing them with users |
| Accountability | Feature delivery and velocity | Business outcomes, security, compliance, and correctness of what the AI produced |
| Key skill | Facilitation, backlog, and backlog hygiene | Systems thinking, spec-writing, domain depth, risk judgment, and AI literacy |
| Failure mode | Building too slowly | Building too much, too fast, or unverified |
The Bottom Line
Product Owners who are half Project Manager and half Solutions Architect are a complete waste of time and money. Product Owners of the Intelligence Age are a completely different breed. They focus on user experience and build solutions for themselves. They are true owners, fully accountable for the outcomes.
A traditional PO manages the flow of work through a team. In the Intelligence Age, AI handles most of the design, build, test, and deploy. The burden on the modern PO shifts to defining intent, judging output, and owning outcomes.
Do This on Monday
In the Intelligence Age, you don’t need a bunch of team members doing all of the work. Modern POs do most of the work themselves utilizing AI for more than 90% of the build. If you have a Product Owner today, here’s where to start:
- Offboard or Retrain. Retrain only if they have the aptitude and personality to serve as a modern PO.
- Shift the Burden. Move the role from managing the flow of work through a team to defining intent, judging output, and owning outcomes.
- Empower the Departments. Let them work amongst themselves toward outcomes defined by your organization’s vision.
Our mission is to free people to do their best work, and that includes the people stuck in meetings with your Product Owner. If that’s you, let’s talk. Contact Us to keep the conversation going.
Daniel Keith
About the Author
Daniel Keith helped start Tenger Ways, where he helps enterprise IT build simple tools that people actually want to use.



