Effectively driving change is a core skill for any leader, and that can set you apart from the rest. Each change is another step towards a better team. Just as your team iterates on the product, so should you iterate to drive growth. To do it easily, let’s go over the Change Algorithm.

The Algorithm

When I first formalized the process in The Tech Executive Operating System, it was because I had in mind how many leaders I’ve worked with found it easier to stick with things when they had a clear structure. Perhaps that’s how most of us are wired. I’m sharing it here in abbreviated form to help more people utilize it.

The thinking is that your change initiatives deserve the same seriousness that you give “real” projects. Tracking what you’re doing and how is not hard, but we often neglect applying these habits to leadership work. Following the algorithm, you’ll be able to execute better on initiatives, improve dramatically between each iteration, and rapidly build up momentum. Let’s get started. Below you can find the illustration of the algorithm from my book.

Define

The very first step is to describe what you’re trying to achieve and how you’ll know when you’ve done it. This step is about crystallizing what change you think is needed and why, along with your definition of done. Without it, it’s extremely easy to fall for changes that are like empty calories: you perform them mindlessly, never realizing whether they are even doing anything useful.

Bite-size

Equipped with your definition, the next thing we do is break it down, just like you’d do with a big feature. Often, leaders get excited about a change and try to go for it all at once. However, that’s a surefire way to bite off more than you can chew. Instead, find a reasonable first pass that will be meaningful but not too big and long.

This works just like it does for your regular iterations for product development. You make sure that the initiative isn’t so big that it becomes amorphous and then just fades away with time. You want to find a slice that’s “just right.”

Introduce

Effectively communicating the change and the work that will be performed to those affected is crucial. The reasoning we came up with earlier will come in handy to ensure alignment. Clarity about how it will be performed also means the time will be more likely to come up with suggestions or notice when things don’t make sense. Separating the introduction from the initiation, which is next, provides the team with time to ask questions, poke holes, and become real partners in the initiative as opposed to mere order takers.

Initiate

As with any initiative, it should be initiated properly. That means there’s a clear kickoff date, from which the change you’ve introduced in the previous step becomes reality. It signifies that we’re done adjusting the plan for the first bite-sized chunk and are off to the races.

Execute

At last! We can get rolling, right? Most engineering and product teams actually know how to execute things, however they tend to use those skills solely for product work, neglecting the same care and attention when it comes to internal changes and processes.

You will execute the change initiative like any other big project. You should continuously track it (e.g., mention it in the daily or have a regular sync), work with a deadline, and at the end celebrate the success and have a learning session (like a retrospective).

Summarize

You’re done! The first bite-sized piece is achieved. Now we want to ensure we have the proper closure. That means clearing your plate: if you’re pleased and the thing is done for now, say it. Ensure everyone is aware, cancel the recurring invites, document it, and move on. This is essential so everyone can sense the progress and realize that there’s no space to try something else.

Further, at the leadership level, I recommend holding an “improving improving” session where you consider the change initiative at the meta level and see if there are any lessons that can be incorporated into your future initiatives.

Rinse and Repeat

Assuming you haven’t reached perfection yet, now’s the time to find the next thing you want to work on and get to work. Just like product iterations. Happy improving!