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.

To empower your team, enforce the '1-3-1 rule' for problem-solving. Before anyone can escalate an issue to you, they must define the one problem, research three potential solutions, and present their single best recommendation. This forces critical thinking and shifts the team from problem-spotters to problem-solvers.

To predict the future health of a partnership, intentionally have difficult conversations before any investment is made. If you can't productively disagree or discuss serious problems before you're formally linked, it's highly unlikely you'll be able to do so when the stakes are higher post-investment.

Early-stage ideas are easily killed by practical objections. To prevent this, implement a rule where feedback must begin with "Yes, and...". This forces critics to be additive and constructive, building upon the initial concept rather than immediately shutting it down. It creates space for a bold idea to develop before facing harsh reality checks.

At Crisp.ai, the core value is that the best argument always wins, regardless of who it comes from—a new junior employee or the company founder. This approach flattens hierarchy and ensures that the best ideas, which often originate from those closest to the product and customers (engineers, PMs), are prioritized.

America's governing system was intentionally designed for messy debate among multiple factions. This constant disagreement is not a flaw but a feature that prevents any single group from gaining absolute power. This principle applies to organizations: fostering dissent and requiring compromise leads to more resilient and balanced outcomes.

For data-less decisions, PhonePe's co-founders have a simple rule: the partner with deeper historical strength in that domain makes the final call. The other commits fully, and they never revisit the decision, ensuring they learn and move forward without blame.

When a senior stakeholder proposes a potentially disruptive idea, direct resistance ('pushing') is counterproductive and strengthens their resolve. Instead, 'pull' them into a collaborative exploration. Acknowledge the idea, discuss the underlying problem it solves, and then gently steer the conversation back to how it aligns with the agreed-upon North Star, defusing tension.