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.

To avoid stakeholders undermining research results later ('you only talked to 38 people'), proactively collaborate with them before the study to define the minimum standard of rigor they will accept. This alignment shifts the conversation from a post-mortem critique to a pre-launch agreement, disarming future objections.

Instead of aiming for vague outcomes like "empowerment," start by defining the specific, observable behaviors you want to see. For example, what does "being data-driven" actually look like day-to-day? This focus allows you to diagnose and remove concrete barriers related to competency, accessibility, or social reinforcement.

When driving major organizational change, a data-driven approach from the start is crucial for overcoming emotional resistance to established ways of working. Building a strong business case based on financial and market metrics can depersonalize the discussion and align stakeholders more quickly than relying on vision alone.

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.

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.

To encourage participation from everyone, leaders should focus on the 'why' behind an idea (intention) and ask curious questions rather than judging the final output. This levels the playing field by rewarding effort and thoughtfulness over innate talent, making it safe for people to share imperfect ideas.

To find the true influencer, ask how a low-level problem affects high-level business goals (e.g., company growth). The person who can connect these dots, regardless of their title, holds the real power in the decision-making process. They are the one paid to connect daily actions to strategic objectives.

Instead of faking expertise, openly admitting ignorance about technical details builds trust and empowers specialists. This allows you to focus on the 'what' and 'why' of the user experience, giving engineers and designers the autonomy to own the 'how', which fosters a more collaborative and effective environment.