When you step into a new leadership role in an existing org there are two situations you’ll most likely encounter:

  1. The org is wildly successful. The previous leader has likely been promoted or is now pursuing a new opportunity elsewhere;
  2. The org is in serious trouble. The previous leader is mostly irrelevant because their decisions have led to this situation, and now it’s time to hit the reset button.

You’re less likely to encounter situation [1], but if you did - congratulations! You are in a terrific position to observe and learn about the org, and then double down on what works best and rework what’s barely working. You are in a unique position to build on your predecessor’s success and compound it with your own.

You’re more likely to encounter situation [2] because that’s how the world works. You can’t control the multitude of external factors that weigh in on your success as a leader (and this increases as you move up the ladder), and sometimes you will lose. That’s likely what happened to your predecessor: either the people above them decided to start fresh with someone else, or they realized there was little chance of success within a reasonable time and effort, and moved on.

Of course there’s the option to move into an org that’s in-between (just doing OK), but that’s only a temporary state. External factors and changes in the business landscape mandate that the organization will adapt, otherwise it will fall into [2].

Having said all that, stepping into a new role in a new org that’s being built is a different challenge altogether that requires another set of priorities and offers a different risk-reward balance, which I will not touch upon in this post.

As a director this challenge is far more visceral because of the size of the org and the scope of responsibility you are granted. You might have not encountered such a challenge before, so isn’t it better to prepare ahead of time? 🙂

So now that I’ve established what you’re likely to face, let’s talk about how you can turn the ship around. I see 3 sets of actions that can help create a new reality, in which the org is on the road to success, the people all around you have faith in your leadership and you’re able to stay sane. Not all of them will be relevant in every case, but any one of them can be fundamental to turning the org around.

Eliminate one bottleneck

When you step into your new role one of the first things that you need to do is sit down with your people and identify what bottlenecks that org is facing today. Are you not receiving budget that is in proportion to the required spend to sustain the business? Are there too many open seats and the minimal set of maintenance is spread over too few people? Is the system flaky and requires too much maintenance, or is very hard to safely improve iteratively? And the list of bottlenecks goes on and on.

As a seasoned leader you need to decide which bottlenecks are worth pursuing. Some bottlenecks can be resolved by a simple reframing of priorities.

For the bottlenecks that are left, write down the internal and external constraints, and what an action plan would look like to resolve it, disregarding the lack of resources you might face. Then you have a discussion with your leadership team on which of these to tackle first. Pick just one bottleneck, that’s enough.

You might pick the one that requires the least amount of effort in order to show a quick win and inspire your people. You might pick the one that requires the most amount of effort because that is what truly will help the business. You might not pick a certain bottleneck because you don’t have the people you need for that today, and need to fish them from somewhere. It all depends on the context, so there’s no single recommendation that would make sense in each situation.

Just clear one bottleneck with your people and celebrate that. There’s no more time for horsing around, you mean business, and they should be and feel competent.

Build a roadmap

Boy, are these boring to write and present. But you can’t afford not to do them. As opposed to the previous item on solving a bottleneck, drafting a roadmap takes longer because you will have to collect a lot of information, some of it might not be readily available, and work through it.

A roadmap is basically a list of work items that are prioritized by time, meaning the first item is the one you will do after you kick off the roadmap, the second item will be done afterwards, and so on. The first one has to be well researched and debated so it would have clear definitions, requirements and business value. The following few items can be less airtight, and those at the bottom of the list can be mere titles. If you have the people for it you can even tackle two or three items concurrently, but I would recommend not more than that because it would rob your focus.

What are the benefits of roadmaps?

  1. No one has to keep anything in their head, least of all you as the org leader. There is some kind of artifact (document, presentation, whatever) that everyone can refer to at their own leisure and see what’s happening now and what’s coming next.
  2. Articulation of the sequence of steps that would bring success. Individual items are no longer worked on in isolation or lacking context about what earlier work they build on, and what future success can be attained by the work we’re doing right now. This has another positive side effect of being able to celebrate the work already done and literally show how it helps us today.
  3. Keeps your people in focus and prevents waste. People are creative and bring all sorts of initiatives to the table. A roadmap lets them know where initiative is needed, and roughly when it is needed. In addition, a roadmap is a tool that helps weigh the business value of initiatives - if the value isn’t in the roadmap, then why put in the effort? Granted, initiatives are not a bad thing and they can shape the roadmap.

Having covered the benefits, it’s only fair to discuss drawbacks so we could have a full picture.

  1. Some people just don’t like working within a framework and prefer a very loose state of affairs. A bit of looseness leaves room for creativity, but an org can’t run on it, so you’ll need to bring these people along.
  2. Some employees or colleagues might not agree with the roadmap and constantly argue against it. This ties back to the discussion from the post on Engagement where you will have to balance (if possible) motivation by authority with motivation by will. At the end of the day, you are the boss: you call the shots, and you own the consequences if things go wrong.
  3. You or anyone else might fall in love with it. Any plan is subject to change, and sometimes roadmaps change as the business context evolves. Change it too rarely and it goes stale; too often and people stop trusting it. A regular review cadence, say quarterly, helps strike that balance.

Automate selectively

In a struggling org, manual toil quietly eats the capacity you need to recover. An org runs a myriad of processes at various frequencies. When some process is new, complex or requires a lot of manual effort there is an urge to automate it. I recommend that instead of jumping head first into the automation pool, ask yourself these questions so you could better judge the value of a proposed automation:

  1. What’s the frequency of the process itself? Is it multiple times a day, once a week, once a quarter or even slower? The lower the frequency, the less implied value exists in an automation.
  2. What’s the expected maintenance effort to keep the automation relevant? The more maintenance required, the less net value there’s in the automation as the people maintaining it aren’t free to engage in other valuable tasks. Counterintuitively, rarely-run automations are often the costliest to maintain: by the time they run again, the system has changed a lot, so you’re fixing several breakages at once instead of one at a time.
  3. Who is involved in the manual process? If it’s one specific person that is very hard to replace, then the automation will reduce the future risk to the org should that person no longer be in their role, for whatever reason. If several people can perform the manual process, this risk is greatly reduced.
  4. What’s the risk of getting the manual process wrong? If a mistake has little impact or can easily be undone, then an automation has less merit.

So to tie everything up, when you step into a new leadership role, and are faced with big challenges, doing any of the 3 sets of actions above will reduce the pressure on the org and yourself, and free up some time so you all could think about how to move forward. Do this over and over and you’ll compound your gains, which is the subject of the next post!