Skip to main content

Can going slower help you to go faster (with process improvement)?

I had two really good examples of going slower to go faster* take place over the last few days.

Have you experienced that feeling when you are trying to get so much done that you get very little done at all?

We think that we're multi-tasking but instead we are really treading water and feeling overwhelmed.

Slowing down, by consciously choosing to do less (but sticking with fewer tasks in order to get them completed properly), can be a good strategy to take.

By going slower to get more things properly done can help you build capacity, avoid future mistakes and increase your overall business pace.

Of course don't take this post as an excuse just to go slower; I'm talking about being selective and nailing a few important actions rather than just giving the impression that you are making progress on a wider range of actions.

For example:

It was worth re-scheduling another improvement session to extend the current one to ensure that the decisions were made and the actions clearly understood. [There are now two more team members who can progress the project rather than the original one.]

It was worth deciding not to start a new action and continue with the hands on work regarding an internal audit process. [There are now two people who can conduct the process, not one, and the programme that was in arrears will now get back on track.]

What could you slow down with, in order to go faster in the long run?



Giles Johnston
Author of Business Process Re-Engineering

* That's why the name 'Smartspeed' was chosen!

Popular posts from this blog

Where there is a (performance) gap there is a concern

I had a really good day yesterday working with a client's team.

The team has issues. Plenty of issues. Some are managerial issues, some are people issues and some are production issues.

When I first met the team they didn't know what to do with their issues, so I started by helping them to see more issues.

Issues everywhere, they didn't seem very impressed.

And then we captured the issues as 'concerns' into the tried and tested 'concern cause countermeasure' format and followed the process:

Concerns probed for root causes and root causes converted into countermeasures.
Soon they realised that some of their root causes dealt with numerous concerns and they gained momentum.

Yesterday we pulled another one of their processes apart and identified all of the gaps. The gaps became concerns and we fed them back into the process. Now they have a practical action plan (of countermeasures) to upgrade the process in question.

What do you do with your performance gaps? …

Continuous Improvement and the Five Legged Race

Many improvement projects need the buy in of several people before they can progress. Amongst these people there will be some that have a firm view of what needs to happen and are keen to make progress. Some of the people won't be sure and they will need more time. Other people might not be that interested and have other priorities they want to focus on.

None of this is wrong.

It is an observation of mine and one that I see repeat on a regular basis with the businesses that I come into contact with.

But, if we take the principle from the observation we have an interesting improvement strategy (one that I personally use when I get stuck with my client's improvement projects).

You might have worked out the approach from the title of this blog post, but it is analogous to a three-legged race (or four, five, nine...). If someone in the group moves in the wrong direction and / or at the wrong speed then the whole group falls over.


In the example I gave at the start it is no differe…

Do you have time to prepare (in order to become super productive)?

I had a funny conversation a few weeks ago with a team that was complaining about one of their colleagues spending 'ages' preparing their workstation within their factory. I meet a lot of people that spend too long preparing (and effectively procrastinating) so I was intrigued by their comment. It turns out that this individual didn't spend too long but rather his colleagues dived into their work without thinking through what the best way to work was...

The slower to start gentleman did in fact prepare his work area. He was also able to produce a far greater amount of work in the same time period because he had invested in a smarter way of working than his counterparts. The time spent preparing his working area was valuable and not overdone.

This example reminds us of the importance of the second S in 5S (set in order) and how workstation design is critical if we want to maximise the productivity of our teams. Whether this is a physical work area in a factory, the filing s…