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.

Shifting from a black-and-white "right vs. wrong" mindset to a probabilistic one (e.g., "I'm 80% sure") reduces personal attachment to ideas. This makes group discussions more fluid and productive, as people become more open to considering alternative viewpoints they might otherwise dismiss.

Leaders are often trapped "inside the box" of their own assumptions when making critical decisions. By providing AI with context and assigning it an expert role (e.g., "world-class chief product officer"), you can prompt it to ask probing questions that reveal your biases and lead to more objective, defensible outcomes.

To evaluate ideas without getting bogged down, use a simple framework: What is the idea? Why is it important? Who will it impact? Explicitly avoiding the 'how' prevents premature criticism and focuses the discussion on strategic value.

To prevent review meetings from becoming about personal opinions, enforce a rule: all criticism must be linked to a testable hypothesis or a clear gap in existing data. This transforms subjective feedback into an objective, evidence-based discussion about what needs to be validated next.

Leaders invest heavily in flawed products because their personal effort creates an emotional attachment, a cognitive bias known as the IKEA effect. They rationalize this by citing outliers like Steve Jobs, ignoring the vast majority who fail with this "strategy."

AI models tend to be overly optimistic. To get a balanced market analysis, explicitly instruct AI research tools like Perplexity to act as a "devil's advocate." This helps uncover risks, challenge assumptions, and makes it easier for product managers to say "no" to weak ideas quickly.

Counteract the tendency for the highest-paid person's opinion (HIPPO) to dominate decisions. Position all stakeholder ideas, regardless of seniority, as valid hypotheses to be tested. This makes objective data, not job titles, the ultimate arbiter for website changes, fostering a more effective culture.

This framework structures decision-making by prioritizing three hierarchical layers: 1) Mission (the customer/purpose), 2) Team (the business's financial health), and 3) Self (individual skills and passions). It provides a common language for debating choices and ensuring personal desires don't override the mission or business viability.