A resignation can be an opportunity
Kamusta mundo! (“Hello World” in Tagalog)
Welcome back to the newsletter, and thanks again for reading/subscribing. Please share with anyone you think would appreciate it!
About this newsletter
What makes this newsletter unique is that every two weeks, I share a chapter from my book It Depends: Writing on Technology Leadership 2012-2022, which Unit Circle Press released in March of last year. These chapters are not sequential; each is a standalone piece. In addition, a podcast serializes the audiobook in order, released alternate weeks from this newsletter.
The Latest Podcast
The latest episode of the podcast is “Changing Hiring Practices to Build a More Diverse Technology Organization.” It’s a case study of our changes at Avvo to reduce bias in our hiring practices, which helped us significantly improve the engineering organization's diversity. If you believe the research that diverse teams outperform homogenous teams (I have personal experience that this is true!), the question is always, “How do I improve the diversity of my team?” Once you have addressed the main cultural blockers, the next step is hiring because that is the only way to change the makeup of a team. This chapter and the podcast will give you ideas of where to start. I shared the text of the chapter almost a year ago in this newsletter.
You can download the episode from Apple Podcasts, Spotify, YouTube, directly via the RSS Feed, or wherever you listen to podcasts (see pod.link for a more extensive list).
Please send me your questions about being or becoming a CTO
Do you want to know what it is like to be a CTO? Are you already a CTO and having some challenges? Do you want to understand the C-level career path better? Please send me your questions! contact@itdependsbook.net. You can also add them to the chat on Substack or in the comments for this post.
Reader Survey
I’m thinking about what happens to this newsletter and the podcast after we complete the book. I want your help! Please complete a very quick and anonymous survey to help me out.
About this week’s chapter
This is one of the most critical chapters in the book. Some of you will not need my advice, but in my experience, most will. I’ve seen many managers tie themselves up in knots when one of their direct reports hands in their resignation. They think about what they are losing instead of considering what they could gain. Even a high-performing team working well together for a while can use an infusion of new energy, new perspectives, and new skills. This chapter exhorts you to think about what change can do to improve your team when you have to replace someone.
This chapter was shared on the podcast in July of 2024.
This is chapter 16 of It Depends.
A resignation can be an opportunity
Originally published on August 27, 2020
People leave jobs. If you are a manager, people will leave your team, just as someday you will leave your team.
When this happens it is an opportunity, a chance to re-evaluate. While you might want to immediately pull out the job description that you used when hiring for the role last time, instead, take some time to think.
A chance to learn
When someone tells you that they are resigning, it can feel personal: ‘they don’t like working for me.’ It can hurt. You might immediately look for any reason why it isn’t your fault. It is natural to want to move on as quickly as possible. You may even obsess about everything that you could have done differently.
Instead, after an employee gives you notice, take a day or two to process and get some distance. Recenter. Then meet with them. Come back to them with an open mind. Do not look to assign blame, let them know that you are working to improve the team for the people that are still here. Ask what did not work for them and what they will miss, aiming not to assign any extra meaning to what they say. Take notes. Thank them.
Take some more time to create mental distance, then come back again and think about the leaver’s words. Try to understand from their perspective what they experienced. If they are taking a more senior role elsewhere, was there a similar opportunity in your company that you could have helped them get? If they are joining another company to learn a different technology, was it a technology they could have explored in your organization? Was there another team in your company that they could have joined instead?
Your goal is to understand their unmet needs. Were there signs that you missed? Were there opportunities in your company or in your team that could have addressed their needs?
Once again, the goal is not to assign blame, and the goal is not to get the employee to change their mind either. The goal is to learn from this experience.
So moving forward, how can you approach your role in a better way?
Consider this process to be a personal retrospective, and just like in an Agile team retrospective, you may want to emerge with a list of things to keep doing, a list of things to start doing, and a list of things to stop doing.
A chance to change
As teams evolve they shift and mature. If the leaver has been in the group for a long time, they may have accumulated an unusual set of responsibilities and they may have influenced the technical decisions around their strengths.
While it may seem like the obvious decision is to look for someone with the same skill set, that is just ‘role inertia’ (credit to Omosola Odetunde for introducing that phrase to me). Instead think of this as an opportunity to re-evaluate and make a change without impacting someone.
Consider your technical vision for the team and the skill sets of others in the group. Is there something missing that could help you today or in the future? Is this role still needed? Should you repurpose the position into a different one based on the team’s long-term needs?
It is critical to think about long-term needs and not short-term ones. A mistake managers often make is that they hire someone because of near-term demand. They assume that there will be a headcount later to cover the long-term need, but too often that headcount doesn’t appear and now the team is missing a crucial skill set.
Potentially your team is out of balance, where you have too many (or too few) senior folks. This opportunity means you can now rebalance the levels within the group. Maybe this role is no longer necessary and you can give a headcount to another team that needs it more, or potentially there is someone on the team who is looking for a new challenge and can step into the role.
If you are in a position where you manage multiple teams then this may be an opportunity to re-evaluate the team structure, especially if the leaver is a manager. A way to approach this exercise would be to imagine that the person leaving was never on the team. Your manager has given you a brand new headcount and asked you to figure out how you want to use it.
Once you have a plan, you can then write the job description and look to fill the role, as you may decide that you need to replace the person with someone who has a similar skill set. If so, you can move forward confidently knowing that you have thought it through, and if you have also taken the time to learn you will hopefully retain your new hire for a long time.
Thanks again for reading! If you find it helpful, please share it with your friends.
Buy on Amazon | Buy on Bookshop.org | Buy on Audible | Other stores