Saying 'no' to product ideas is often contentious. At GitHub, the process is simplified by first 'seeking the truth'—rigorously assessing if an initiative aligns with the team's definition of success. If it doesn't, the 'no' becomes an objective, logical conclusion rather than a subjective or political decision.

Many PMs crave validation for their craft, leading them to explain processes like discovery or agile to executives. This is ineffective because executives don't care about the 'how'. Communication should focus on financial results, not methods.

A product manager's primary role is not just managing roadmaps but injecting courage into the team. This means making unpopular decisions, like scrapping a project after months of work, to ensure the team is always building the right thing, even when it's difficult or requires challenging leadership.

Product managers frequently receive solutions, not problems, from stakeholders. Instead of saying no, the effective approach is to reframe the solution as a set of assumptions and build a discovery backlog to systematically test them. This builds alignment and leads to better outcomes.

Just as PMs are warned against solution-bias, the same discipline applies to problems. The goal is not just to find one problem, but to find multiple, then assess which is most valuable, strategically aligned, and worth pursuing for the right audience before committing resources.

To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.

The ultimate sign of a product manager's influence is not receiving feature ideas, but being the go-to person for complex business problems. This indicates you are viewed as a strategic partner capable of diagnosing root causes, even when a solution isn't obvious.

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.

Product managers are trained to conduct discovery to understand user needs, yet they frequently fail to apply this same curiosity and process internally. They don't discover what sales, marketing, and other partners need to be successful, leading to a disconnect where they only focus on shipping features rather than enabling the entire business.