Skip to main content

How Do You Capture Your Actions?

One thing that happens when you get involved with continuous improvement is that you find other, related, actions start to appear. They might be things that you can't do immediately (for time constraints let's say) but that you do want to do.

How do you capture all of these actions that spring up?

On a wider note, how do you capture all of the actions that come forth from you business that you have been asked to do, or need to do?

The ability to 'capture' the actions / tasks that float around your business is a critical activity in my opinion. Just being consistent with logging the actions is a part of being effective with dealing with both improvement and general management, day to day.

The corresponding activity of 'execution' of these lists of actions is obviously the other essential ingredient, otherwise they are just lists for lists sake.

We could end up in a whole debate about time management, but thankfully blog posts are generally short!

So, the question I want to pose to you is this:

Do you have a simple and accessible method to capture all of the stuff that is floating around you (so that you can deal with it later on)?

I see minutes from meetings with actions listed on them, that don't get acknowledged until the next meeting (with a response of 'oh, er, I haven't done that yet') by people who don't even recognise the action.

I hear conversations about good ideas that get nods of agreement, but the ideas don't get captured and nothing changes.

And, I see lots and lots of loose ends. Actions started and never (consciously) closed out.

Don't be the same as this; find a method to capture the ideas and actions, related to you, floating around your business and then systematically flush these lists. If you are looking to become more effective in both terms of management and improvement then this approach won't let you down.

Giles Johnston
Author of Business Process Re-Engineering

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…