HOW TO EAT AN ELEPHANT |
We usually try to calculate how long a Safety-related task or project will, or should, take us in hours, days, weeks, months, or even years.
It is later that we come to the realisation that, although in an ideal world the forecast timeline may have been reasonable, in reality, it just was not achievable, for reasons which only become apparent as the project or task progresses.
There is only one advantage that can be gained from such a situation: If we knew in advance how much effort, time, worry and money it would ultimately require, we might never have attempted the task or project - regardless of how necessary or important.
|
Out of sheer optimism, or because we want to ‘look good’, or because of unrealistic deadlines, we estimate the shortest possible time-to-completion. But we are mostly setting ourselves up for failure by down-playing the delays that can, and usually are, introduced by the human element. Even when we do try and cater for
delays, we don't always make the correct provision for productivity lost due to public strikes, break downs, public holidays, illness, carelessness, lack of interest or participation, etc.
|
|

|
Is it realistic to assume that basics like systems, programmes, etc. are in place before you begin the meal ? Or do systems, programmes, etc. form part of the meal ?
Sort out your
priorities.
Decide:
Do you need to start by carving into the toughest hide of the elephant (the sole of the foot? or the hide on the back?).
Or, do you start with the part that is easiest or quickest to tackle ?
Learn to differentiate between what is important and what is urgent !
Be smart, work smart, and remember that SMART means specific, measurable, attainable, realistic, time-bound. |
|
In conclusion:
You eat an elephant by being systematic,
by taking the first bite,
and then the next,
and the next ...
one at a time.
Do what you have to do and do not procrastinate.
|