The Four Toxic Relationships Product Managers Have With Their Product
Every PM is in a relationship with their product. Three of these patterns are destroying it. One might save it.
Every Product Manager is in a relationship with their product. And like all relationships, it can turn toxic without you even noticing.
After three decades building products and watching hundreds of PMs operate, I’ve identified four distinct relationship patterns. Three of them are destroying your product. One might save it.
1. The Lover: “My Product Can Do No Wrong”
You know this PM. They light up when talking about their product. Every feature is elegant. Every decision was the right one. Customer complaints? Users just don’t understand the vision yet.
The Lover fell in love with the solution, not the problem.
They defend technical debt like it’s a family member. They interpret declining metrics as “users need more education.” They spend more time polishing existing features than asking if those features should exist at all.
The symptom: When someone criticizes the product, it feels personal.
The cost: The Lover builds beautiful products that nobody needs. They’re so close to the canvas they can’t see the painting is hanging in an empty museum.
Steve Jobs famously said “Stay hungry, stay foolish.” The Lover heard “Stay loyal, stay blind.”
2. The Savior: “I Must Rescue These Poor Customers”
The Savior is the opposite extreme. They’re so obsessed with customer empathy that they’ve lost all product conviction.
Every customer request becomes a feature. Every complaint becomes a priority. The roadmap isn’t a strategy—it’s a suggestion box with a development team attached.
The symptom: Your product tries to be everything to everyone and ends up being nothing to anyone.
The cost: Feature bloat. Confused positioning. A product that looks like it was designed by committee—because it was. The Savior doesn’t build products; they build appeasement engines.
The Savior confuses customer obsession with customer obedience. Jeff Bezos built Amazon on customer obsession, but he never let customers design the Kindle. There’s a difference between listening and obeying.
3. The Resentful: “I Hate What This Has Become”
This is the darkest pattern, and it’s more common than anyone admits.
The Resentful PM inherited a product they didn’t build, or watched their original vision get compromised by politics, technical constraints, or market realities. Now they resent every standup, every sprint review, every customer call.
But here’s the insidious part: they don’t leave. They cover.
The Resentful PM buries their hatred under features. New functionality piled on top of functionality they despise. It’s not a product strategy—it’s a coping mechanism. Every new feature is another layer of paint over the cracks they can’t stand looking at.
The symptom: “We need to add X” is always easier than “We need to fix Y.”
The cost: Technical debt compounds. The product becomes a sedimentary rock of resentment—layer after layer of features that exist not because users need them, but because looking at the core was too painful.
Sun Tzu wrote: “If you know neither the enemy nor yourself, you will succumb in every battle.” The Resentful knows neither the customer nor their own motivations. They’re just surviving.
4. The Gardener: “This Needs Constant Pruning”
The healthy relationship isn’t love. It’s gardening.
The Gardener sees the product as a living system that requires constant attention, honest assessment, and sometimes painful cuts. They love what the product does for users, not the product itself. They’re willing to kill features, admit mistakes, and start over when needed.
The Gardener asks uncomfortable questions:
- “Does this feature still earn its place?”
- “What would we build if we started today?”
- “What are we keeping out of habit, not value?”
The symptom: Regular pruning. Features get removed, not just added.
The cost: Short-term conflict. Stakeholders don’t like hearing “no.” But the long-term payoff is a product that stays coherent while competitors bloat themselves into irrelevance.
Brian Chesky rebuilt Airbnb’s entire product organization because he realized the company had drifted from gardening into maintenance. The result? A focused product that actually reflected user needs instead of internal politics.
The Uncomfortable Truth
Most PMs cycle through all four relationships during their career—sometimes during a single quarter.
The question isn’t which relationship you want. It’s which relationship you have, right now, that you’re not admitting to yourself.
- If defending your product feels like defending your identity, you’re a Lover.
- If your roadmap is just a list of customer requests, you’re a Savior.
- If you’re excited about new features but exhausted by the existing ones, you might be Resentful.
- And if you’re willing to kill your darlings, prune relentlessly, and love outcomes over outputs—welcome to the garden.
Two Books for Two Journeys
Recognizing these patterns is step one. Mastering them is a longer journey.
If you’re working on becoming a better Product Manager—sharpening your fundamentals, improving stakeholder communication, and building the core skills that make great PMs—I wrote Top Product Manager specifically for that journey. It’s the foundation.
But if you’re sensing that the entire PM role is evolving—that AI, Founder Mode, and the rise of Product Engineers are changing what “product” means—then The Broken Telephone is about what comes next. It’s not about being a better PM. It’s about understanding why the role itself is transforming and how to stay ahead of that curve.
The first book helps you master the game. The second helps you see that the game is changing.
Which relationship are you in right now?
John Macias
Author of The Broken Telephone