We scan new podcasts and send you the top 5 insights daily.
At 10x Genomics, McDonnell learned that to gain buy-in from smart, 'finicky' scientists, one must avoid a critical posture. The most effective approach is framing ideas collaboratively, asking, 'Hey, I have an idea. What do you think?' This fosters consent and encourages meaningful contributions rather than defensive reactions.
Product leaders often feel they must present a perfect, unassailable plan to executives. However, the goal should be to start a discussion. Presenting an idea as an educated guess allows for a collaborative debate where you can gather more information and adjust the strategy based on leadership's feedback.
To transform team dynamics, leaders should intentionally ask questions that invite challenges and alternative viewpoints. Simple prompts like 'What might we be missing here?' or 'Does anyone have a different point of view?' create psychological safety and signal that all contributions are valued.
The goal of asking questions isn't just for you to gather information. It's a Socratic dialogue designed to help stakeholders think differently and arrive at the real need themselves. By guiding their thought process, you build deeper alignment and co-create a better solution, rather than just extracting requirements for yourself to fulfill.
Don't pitch big ideas by going straight to the CEO for a mandate; this alienates the teams who must execute. Instead, introduce ideas casually to find a small group of collaborative "yes, and" thinkers. Build momentum with this core coalition before presenting the developed concept more broadly.
When an executive says something you think is wrong, don't confront them. Instead, disarm them with a curious question like, "That's so interesting. What led you to believe that?" This shows respect, uncovers hidden context (like board pressure), and shifts the dynamic from a disagreement to co-creation.
When an engineer proposes a flawed idea, directly saying "no" can cause resentment. A more effective leadership technique is to ask guiding questions about potential impacts. This allows the individual to discover the flaws themselves, fostering independent problem-solving and preserving their autonomy and confidence.
In tense executive meetings, this simple verbal tool can de-escalate conflict. By starting with two points of agreement ("I like...") before posing a question ("I wonder if..."), you validate the other person, lower defensiveness, and create space for alternative ideas.
To introduce a new idea, a leader shouldn't dictate terms. Instead, they should pose it as a discussion topic and listen to the language the team uses (e.g., "cost of living" vs. "inflation"). Adopting their terminology builds shared understanding and makes people feel heard, which enables collective action.
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 gain buy-in, guide people to your desired outcome through a curated series of questions. This allows them to feel like they are discovering the solution themselves, creating a powerful sense of ownership. They are more likely to commit to a conclusion they feel they helped create.