Week 23, 2026
There is an idea I used to believe without questioning. If you hire a strong Product Manager, you will build a strong product. It sounds logical. It feels clean. It gives leadership a clear lever to pull. Hire better PMs, get better outcomes. I have seen this assumption play out across teams and across products. And I have seen where it quietly breaks. The uncomfortable truth is this. Product management is too important to leave only to Product Managers. The moment we treat product thinking as something owned by one role, we unintentionally weaken the very thing we are trying to strengthen. Because product thinking is not a role. It is a way of thinking. And when it stays locked inside one person, the result is almost always the same. Slow decisions. Shallow reasoning. Average products.
Early in my career, I leaned into the idea of being the single brain behind the product. I defined the problems. I drove prioritization. I was the one expected to connect all the dots. On the surface, it felt like strong leadership. There was clarity. There was control. There was a single point of accountability. But what I did not see at the time was what was quietly forming underneath. Bottlenecks started to appear. Teams waited for direction instead of thinking for themselves. Conversations narrowed instead of expanding. And over time, the quality of decisions did not improve. It plateaued. Because the product was being shaped by one perspective, no matter how informed that perspective was. That is when it clicked for me. The Product Manager is not the product. And the Product Manager should not be the only one thinking about it.
The best product outcomes I have been part of did not come from Product Manager led decisions alone. They came from teams that thought like product people, regardless of their title. I remember one engineer who stopped a feature halfway through development and asked a simple question. Are we solving the right problem? That question saved us weeks of work and redirected us toward something that actually mattered. I have seen program managers challenge whether we were even working on the highest priority problem in the first place. I have seen operations partners point out exactly how something would break the moment it hit the real world. None of these people had Product Manager in their title. Yet they were practicing product thinking at the highest level. They were questioning value. They were evaluating trade offs. They were connecting decisions to outcomes. That is when I started to see the real pattern. Great products are not built by great Product Managers alone. They are built by teams where everyone thinks like a Product Manager.
There is a very real emotional shift that happens when teams move from Product Manager centric thinking to team based product thinking. When everything flows through the Product Manager, decisions slow down because one person becomes the gate. Ownership weakens because others feel less responsible for the outcome. Product quality suffers because perspective is limited. It creates the illusion of leadership while quietly degrading the system. In contrast, when teams share product thinking, everything changes. Decisions improve because multiple perspectives challenge assumptions. Accountability increases because everyone sees themselves as responsible for the result. The product gets better because it is shaped by a richer understanding of users, constraints, and consequences. No framework, no roadmap, no prioritization tool can compensate for a team that does not think critically about value and trade offs. Product thinking is a capability, not a process.
This realization forced me to rethink what it actually means to be a good Product Manager. It is not about having all the answers. It is not about being the smartest person in the room. It is not about controlling every decision. The best Product Managers I have worked with do something else entirely. They do not hoard context. They create it and share it. They do not act as the single brain of the product. They build many. They do not protect decisions. They explain trade offs. They actively teach others how to evaluate problems and reason about outcomes. In a strange way, the goal becomes to make yourself slightly redundant. Not irrelevant. But no longer the bottleneck. When the team can reason about problems without waiting for you, you are finally free to focus on the hardest and most ambiguous challenges. That is real leverage.
There are a few reframes I keep coming back to. Product thinking is not a title. The Product Manager is not the product. Strong products come from strong teams, not heroic roles. And maybe the most important one. Great product execution is not when the Product Manager makes every call. It is when the team can make great calls together. That is the real test of product maturity. Not whether the Product Manager has all the answers. But whether the team can reason about decisions without depending on one person.
If you are a Product Manager, there is a practical way to move toward this. Make priorities explicit so others can challenge them. Explain trade offs instead of just sharing decisions. Invite dissent and reward it when it improves thinking. Teach others how to evaluate problems, not just how to execute solutions. And most importantly, build teams that can think independently. The goal is not to remove Product Managers. The goal is to remove the dependency on a single product brain. That is what turns good products into remarkable ones.
DISCLAIMER: This post reflects my personal views and experiences as a product manager. It does not represent the views, strategies, or opinions of my employer or any organization I am affiliated with.
