Skip to main content

Most Improvements Don't Happen Instantaneously

Time is a funny thing.

As a society we often contemplate it, and some of us (including me!) have written on the topic of managing it as best we can.

So, why is it that there are so many improvement, delivery and project plans that seem to ignore the simple maths that lie behind the scheduling of activities?

I don't think that a week goes by that I don't experience a situation where someone has forgotten that it takes time to complete tasks.

This might seem like a daft post and that this can't surely be a real situation... I shake my head so often I could understand your point of view (if you do agree with that statement).

But, it does happen an awful lot in my experience and my guess is that this same experience probably exists somewhere in your business too. It might not be you, it might not be your team, but it might be lurking somewhere.

Whilst mulling this issue over, before I started writing this article, I thought of a number of instances where I spotted this phenomenon and I may have identified a place for you to start your investigations!

The place where time seems to get forgotten is in the tasks immediately after a behind schedule activity. Or, put another way, someone is struggling and they are hoping like hell that the following tasks can be done immediately and without their usual timings / delays:

  • Customers are promised delivery dates immediately after the late operation is completed, ignoring the other operations that follow.
  • Production teams are promised go live dates immediately following a late installation activity, ignoring all of the other task that need to happen.
  • Service users are promised queue jumps, when they complain, ignoring the fact that other service users are ahead of them.
I'm sure that there are plenty of other places in our businesses that host these kinds of 'zero time' promises, but this is a good place to start for many of us.

The knock on effect of making promises based on this spurious thinking are too great to list, but all involve letting others down (and the resulting chaos / fire-fighting that has to take place to resolve the situation).

Have a look in your own business and let me know if you come to the same conclusion.

Giles




About the author
Giles Johnston is a Chartered Engineer who specialises in helping businesses to grow and improve through better business processes.

Giles is also the author of Business Process Re-Engineering and creator of the 'Making It Happen' continuous improvement toolkit.

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…