Skip to content
Home » Blog » The Multi-speed Operating Model. Is it right for you?

The Multi-speed Operating Model. Is it right for you?

The Thinking Cube - The Multi-speed Operating Model. Is it right for you?

In today’s disruptive market agility is the key to success. The big question though is how to achieve it in an organization that may not be ready for it. When you can’t go all-in on the Agile operating model, the answer may be a hybrid multi-speed model that includes multiple delivery methods including Agile and Waterfall. The multi-speed model has some risks, but the rewards are great.

What is multi-speed?

Not every team in your business can work at the same speed. That being the case, multi-speed sets a target state for your delivery options. Multi-speed chooses the right model for each team and reduces dependencies between them to avoid bottlenecks.

Should you use Waterfall?

While Agile methods are the goal of many businesses, it is difficult to attain all at once. The Waterfall method could be more suited. This criterion should be considered to make an assessment:

  1. Needed change is small.
  2. There are too many dependencies on other systems to allow for frequent releases.
  3. Existing culture and associated constraints are difficult to overcome in a short timeframe.
  4. The level of change of both technology and scope of a project can be contained.

Waterfall is best used when there is a clear best practice, a short pipeline for change, and the delivery lifecycle cannot be changed.

Multi-speed enables, not transitions to Agility

Multi-speed requires CTOs to change direction to enable teams to deliver change dynamically and responsively to other business teams. This operating model grows from the need to adopt some Agile methods but not the whole methodology.

How to design your Multi-speed operating model

The Multi-speed model can be difficult to implement and is not risk free. Here are some guidelines to help create the model:

  1. Create independence in well-defined teams.
  2. Avoid changing resources and team structures with a single delivery method.
  3. Delivery methodologies must be clearly defined.
  4. Use project management software to unite efforts at the company level.
  5. Prioritize initiatives on a single list.

Final thoughts

It is important to keep some things in mind as you plan out your multi-speed method.

  • Create leaders. Identify those who are excited and will to be the first movers. Their success will reassure others in the team.
  • Create Allies. It is important that both upper and middle management are behind you efforts and that they understand that agility is the eventual goal.
  • Patience is a virtue. This is not a short term process, you may not see the rewards for up to two years.
  • Clear the path to success. Clearly defined processes and delivery methods are essential. Ensure conditions for success and define which teams would benefit from certain methodologies.

Let’s get started…