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

Stop firefighting, start performing!

Another weeks passes and another example of unnecessary fire fighting demonstrated by a business I have been to help. If you have this taking place in your business, let me ask you a few questions: 1. What keeps on happening? Regain control with this practical book Can you pin down what it is that you keep having to do, to get out of trouble? If you can't, is there a pattern you can observe? 2. Do you want it to stop? Is it causing you enough of a problem that you want it to stop? If the answer is yes, keep reading, if not park it for another day. 3. Find out what is going on Do you know why you are having this issue? If you aren't sure where the issue is arising from, then take a few minutes to have a look around. When you have some idea, go to the next step. 4. Cause and effect Do you know what is truly causing the fire fighting situation? If you spend the time to get to the root cause of the situation , you have a good chance of permanently eliminating this situation. Most p

Kaizen improvements need to be specific

Do you find that your Kaizen improvements don't always go to plan? If you do, then you're with the majority! Whilst there is great deal of 'trial and error' there is a simple approach that can help. Available from Amazon Being specific about critical parts of your improvement can uplift your results. So, how do you go about doing this? The most direct route is to be clear about which parts of your improvement are critical. From here you can explain, in detail, what you want for those items. This might take some practice as many of us have become lazy in this regard. We take it for granted that our team 'get us' and will know what they need to do. If you ever feel that something basic is missing from an improvement ask this question: "What does good look like?" The answer should put you back on track. About the author: Giles Johnston is a Chartered Engineer who specialises in helping businesses to grow and improve through better business processes and

Are your teams clear?

I have recently finished working with a team that were struggling. They were struggling to meet their production schedules. They were struggling to respond to customer enquiries on time. They were burnt out and frazzled. After some prodding and poking it became clear what their issues were. In particular, it became obvious that expectations of the team weren't clear or defined. Defining what you expect from teams is a standard management approach. The problem with most teams is that leadership describe the standards in vague terms . So, what happens if you get the standards crystal clear? You should expect to see the team produce the right outputs. They should produce the outputs at the right time. And, they should produce them in an agreed way. Be clear with your teams. Ask the question: What does good look like? If you want to get some more ideas on how to define effective standards and visions, get your copy of my book today . What does good look like? is a practical guide to h