The PM Mind

As a PM, you will almost never have all the information you want before making a call. That's normal. Make the best decision you can with what you have, ship it, and let the real world tell you what to fix. Doing nothing is actually the riskiest choice because you get zero new data.

When you launch a feature or make a product decision, your job is not to prove you were right — it is to find out as fast as possible whether your hypothesis holds. That means looking for evidence that breaks your idea, not evidence that supports it. If the data says you were wrong, that is a success, not a failure — you just learned something before it became expensive.

When you sketch a solution too early, your team stops exploring and starts refining that one sketch. It feels productive but you've actually narrowed your options before you understood the problem. Stay in questions and words longer than feels comfortable — the picture should be the destination, not the starting point.

When you're a new PM, every decision feels like you need more information first. But most of the time, making a decent decision quickly and learning from what happens beats waiting forever for certainty that never comes. The signal you need is often hiding in a five-minute phone call with a real customer, not in a 50-slide research deck.

As a new PM, you might think your job is to stay neutral and follow the data wherever it leads. But great PMs actually have strong points of view about what matters and why — they just don't let that become stubbornness about how to get there. Think of it as knowing exactly where you want to go, but being willing to take different roads.