Most advice for Product Managers focuses on how to think: frameworks for prioritization, models for strategy, techniques for discovery. But very little is said about an equally important skill – learning to rethink.

Rethinking is the ability to question your own assumptions, update your beliefs when the evidence changes, and let go of ideas you were once sure about. It is what separates PMs who ship the right things from those who ship confidently in the wrong direction.

The trap of first conclusions

When you form an opinion early in a project – about what users need, about which solution is best, about why a metric is moving – your brain starts working to confirm it. This is confirmation bias, and it is especially dangerous in product work because:

  • You have authority. When a PM says “I believe X,” the team tends to align around it.
  • Feedback loops are slow. You might not learn you were wrong for weeks or months.
  • Sunk cost kicks in. The more you invest in a direction, the harder it is to change course.

The result is that many product decisions aren’t really decisions at all – they’re early assumptions that were never revisited.

What rethinking looks like in practice

Rethinking isn’t about being indecisive. It’s about building habits that keep you honest:

1. Treat your roadmap as a set of hypotheses

Every item on your roadmap is a bet. Frame it that way. Instead of “We’re building feature X,” try “We believe feature X will improve retention by Y% because of Z.” This makes it natural to revisit the bet when new data comes in.

2. Seek out disconfirming evidence

When you’re evaluating a product decision, actively look for reasons you might be wrong. Talk to the users who didn’t adopt your feature. Read the support tickets that contradict your narrative. Ask your team, “What would have to be true for this to be the wrong call?”

3. Separate your identity from your ideas

The moment you tie your ego to a product decision, rethinking becomes a threat instead of a tool. Practice saying “I was wrong about this” out loud. The more you do it, the easier it gets, and the more your team will trust you for it.

4. Create rethinking rituals

Build structured moments to revisit past decisions:

  • Monthly assumption audits – review the key assumptions behind your current priorities. Are they still valid?
  • Pre-mortems – before launching, imagine the initiative failed. What went wrong? This surfaces risks your optimism is hiding.
  • Retros focused on beliefs – instead of just “what went well / what didn’t,” ask “what did we believe that turned out to be wrong?”

Why this matters more in the age of AI

If you’re building products that involve AI or machine learning, the need to rethink is even more acute. The capabilities of these systems change rapidly. What was impossible six months ago may now be a solved problem. A PM who clings to outdated assumptions about what AI can or can’t do will consistently miss opportunities – or invest in the wrong ones.

The best AI product managers I’ve seen share a common trait: they hold their mental models loosely. They stay close to the technology, update their intuitions frequently, and aren’t afraid to pivot when the landscape shifts.

The bottom line

Thinking well gets you into product management. Rethinking well is what makes you great at it. The PMs who have the biggest impact aren’t the ones with the best initial instincts – they’re the ones who update fastest when reality disagrees with their plan.

Build the habit of questioning your own conclusions. Your users, your team, and your products will be better for it.