Winning Hearts and Minds: Persuasion Strategy for Engineering Leaders
In the end, it's not about selling an idea; it's about inspiring a movement.
In the world of software engineering, great ideas are the lifeblood of innovation. But here's the catch: having a brilliant idea is just the beginning. Convincing your team and peers to embrace that idea and turn it into reality can be the real challenge. As a software engineering leader, I've learned that persuasion is the key to success.
Understanding the Significance of Persuasion in Software Engineering
Consider this scenario: You're a software engineering leader with a game-changing concept. You could march into your team's meeting room and declare your idea as the next big thing. But, what's the likelihood that your team will jump on board with enthusiasm? Probably not very high (see Lack of Ownership).
Chelsea Troy, in her insightful post about "How to Socialize Big Changes at Work" highlights a common pitfall when introducing new ideas to a group:
Presumably, if the whole team is together, they know the topic they’re there to discuss, and they’ve agreed that it’s relevant. You show up and drag the topic onto your new thing. No one in this meeting has had the chance to agree that this thing is relevant.
So you’re co-opting time that people have given to something relevant. Co-opting people’s time without their consent annoys them, at best. It’s an emotional hurdle you don’t need in your effort to get your idea adopted.
In this context, persuasion isn't solely about selling; it's about engaging. Your team and peers need to believe in it, see its potential, and feel motivated to contribute. After all, a great idea is only as good as its execution, and that requires a committed team.
So, how to start? Feedback is the answer.
Initiating the Process with Feedback
One of the first steps in persuading your team to embrace your idea is to seek feedback. This approach may seem counterintuitive, as you might fear that criticism could derail your vision. However, feedback is vital in refining your idea and involving your team in the creative process.
Imagine presenting your idea as a rough sketch and inviting your team to contribute their thoughts. This approach fosters collaboration and helps you identify potential pitfalls early on. When people feel heard and valued, they're more likely to get on board.
In the realm of software engineering, the best way to do this is by using written communication.
By segregating the message's definition from its dissemination, you have the opportunity to meticulously craft your message to ensure that your ideas are conveyed with clarity and precision. This clarity significantly aids your audience in comprehending your perspective.
Also, written materials can be easily distributed to a wide audience, making it an efficient way to reach and persuade multiple individuals or stakeholders simultaneously, regardless of their time zones.
And last, written communication creates a permanent record of your message, which can be referred to later. In his communication course, Pat Kua highlights that writing is important to capture context.
As mentioned in his material, a good example is architecture decision records. This short text file (Michael Nygard’s definition) is used by many companies and teams to document and share the details about the trade-offs and other information that may explain the decisions that someone made over time.
When this does not happen, Pat Kua defines it as “Tribal Knowledge”:
“Tribal Knowledge” sounds fun when you’re sitting around a campfire sharing stories but other cannot benefit if that person with that “Tribal Knowledge” is no longer around.
Another important decision to make while seeking feedback is choosing the right people for it. According to Riitta Katila, your manager is definitely not the ideal candidate for initial feedback on a new idea. You should first look for people with a “creator” mindset, who are more open to fresh ideas, changes, and innovation.
Once you have started or concluded the co-creation phase using the obtained feedback, it is time to spread the message through additional voices.
Finding Internal Sponsors and Allies
Even the most revolutionary ideas need champions within the organization. These champions can be your internal sponsors and allies who support and advocate for your idea. Seek out individuals who share your vision and can help you navigate the complex landscape of organizational politics.
As per Riitta Katila’s insights, managers are 57% more likely to embrace new ideas when they are presented by someone other than the idea's originator.
Think of these allies as partners in your journey. They can help you gain the support and resources you need, making it easier to persuade others. Remember, you don't have to go alone.
A productive method for identifying these supporters within your organization is to pay attention to social interactions and identify those who share similar interests. Look for potential allies through your company's Slack channels, internal communication platforms, All Hands meetings, and other opportunities for engagement.
Effective Communication
Communication is the cornerstone of persuasion. You might have a brilliant idea, but it's unlikely to gain traction if you can't articulate it clearly. Craft a compelling narrative around your idea, emphasizing its benefits and value to the team and the organization.
Your goal is to create a shared understanding and enthusiasm for the idea. There is no better strategy for this than demonstrating its value and benefits, connected with your company’s business drivers.
Every idea, no matter how innovative, must demonstrate its worth. Showcase how your idea can address pain points, improve efficiency, or drive revenue. When your team and peers can connect the dots between your idea and tangible benefits, they're more likely to buy in.
Use real-world examples or success stories to illustrate how your idea has worked in similar contexts. People are more inclined to trust and support something with a proven track record.
Dealing with Resistance and Challenges
Resistance is inevitable. Not everyone will immediately embrace your idea, and that's okay. When faced with resistance, approach it as an opportunity for growth and learning.
Listen to concerns and objections with an open mind, and be prepared to adapt your approach. Sometimes, making small adjustments can turn skeptics into advocates. Patience and persistence are your allies in overcoming challenges.
Conclusion
In the ever-evolving world of software engineering, leadership is about more than just making decisions; it's about inspiring and guiding your team toward a shared vision. Persuasion, done with empathy and authenticity, is a powerful tool that allows you to lead with influence, not authority.
Remember, you're not selling a product; you're championing an idea that has the potential to transform your team and your organization. Use feedback, allies, effective communication, and a demonstration of value to win hearts and minds. Embrace resistance as an opportunity for growth, and watch your ideas flourish in the hands of a motivated and engaged team.
In the end, it's not about selling an idea; it's about inspiring a movement.
Very good article and well applied to reality, especially when talking about sponsors and allies. Depending on the initiative, you need common areas that spread in terms of communication and that benefit each other, to achieve better allies