Marty Cagan on Product’s Big Reckoning
Lately I’ve been in a lot of conversations with product people and founders about the push and pull between execution and strategy, and what “good” product managers should actually be doing in the middle of it. In some teams PMs own the roadmap and the narrative. In others they are almost Jira admins with nicer job titles.
Which is why the conversation between Lenny Rachitsky (Lennys Podcast) and Marty Cagan was interesting to me.
I think most Product people know of Marty. When I was hiring the Product team at Messagemedia a few of the team had his book Inspired on their desks. Marty has been working with product teams for more than two decades. He has seen more product organisations from the inside than almost anyone else, and he’s written three of the core texts in the field: Inspired, Empowered and now Transformed. When he says the industry is in a reckoning, it’s worth paying attention.
This is my take on that discussion, written for founders, functional leaders and cross-functional teams who are trying to build real products, not just ship features.
1. Most “product management” is just project management in disguise
Marty is blunt: a lot of companies over-hired during the pandemic, and not just on engineering. They added every adjacent role you can imagine: agile coaches, product owners, product ops, business analysts, assistant PMs, multiple types of project manager.
On a slidedeck it looks sophisticated. In reality, he thinks a lot of it is theatre.
In Marty’s language, most of these are feature teams. They are handed a roadmap of output and a set of dates. The “product manager” job in that model is to:
- keep the backlog updated
- attend ceremonies
- chase stakeholders
- make sure features ship roughly on time
Useful work, but it is coordination, not product.
I think that this gap explains some of the misunderstanding around the role. In a feature factory, the PM is responsible for output, not outcomes. You already have people who can do that.
Marty’s observation is that many of these roles are dramatically overpaid for the value they provide.
For founders and leaders, that leads to a simple test:
Are your “product managers” actually managing products, or managing projects?
If it is the latter, you may want to think more deeply about this.
2. The real split: feature teams vs empowered product teams
The distinction Marty cares about is straightforward:
- Feature teams are given solutions to ship
- Empowered product teams are given problems to solve
Feature team brief:
“Here’s the roadmap. Build these features. We’ve already promised them. You’re accountable for the dates.”
Empowered product team brief:
“Churn in this segment is hurting growth. Over the next quarter, reduce it by Y%. You’re accountable for the outcome.”
Marty believes that everything then flows from that.
Feature teams optimise time to market. Product teams optimise time to money.
Feature teams “get points” for shipping. Product teams “get points” for moving a metric that matters.
In that second world, the product manager’s job changes completely. They are no longer a facilitator between stakeholders and a backlog. They are a creator, alongside design and engineering.
Their responsibilities shift to:
- Value – does this solve a meaningful customer problem?
- Viability – can the business sell, support and afford this, within legal, compliance, data and monetisation constraints?
Engineers still own feasibility. Designers still own usability. The PM owns the intersection of customers, data, market and business model.
For a founder, this is where a PM stops being overhead and starts being a force multiplier. If you are willing to give a team a real problem and trust them with the outcome, a strong product manager becomes one of the highest-leverage people in the business.
3. The reckoning: bloat, remote and AI
Marty’s tone was at times sharper than other interviews because a few forces have collided:
- Pandemic over-hiring, followed by cuts
- Higher interest rates, so far less patience for functions that cannot show impact
- Remote work, which in many companies has quietly reduced both velocity and innovation
- Generative AI, which is already chewing through admin-heavy, low judgement work
If your “product management” function is mostly:
- writing tickets
- updating decks
- policing process
- coordinating stakeholders
then AI will take a big bite out of that.
This is why he is so direct about backlog administrators and feature-team PMs being vulnerable. They are easy to remove because they are not meaningfully tied to outcomes. If you’re currently a PM that finds themselves doing more of this kind of work then you might want to think about what needs to change.
AI does not remove the need for product thinking. It makes the contrast sharper between people who truly understand customers, markets and business models, and people who are shepherding work through a process.
4. What “good” looks like: the product operating model
Marty’s new book gives a label to what great companies already do: the product operating model.
Underneath the name, it is quite simple:
- Leaders make real bets They set clear product strategy. They choose which problems matter and in what order. This is not shipping a big feature list, it is picking the right problems.
- Teams own problems, not tickets Cross-functional teams have the skills in the room to discover, deliver and measure solutions:
- Principles beat process Practices vary, but the principles in strong product companies tend to rhyme:
A lot of organisations try to fake this by layering new frameworks over old behaviour, with more roles and more governance. Marty’s view is clear: that is product theatre, not transformation.
The pattern that works is almost the opposite: fewer roles, clearer responsibility, more accountability for outcomes.
For startups, you do not need every piece of the model. You do need the spirit of it: explicit bets, problem-led briefs, and proof that what you ship actually works.
5. What this means for founders and leaders
Viewed through a startup lens, a few practical points drop out.
Hire PMs later, and expect more from them
When you do hire PMs, be explicit:
- They are not there just to run stand-ups and tidy Jira
- They are there to own value and viability, with design and engineering as partners
- They are accountable for outcomes, not just ship dates
If you cannot describe the role that way, you may not be ready for it.
Smaller cross-functional teams, with clear outcomes and real ownership, will almost always beat large, fragmented teams where no one truly owns the result.
6. A quick word to PMs and cross-functional teams
If you are a PM reading this in a feature team, Marty is actually optimistic about your options.
You can start shifting your own role:
- move from “backlog owner” to “value and viability owner”
- get much closer to customers and data
- frame your work in outcomes, even if you were handed output
At worst, you become far more employable somewhere else. At best, you become the person your current leadership trusts when they want to move towards empowered product teams.
For designers, engineers and functional leaders, it is also a useful lens to evaluate your PM partners. Do they really understand customers and the business, or are they just moving tickets? The difference matters more in an AI-heavy world, not less.
The strategy versus execution tension is not solved by adding more roles, more ceremonies or more frameworks. It is solved when:
- leaders make clear bets
- teams own real problems
- PMs are hired and supported to do actual product work, not theatre
- everyone cares more about time to money than time to market
This is already how the best teams work.
Before you go, can you help me out?
Nearly 1300 people have now subscribed to this newsletter in ~20 weeks, which makes me feel that it’s resonating. So thank you to all of you 🙏🏻
If you found this issue useful, here are four ways you could support me:
- Share it – Forward this to a founder, leader. hiring manager, or job seeker who you think might find it useful and/or interesting.
- Subscribe to this newsletter
- Follow and/or connect with me on LinkedIn if you’re not already – https://www.linkedin.com/in/simonfromcrew/
- Send feedback – What topics would help you most? What’s working? What isn’t? Just hit reply.
These small actions make a massive difference in helping me reach more people who need this content.
Thanks for being here. Have a brilliant week ahead.
Weekly newsletter drop: Wednesday, 1:30pm
Need hiring help?
If you’re struggling with a specific hiring challenge, I still offer 1:1 strategy calls through my consultancy, Crew. Book a 15-minute clarity call here.
Simon
