Being a great product manager is a moving target. The fundamentals have not changed much, but the context has. AI is reshaping how product work gets done, the bar for what counts as "good" has risen, and what is expected of PMs is broader than ever.
These ten strategies reflect what strong product managers are doing right now.
1. Listen to your customers
The best product managers build a steady habit of weekly customer contact, not a research sprint every quarter, but short, regular conversations. Over time, this builds a real picture of how your product fits into people's lives and where it lets them down.
The "Jobs to Be Done" framework is still one of the most useful lenses here. Customers are not evaluating your feature list. They are asking whether your product helps them get something done, in their specific situation. Surface-level feedback rarely reveals this, but curious conversations do.
2. Embrace the challenge
Instead of seeking validation, seek contradiction.
When asking for feedback, do not ask "what do you think?" Ask "what does not make sense?" or "where does this fall apart?" These questions are harder to answer comfortably, which is exactly why they produce better insights.
The 5 Whys technique is useful here. When you identify a problem, keep asking why. Most teams stop at the first plausible explanation. The real cause is usually deeper, and finding it changes what you actually need to build. When your team is aligned on a direction, that is a good moment to ask who disagrees and why.
3. Diversify your research
No single research method gives you the full picture.
Quantitative data tells you what is happening. Qualitative research tells you why. Relying too heavily on either creates blind spots. The combination is what builds real understanding.
AI tools have made it faster to process large volumes of feedback and surface common themes, which is useful. But they can only work with what customers chose to say. They do not replace the depth that comes from a well-run user interview or an honest conversation with a frustrated customer.
Discover the nuances of mixed methods research by reading Wim Oers' comprehensive article, which provides a clear understanding of how to successfully apply this research approach.
4. Use AI to work smarter, not just faster
AI tools are now part of the job. If you are not using them actively, you are probably working slower than you need to be.
Research synthesis, first drafts of specs, backlog hygiene, these are all meaningfully faster with AI assistance. But there is a real risk alongside the benefit. The judgment that matters most in product management, deciding which problems are worth solving and which direction to take, requires context that AI tools do not have.
Treat AI-generated analysis as a first draft, not a conclusion. Check it against what you know from direct customer conversations.
5. Become an expert in your domain
Domain knowledge compounds over time. A PM who understands their industry deeply will surface better insights, frame problems more precisely, and evaluate solutions against what actually makes sense in context.
When you are new to a domain, seek out the people who know it well: authors, conference speakers, experienced practitioners. Many are willing to share what they know with someone who is curious.
As you develop expertise, periodically step back and approach your domain as a newcomer. What are first-time users discovering? What assumptions have you stopped questioning that might be worth revisiting?
6. Consider opposing views
Strong product decisions come from engaging seriously with the arguments against them.
Before committing to a direction, build the strongest possible case against it, if you cannot do this, the decision has not been thought through carefully enough. Red Team exercises make this structural: assign someone to argue against the proposed direction with genuine effort. The friction that results is how decisions get better before they are made rather than after.
When a stakeholder raises a concern, resist the instinct to defend your position. Get curious instead, sometimes the objection reveals a real gap.
7. Work as a team with your designer and engineer
The most expensive product mistakes tend to follow the same pattern. The PM writes a spec, the designer produces mockups, the engineer builds and ships. Then a post-launch review reveals the solution answered the request but not the actual underlying problem, something that would have been visible if the three people involved had been thinking through it together from the start.
Working as a product trio produces consistently better results.
- The PM focuses on whether this creates real value.
- The designer on whether it will be easy to use.
- The engineer on how to build it well, often spotting a smarter approach no one else would have considered.
These perspectives need to meet early, not late.
8. Speak the language of the business
Many strong product managers struggle to have a credible conversation with their CFO or CEO about why their work matters.
The people who control budgets think in terms of revenue, cost, risk, and growth. When product thinking cannot be translated into those terms, it gets deprioritised when it counts most.
The translation is learnable, the underlying product thinking does not change. The way you communicate it does, and that difference determines whether your priorities survive the next budget conversation.
9. Understand your team
For product managers who lead people, the biggest trap is treating everyone the same way. A junior PM needs clear guidance on how to frame problems and make trade-offs visible.
Adapting to where each person actually is requires attention. Where does this person move confidently? Where do they hesitate? The answers should change how you work with each person, and keep changing as they develop. Real one-to-ones, focused on how someone is thinking rather than what they are delivering, are one of the most direct investments you can make in your team's quality.
10. Prevent problems before they arise
The best product managers reduce how often they have to react by building the habit of thinking ahead.
The pre-mortem is one of the most practical tools for this. Before a project moves forward, imagine it has already failed and ask what went wrong. Most teams, when they do this honestly, find at least one assumption they were about to act on without questioning. That alone makes it worth doing.
Beyond specific projects, build a small set of regular metrics you check and understand well enough to interpret. When something moves unexpectedly, the PM who already understands the baseline responds faster and more accurately than one encountering it fresh.
In summary
Becoming a great product manager is about much more than just managing products. It's about organising, questioning, listening, collaborating, focusing, arguing, overcoming, adapting, and, most importantly, preventing.
These ten strategies are habits. They require consistent effort to maintain, especially when the organisation is pulling in a different direction.
The question worth sitting with is not which of these you already do. It is which ones you are actively protecting, and whether your current environment makes that easier or harder to sustain.
