Marketing decisions should not be based on internal team members' subjective preferences, such as "I wouldn't click on that." Your team is not your target audience. A culture of A/B testing ideas should always take precedence over personal opinions to avoid a bad marketing environment.

Product leaders often feel they must present a perfect, unassailable plan to executives. However, the goal should be to start a discussion. Presenting an idea as an educated guess allows for a collaborative debate where you can gather more information and adjust the strategy based on leadership's feedback.

Don't design solely for the user. The best product opportunities lie at the nexus of what users truly need (not what they say they want), the company's established product principles, and its core business objectives.

When Mozilla leadership pushed to adopt the WebRender engine based on "vibes" and momentum, they ignored valid concerns from the expert graphics team. This dismissal of deep technical expertise in favor of top-down enthusiasm proved toxic and led to the departure of key senior engineers.

True product rebellion isn't disruption for its own sake. It's upholding user needs—which ultimately serve the company—against short-term schemes or departmental politics. This requires strategically giving ground on minor issues to maintain momentum on the most important, long-term goals.

When leaders use arguments like the "faster horses" quote, it's rarely about a genuine belief that research is valueless. Instead, it often signals fear—of being out of touch, of ceding the vision, or of challenging the status quo. The best response is empathy, not a factual takedown.

When products offer too many configurations, it often signals that leaders lack the conviction to make a decision. This fear of being wrong creates a confusing user experience. It's better to ship a simple, opinionated product, learn from being wrong, and then adjust, rather than shipping a convoluted experience.

Product managers often fail to get ideas funded because they speak about user needs and features, while executives focus on business growth and strategic bets. To succeed, PMs must translate user value into financial impact and business outcomes, effectively speaking the language of leadership.

Unvalidated product ideas often originate from executive leadership or adjacent departments. A product manager's critical role is to use disciplined stakeholder management and clear communication to maintain focus on solving validated user problems, rather than simply executing on top-down directives.