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.
Individual contributors are rewarded for having answers and sharing their expertise. To succeed as a leader, one must fundamentally change their approach. The job becomes about empowering others by asking insightful questions and actively listening, a diametrically opposed skillset that is difficult to adopt.
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.
Forcing innovations to "scale" via top-down mandates often fails by robbing local teams of ownership. A better approach is to let good ideas "spread." If a solution is truly valuable, other teams will naturally adopt it. This pull-based model ensures change sticks and evolves.
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.
Leaders often assume goal alignment. A simple exercise is to ask each team member to articulate the project's goal in their own words. The resulting variety in answers immediately highlights where alignment is needed before work begins, preventing wasted effort on divergent paths.
Gaining genuine team alignment is more complex than getting a superficial agreement. It involves actively surfacing unspoken assumptions and hidden contexts to ensure that when the team agrees, they are all agreeing to the same, fully understood plan.
Use the GROW model (Goal, Reality, Options, Way Forward) to structure coaching conversations. This simple set of question categories helps leaders guide their team members to find their own solutions, fostering independence and critical thinking without the leader needing to provide the answer directly.
Instead of approaching leaders first, engage end-users to gather 'ammunition' about their daily pains. They may not have buying power, but their firsthand accounts create a powerful internal case (groundswell) that you can then present to management, making the approach much warmer and more relevant.
Instead of developing a strategy alone and presenting it as a finished product (the 'cave' method), foster co-creation in a disarming, collaborative environment (the 'campfire'). This makes the resulting document a mechanism for alignment, ensuring stakeholders feel ownership and are motivated to implement the plan.