Skip to main content

When Smart People Are A Nuisance

We all like smart people, right?

The purpose of this article is to share a word of caution when undertaking new continuous improvement projects; sometimes the situation to be improved can be made artificially complex. Many smart people like complicated things. However, complicated problems and complicated solutions can make life unnecessarily difficult.

When a situation is difficult to manage and needs to be improved you can often find yourself looking for solutions that will take every last detail into account and provide a robust solution. What if you don’t need to undertake all of these details? What if they are symptoms of something else?

If you find yourself in this position then it might be a good time to undertake some root cause analysis, to find out what is real and what is a knock on effect from some other activity. Root cause analysis can be very simple to undertake and one of the most popular options is ‘5 Why’. This approach is widely used to dig past the symptoms of a problem with a carefully chosen ‘why?’ question. Don’t just use the question ‘why?’ on its own, this doesn’t provide the necessary guidance for the people asking the question (and can become quite irritating).

The purpose of digging under the skin of a problem is that there is usually some kind of ongoing issue that needs to be resolved. By probing further you often arrive at a really simple (and obvious) insight that is in your control to resolve. This flash of the blindingly obvious is, however, only obvious once you do the necessary digging. The point of root cause analysis is to prevent you from accepting the first solution and instead help you to find out what is really going on, and more importantly, what you can do to change the situation.

After you have this level of clarity you can then go about crafting an improvement project which will address the right problems, and give you the correct results. Solutions for our problems may need to be complicated. They could also be an excuse not to stop, stand back and look at what you are doing and look at the bigger picture. If you find yourself in this situation then I recommend considering the following:

  • Fully define the problem you are trying to solve. By defining a problem accurately you can often devise a simple solution in its own right. This step alone is often glazed over and never given the true amount of time it deserves. Spend more time on this step if your projects are too complex.
  • Undertake some root cause analysis if the defined problem does not give you a beautiful yet simple solution. Try ‘5 Why’ or similar techniques to help you get to the bottom of the problem.
  • Generate an improvement plan to address your real issues.
  • Review the improvement plan, challenging each step with the question ‘what would give me a better result for less effort and cost?’ Revise the plan to reduce the amount of resources and effort the plan currently requires. You may need to leave this step over a period of hours, or days, to get your mind to give you some really good answers.
  • Take action and review the results.

I hope that if your projects seem too complicated or difficult that you will try the above. I really like smart people, but I am also aware that many of them like to jump into a problem and develop novel, complicated, long winded solutions. Stepping back might seem like taking time that you don’t have available. In most cases where I have recommended this approach businesses have saved themselves a lot more time and effort than if they just pushed ahead with the original solution. Their solutions were better too, so please take a time out if you are feeling that your projects are too complicated and try this approach.


Giles Johnston
Author of 'Business Process Re-Engineering', a practical plan to improve business performance.

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…