Skip to main content

What is your business' performance focus?

When you undertake continuous improvement activities it is easy to have a broad brush approach.

"We'll improve everything!"

Everything can take a lot of time, and doesn't mean that you'll get the best results as quickly as possible.

Having a narrow focus can help you to prioritise your efforts and ensure that you make tangible progress.

Having a 'performance focus' is a good way to do this. Consider the different performance approaches that you could consider, pick one and then keep focusing on that aspect of your business until you feel ready to move towards another focus.

These different foci could include:

  • Delivering on time.
  • Increasing responsiveness to customer demands.
  • Shorter lead times.
  • Increased profitability.
  • Reduced debtors.
  • Higher levels of new product introductions.
  • Customer satisfaction.
  • Better inventory control.
I'm sure that you could think of a few, right now, that would be meaningful for your business.

It's a pretty simple formula to adopt:
  1. List out the potential performance foci.
  2. Pick one and 'hammer it' from an improvement perspective.
  3. Stop at an agreed point in time and reflect on the progress made.
  4. Decide if you want to stick with your focus, or change.
  5. Go to step 2, and repeat.
This approach can take a lot of hassle out of managing a continuous improvement programme within your business.

Give it a go and see how it works out for you,


Giles

P.S. If you are looking for simple strategies to help you make improvements take place in your business more regularly and with greater impact, then check out my Making It Happen course - click here.




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 strategies course.

Popular posts from this blog

Want more time for your projects? Try the 'Hour of Pain'!

Do you find your day being broken up by interruptions, stopping you from getting on with your work?

Continuous improvement projects often fall foul of this. The day can become so inefficient through the constant stopping and starting that we only just seem to have enough time to get the 'day job' completed.

I was in a meeting last week where this same issue cropped up. It also cropped up today. It's nothing new, but it is still a pain in the rear!

So, let me share with you an approach that has worked for my clients - the 'Hour of Pain!'.

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…

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? …