When driving the controversial ComponentKit framework, Ryan Peterman didn't go it alone. He relied on influential allies who had different convincing styles and compromised by integrating a competing framework's technology. This created a shared win and brought skeptics into the fold.
When trying to influence external partners, start with those most eager to collaborate. This 'coalition of the willing' builds momentum, helps set standards, and creates social pressure for larger, slower-moving players to join the initiative.
Don't mistake an internal detractor for someone who is simply rude or against you personally. The most formidable "enemies" are often just champions for another solution or the status quo. They have power, influence, and a vested interest in another outcome, making them a mirror image of your own champion.
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.
Technologists often fail to get project approval by focusing on specs and data. A successful pitch requires a "narrative algorithm" that addresses five key drivers: empathy, engagement, alignment, evidence, and impact. This framework translates technical achievements into a compelling business story for leadership.
To get a major initiative approved, don't just pitch the vision. Interview key decision-makers beforehand and ask for every possible objection. Then, build your pitch around a mitigation plan for each concern, removing every reason for them to say 'no' before you even formally present.
When trying to convince teams to adopt a new technology, the most effective strategy is to implement the solution for them. Presenting a finished, working migration is a much easier conversation than asking them to take on a large, uncertain task themselves.
When your proposal is too far from someone's current position, it enters their "region of rejection" and is dismissed. Instead of asking for the full change at once, start with a smaller, more palatable request. This builds momentum and makes the ultimate goal seem less distant and more achievable over time.
When you identify a deal blocker, don't confront them alone. First, approach your champion and ask for their perspective on the dissenter's hesitation and advice on the best way to engage them. This provides crucial internal political context and helps you formulate a more effective strategy before you ever speak to the blocker.
When a critical technical decision is stalled, force a resolution with a timed design competition. Split all relevant tech leads into two competing teams and give them a few hours to independently architect a solution. This quickly reveals areas of consensus and isolates points of disagreement.
In large deals, internal 'enemies' often champion a competing solution. Top reps know the goal isn't to win these individuals over, which is often impossible. Instead, they focus on engaging them directly to neutralize their opposition, preventing them from actively derailing the deal.