Skip to main content

Slaying The Headless Chickens

When will running around, trying to go faster than the day before through sheer physical exertion, stop being the strategy of choice for many businesses? You know the common phrase 'running around like a headless chicken', don't you? We joke about it, but it can waste a huge chunk of time from our working weeks.

When I first start working with a business this is often the approach that we are trying to overcome.



You probably know the kind of thing I am referring to, something happens that causes a problem in the business, something that we have to stop and deal with. Instead of taking the time out to get some facts and decide on an effective course of action, we make a swift decision and push on with the rest of the working day.

The swift decision sometimes don't properly address the problem and we then find that this problem resurfaces days, weeks,  or months later. Instead of us spending a little bit more time upfront we end up paying for this issue several times over.

So, is it better to spend two hours properly solving a problem, or is it better to make a quick decision and then repeat the same decision making / aftermath on an ongoing basis?

I know what my answer is, but so many people seem to take the 'chronic' option. Sure, there are times when you haven't got the two hours to spare, but you can still pencil a slot in your diary for later that week to take a proper look.

Too many people say that they haven't got the time to do the important things in business. Interestingly,  these same people do have time to fire-fight... when the quick fix comes back to haunt them.

Are you ready (and prepared) to slay some headless chickens?



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

P.S. If the above applies to you, then check out my book 'Business Process Re-engineering', available on Kindle, iBooks, or as a PDF download.

Click above to read a sample of the book.

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