Skip to main content

Do You Need Clearer Project Actions?

Something that I have observed (consciously at least) over the past few months is the correlation between clear project actions (such as on meeting minutes) and the rate of actions being closed out.

How many times have you read the notes from a meeting and wondered what on Earth the tasks really are? I'd bet that a lot of people feel the same way.

The result, however, is that actions aren't being undertaken and progress doesn't get made in a timely manner.

We're already competing against time, other priorities and who knows what else in terms of day to day hassles. Having actions that are unclear on a circulated document do not aid their completion, and certainly helps the actions to find their way to the bottom of the pile (so to speak).

So, over the past few months, when I have witnessed this in action, I have challenged my clients to spend a few seconds more on each action and make sure that the request is clear. Not just the 'who' and 'when', but the description of the 'what' itself.

I've seen people who sent out the actions go back to the list (usually at the next meeting) and scratch their heads as to what they meant...

If you are guilty of this then please stop! Taking a few extra moments before you send out your list to ensure that the actions are crystal clear is well worth the investment. After all, a few extra minutes invested with defining / recording the actions may save you weeks in terms of getting results.

And yes, my clients instantly spotted the errors of their ways. Better action lists were produced from their meetings and more stuff started happening in-between their improvement meetings. It's simple, but it works.


Giles Johnston
...optimising MRP systems and re-engineering business processes

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…