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.

Tying a PM's success to getting their project approved creates perverse incentives. Instead, frame discovery as a team effort to find the right opportunities. This encourages rigorous, unbiased investigation and celebrates killing bad ideas, not just launching new ones.

To harness new ideas without causing chaos, mandate that new employees first learn and execute tasks the established way. This forces them to understand hidden dependencies and workflows they can't see initially. Only after mastering the current system can they suggest meaningful, context-aware improvements.

Siphoning off cutting-edge work to a separate 'labs' group demotivates core teams and disconnects innovation from those who own the customer. Instead, foster 'innovating teams' by making innovation the responsibility of the core product teams themselves.

Deep experts can be "particularly dangerous" to innovation because their established knowledge can cause them to prematurely shut down novel ideas. Drawing lessons from Pixar, innovative organizations must structure creative processes to ensure that neither experts nor bosses dominate the conversation and stifle nascent concepts.

True innovation cannot be delegated to new hires. The core founding team, with its deep context and high-pressure tolerance, must personally lead and execute critical new ventures. Success comes from pointing the "Eye of Sauron" of the original team at the next big problem.

To stop teams from re-inventing the wheel or ignoring valuable existing knowledge, add a mandatory "Prior Art" section to all product briefs. This simple process change forces teams to acknowledge and build upon what other internal teams have already discovered, leveraging collective wisdom.

Jack Dorsey reframed the Product Manager role as "Product Editor." The most valuable skill is not generating new feature ideas, but exercising judgment to cut through the noise, simplify complexity, and edit the product down to the essential few things that truly drive customer outcomes.

Demanding a step-by-step logical justification for every new idea prevents exploration of truly innovative solutions. This process inherently limits a company to the same 15-20% of the solution space that competitors, using the same logic, are also exploring.