Week 28, 2026
I used to believe that Product Management was simply about learning the right advice and applying it consistently. If you did enough user interviews, looked at enough dashboards, and followed enough frameworks, you would eventually get it right. That belief is everywhere in our industry. It shows up in articles, talks, and playbooks that tell you exactly what to do next. Talk to users. Be data driven. Prioritize better. Think strategically. It sounds empowering, almost comforting. But here is the uncomfortable truth I learned the hard way. Advice is not enough. In fact, advice without thinking can make you feel more lost, not less. The problem is not that Product Managers lack guidance. The problem is that most of us were never taught how to think like Product Managers.
Early in my career, I did what many Product Managers do. I followed advice very diligently. I booked user interviews, carefully wrote down quotes, and left each session feeling productive. And then I sat there staring at my notes, unsure what to do next. No one had taught me what a good question actually looks like, or how to connect answers back to decisions. The same thing happened with data. I was told to be data driven, so I built dashboards, tracked metrics, and refreshed them more often than I would like to admit. But when a decision had to be made, I struggled to explain which number mattered and why. Prioritization was no different. I learned frameworks, applied them with enthusiasm, and ended up with neatly scored lists that did not actually make decisions easier. Everything still felt important. In theory, I was doing the right things. In practice, I felt like I was copying moves without understanding the game. That is the gap advice creates when it is not paired with structured thinking.
This is where the difference between an advice driven Product Manager and a thinking driven Product Manager becomes clear. The advice driven version of me followed best practices, applied frameworks almost blindly, and kept looking for the “correct” answer. It felt like progress. It looked like learning. But it often resulted in shallow understanding and fragile decisions that fell apart under pressure. I second guessed myself constantly. I copied what others did without fully understanding why it worked for them. And despite all the effort, I still felt behind. In contrast, the thinking driven version of a Product Manager operates differently. They focus on context first. They ask better questions. They reason through trade offs instead of avoiding them. That shift changes everything. Decisions become clearer. Trade offs become explicit. Confidence stops coming from guesswork and starts coming from reasoning. Advice tells you what to do. Thinking tells you why. Frameworks do not replace judgment. Good Product Managers follow practices. Great Product Managers understand them.
What helped me move in that direction was not discovering a new framework or reading another list of tips. It was learning to break problems down in a consistent way. I started asking myself four simple questions.
- What problem are we actually solving?
- Why does it matter right now?
- What are the trade offs if we choose one direction over another?
- What would success look like if we got this right?
These questions became my anchor. Suddenly, “talk to users” had a purpose because I knew what I was trying to learn. “Be data driven” became meaningful because I knew which decision I was trying to inform. “Prioritize better” became less about scoring features and more about understanding what mattered most in a specific context. This is something you see reflected in much of the best Product Management literature, even if it is not always made explicit. Books and practitioners often emphasize outcomes, context, and decision making, but somewhere along the way, the nuance gets lost and turns into simplified advice. The real learning is not in the slogans. It is in the reasoning behind them. Product thinking is a capability. It is not a checklist.
That is why this shift matters so much, especially early in your career. Growth does not come from collecting more advice. It comes from learning how to use it. That starts with a simple habit.
- Before acting on any advice, ask why.
- Turn every recommendation into a question.
- Seek context before applying any framework.
- Look for real examples, not just principles.
- Pay attention to the order in which problems are approached and decisions are made.
- And most importantly, build your own mental models.
Because the real test of a Product Manager is not whether you know the best practices. It is whether you can figure out what to do when the situation is unclear. That is also where leadership begins. Not in giving better instructions, but in helping others think more clearly. When you build teams that can reason about problems, understand trade offs, and define success on their own, you create something much more powerful than alignment. You create autonomy. And that is when Product Management stops being about following advice and starts becoming about building judgment.
The goal is not to ignore advice. The goal is to understand it well enough to know when it applies, when it does not, and what to do when there is no playbook. Because the real problem is not that Product Managers lack advice. It is that most of us were never taught how to think like Product Managers.
This newsletter 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.
