Welcome!
Welcome to Developing Skills - Skills for Developers looking to develop their careers.
Tip of The Week: Become Better At Influencing Without Authority
As a software engineer being able to influence without authority is a crucial skill. It helps you gain support from stakeholders, improve collaboration, and drive technical decision making.
So what is it?
Influencing without authority is the ability to shape decisions and drive actions without holding hierarchical power over others. It is particularly valuable when projects involve multiple teams, each contributing their expertise to achieve organisational goals.
You don’t need to be the most senior person in the room to have influence. Building you soft skills such as: deep listening, effective assertion, and self-awareness can allow you to influence people around you.
Here’s 8 more tips to improve your influence:
Build credibility and trust - leverage your expertise, speak the language of your colleagues (including the non-technical ones), and demonstrate an understanding and empathy for their needs, show mutual respect and be reliable.
Build allies and leverage their support - Cultivate a solid network of allies within your organisation. Allies can provide everything from momentum through to actual authority if you find a high level sponsor.
Find the common ground - understand other's needs and align your goals with theirs. Show how what you’re pushing for aligns with their goals.
Listen to understand - to effectively communicate, listen carefully to your audience, empathising with their needs and asking questions to really understand their point of view.
Use storytelling - Passionate storytelling can inspire others and create a shared sense of purpose.
Bring solutions, not more problems - Present practical solutions. Don’t present a problem then add more problems to the pile. Being someone who proactively solves problems builds credibility.
Leave you ego at the door - Focus on acting with high emotional intelligence and a low ego. Ensure your mindset is geared towards collaboration and if necessary compromise to find the best solution for all.
Expect push back - accept that resistance is a natural part of the influencing process. Instead of being disheartened view it as a sign that this is viewed as a significant change, they look to understand why and offer re-assurance.
Two Ways I Can Help You Level Up As A Software Engineer:
I write another newsletter, Coding Challenges that helps you become a better software engineer through coding challenges that build real applications.
I have some courses available:
Build Your Own Redis Server (Python Edition) which guides you through solving the Redis Coding Challenge in Python.
Build Your Own Shell (Go Edition) which guides you through solving the Shell Coding Challenge in Go.
This is a great writeup.
"Build credibility and trust" would give you a foot into the door. As a new team member or a junior engineer, that should be most important thing to tackle.
Love this article! One of the best ways to build trust (and influence) I’ve learned as a PM is to do the things you said you’d do and TELL people you did them. They feel seen and heard. Repeat this a few times and they trust you to get shit done. Eventually they trust you with decisions you make and ideas you bring. Influence. This applies to everyone and not just PMs