It is easy to confuse process mastery with product success. The most critical skill is judgment—the ability to identify what truly creates customer value. This is proven not by your process, but by the ultimate business outcome: customers paying with their time or money.
Instead of a traditional story structure, present the most exciting outcome first. This immediately creates either allies who want to believe or skeptics who want to challenge you. Both states are preferable to apathy, as an engaged audience is a listening one.
Forget frameworks and documentation types; they are vanity metrics. The single most important measure of a product organization's effectiveness is its learning velocity—how quickly it can gain an insight and act upon it. A daily cycle is world-class; a monthly cycle indicates immaturity.
During M&A integration, conflict arises when teams defend their respective solutions. Re-center the conversation on the customer problem they both aimed to solve. Emphasizing that all solutions are temporary and fungible de-escalates conflict and fosters alignment around a shared, permanent goal.
In high-stakes product decisions, data alone is insufficient to persuade senior leaders. A compelling narrative that taps into emotions and vision is more effective. The better story, even with less supporting data, will often win against a data-dump because decisions are both rational and emotional.
Don't let technical debt accumulate until it cripples your ability to innovate. Product should proactively treat it as a feature to be prioritized. Use natural lulls in the product cycle to pay down debt, ensuring you can move fast when the next big market opportunity arises.
PMs often feel pressure to keep engineers busy building new features. The real job is to drive deep understanding, even if it means perfecting three core features rather than adding a fourth. It's better to pause building than to create a bloated, mediocre product that does nothing well.
Actively supporting a decision you disagree with isn't just about team cohesion. If the project fails despite your best efforts, you have collected the most credible data to prove the initial decision was wrong, which is far more convincing than if you had undermined it from the start.