If You Can't Be Replaced You Can't Be Promoted. Career Growth Through Succession Planning.

Sign in<br>Subscribe

Welcome to my newsletter! I'm Dave Anderson, an ex-Amazon Tech Director and GM. I write this newsletter I've called Scarlet Ink, which is a weekly newsletter on tech industry careers and tactical leadership advice.<br>Free members can read some amount of each article, while paid members can read the full article. For some, part of the article is plenty! But if you'd like to read more, I'd love you to consider becoming a paid member. All of my articles are intended to be evergreen (readable and valid forever). Some weeks I have fresh content; other weeks I'll update/rewrite something from 4+ years ago because I want to keep the quality of all articles high.<br>And yes, this article applies to engineers, project managers, and designers. Everyone needs to think about who will replace them.<br>Years ago, I was internally hired to build the engineering organization for Kids Devices. The existing engineering group was small (a total of approximately 20 people), and the business was profitable and growing quickly.<br>I'd chosen this position specifically because of the promise of growth. I knew that if nothing changed regarding business profitability and growth trajectory, the engineering organization was almost guaranteed to grow quickly. My goal was to find a role that would bring me from a Level 7 Senior Engineering Manager to a Level 8 Director of Technology. A promotion at this level is a difficult promotion to get, so I had to approach it purposefully.<br>When I joined, I already had quite a few open positions. I certainly put out feelers to engineers I knew to help the engineering managers on my team fill out their open positions. But I made one hire my top priority. My successor.<br>I'd just been hired into the group. And part of my hiring agreement was that I'd committed to my manager (the Director of the organization) that I would stick around for 3 years. This meant that I theoretically had years before I should worry about needing a successor.<br>Why then did I decide that my first hire needed to be my successor? That's a large part of what this article is about.<br>I thankfully did hire my successor as one of my first hires. I was upfront with him, explaining my goals, plans, and timeline. Around three years later (exactly on schedule), I was promoted to Director. Shortly afterward I took a leave of absence, and my successor took over. Since then, my successor was promoted to Director as well. It all went according to plan. Which is remarkable.<br>Part of that success was luck, but it also took careful planning. And far too many people don't do this type of planning. Maybe you can be different.<br>What is succession planning?<br>Early in my career, I was asked about my succession plan. I named someone and thought I was done. "In the event I'm hit by a bus, Hector should take over."<br>The problem is that succession planning isn't about just pointing at someone. If Hector doesn't know how to do my job, he certainly can't take over. And if my manager doesn't trust Hector, that won't work either.<br>Naming someone is a final task of succession planning. The succession planning process is about the complex task of getting someone ready to take over your role (or a portion of your role). If I were a more experienced person at the time, a proper response from me could have been:<br>"As a result of years of work, Hector is ready to take over my job when i'm needed elsewhere, or if something happens to me. He already knows all our major partners and team members, and they know and trust him. He's done all aspects of my job at least a few times."<br>Let's walk through the major aspects of succession planning and break them down. Because that's what I feel like doing.<br>Your successor knows everyone you rely on to do your job well.<br>Let's say you have to occasionally post marketing images on the Amazon retail site. Your successor needs to know who you rely on to get those images created. Or maybe you need a last-minute code change pushed to production. Your successor needs to know the person who has to sign off on the change.<br>If you get hired into a new role, one of the hard issues to solve is "Who do I need to talk to about this?" - Your successor requires those answers.<br>Your successor is known and trusted by those who rely on you.<br>You frequently partner with a peer engineering manager on tasks. They need to know and trust your successor.<br>All the design reviews and engineering promotions require your organization's principal engineer. They need to know and trust your successor.<br>The requirements of your product are written by your product manager. They certainly need to know and trust your successor.<br>The point is that you've built a working relationship with a long list of people. If you want someone to take over some or all of your job, you'll need to make sure that these people also know your successor.<br>Building trust from scratch is difficult...