An Easy-to-Follow Guide to Stepping Down as a Leader!
This article was automatically translated from Japanese by AI. Read the original Japanese version →
Table of Contents
Once you take on a title with "leader," "lead," or "manager" in it, you'll be buried in coordination work and never get to write code again—I'd imagine quite a few people feel that way, right?
Even if it hasn't gone quite that far, many people probably feel weighed down by coordination overhead or the general workload of being a leader and want to do something about it.
In this post, I'd like to suggest a few practical ways—and underlying mindsets—for streamlining or sharing the workload as a leader.
There are six main points:
- Automate everything you can
- Make tasks simple enough to delegate
- Build good dashboards for your team
- Turn decisions into recurring meetings
- Train a successor
- Delegate interviewing too
Automate Everything You Can
Let computers do the boring work. Leadership tasks are no exception. In fact, because leadership involves processing a lot of information, there's plenty of room for automation.
Things like generating reports for upper management or handling approvals can often be automated at least partially, even if not end-to-end. Automating something also turns it into source code, which naturally documents and shares what's actually being done.
Make Tasks Simple Enough to Delegate
Even if you can't automate something completely, preparing decent runbooks can make it possible for others to handle it. Or partial automation might bring it down to a level anyone can do. Even if not literally everyone can do it, as long as 1 or 2 other people on the team can, you'll be able to ask them for help.
It also adds redundancy to the team, so have the courage to ask others to take things on.
Also, having the leader built into an approval flow is often just a formality of authority without much real point. If team members can make the same level of judgment, letting any member approve is fine too.
Build Good Dashboards for Your Team
Decision-making becomes dependent on a single person when people are looking at different information. Put differently, if other team members can see the same information in an organized way, you can reduce that dependency. Reflect on how you organize information when making decisions yourself.
People often think of dashboards as something only leaders look at, but you should build clear dashboards specifically for your team members. Clearly communicating where the team stands also helps boost motivation.
Turn Decisions into Recurring Meetings
Rather than having the leader make ad-hoc decisions and notify people piecemeal, hold a regular meeting. Doing it over chat is fine too.
Ideally, you can knock out action items, schedule tweaks, and owner assignments in about 10 minutes while looking at the good dashboard mentioned above. Whenever you're adjusting things, you probably need agreement from the members involved anyway, so having even a few minutes to get together is better. In my experience, handling things via "reach out whenever" ends up eating huge amounts of the leader's time because they're pulled into almost every topic.
Meetings tend to get treated as evil, but if you're deciding something important for the team, discussion and consensus are necessary. In a setup where the leader decides unilaterally and members just go along with it, you'll never be able to step down as leader.
Train a Successor
Even if you reduce the day-to-day chores of being a leader, a team still needs leadership. In particular, thinking about the team's vision is a role that's hard to replace. Still, that doesn't mean you have to do it alone—even if involving the whole team is tough, you can probably get 1 or 2 people to think about it with you.
Regardless of whether they end up formally taking over the leader role or not, if anyone shows even a little interest in leadership work, I recommend getting them involved early on.
Delegate Interviewing Too
First off, I kind of wonder "Is that even a leader's job?!"—though having engineers from the actual team involved in interviews is definitely important. Still, there's usually no reason it has to be someone with a leader title, so talk with HR and others to get team members involved.
People might say it's better to have someone with longer tenure or who knows more about the team, but having interviews rely on one specific person isn't healthy for the company either—it usually means interview questions and hiring criteria aren't written down anywhere.
That's all—I hope this helps any leaders out there who are struggling with their workload.