However skilled or knowledgeable we are in our chosen profession, the one thing that can go a long way towards de-railing our efforts is poor time management. Yet I use the term 'time management' only as a convenience, because I don't really believe that it's possible to manage time. Time just is, and we all get 24 hours a day. The real problem lies, instead, in how we manage our work flow. Time management is really about managing a queue.
This is an important statement because it makes us immediately realise that what is true about the physical queues that we experience during everyday life is also true about our work.
Further, we can also see that the methods that go into properly managed queues might also work for us in managing our work flow. Saturday night at the bar in a busy pub is chaotic because there is no proper queue, just people trying to catch the attention of the bar staff. Conversely when, as in many main Post Offices today, there is a single queue and an adequate number of cashier positions, the queue moves much faster. Unfortunately, the chaotic queuing system operating on Saturday night at the bar is the one most resembling the way many people run their work days. Instead of imposing order on the flow of work, they are open to every random interruption - they tend to give priority to whatever is 'making the biggest noise' at the time.
Yet this is probably the least effective method of prioritising ever devised. Depending on the amount of noise that it is making, any incoming piece of work will either be dealt with immediately (thereby taking us away from what we were already working on) or will be put off until later. The problem is that 'later' is undefined. It could be any time from now to the end of the world. So not only do pieces of work arrive at random, whether and when they get dealt with is also random. What we can easily end up with is a situation in which our work is out of our control. We might just as well throw dice to decide what gets done.
The problem is compounded because, since our work comes in at random and gets processed at random, there is no obvious way to check whether the workload is in fact appropriate for the amount of time we have available. How can we tell if the queue is too long if we don't have a queue? Without the discipline that knowing the length of the queue brings to our workload, we have a strong tendency to take on further commitments (again more or less at random) in the vain hope that somehow we will find time to fit them in. We ignore the basic truth that, if we are already filling 24 hours a day, something has to give every time we take on an extra commitment.
In summary, the problem poor time managers face boils down to this:
If this is the problem, then the solution must be to learn to manage the queue properly and to cut back the workload to what is within the individual's capacity.
Seeing our workload as a queue makes us realise that the two most common ways of managing it - by priority and by urgency - are not going to work very well if the queue is too long for everyone to be served before the 'shop' shuts.
If 'important' people keep pushing to the front of a queue, when are lesser mortals going to get served? And if people keep being given preference because their business is 'urgent', when do those of us who aren't granted 'urgent' status get served? In both cases the answer is 'never' if the queue is too long.
This sort of prioritisation only makes sense if the queue is short enough for everyone to get served. But if everyone is going to get served anyway, surely most of the important and urgent cases could be left to wait their turn?
The aim of a good queuing system is for everyone to get served within reasonable time. A queue will fail if:
Poor time manager - the way poor time managers deal with email is usually like this:
Good time manager - a good time manager checks email at pre-arranged times, maybe one, two or three times a day and then deals with all the email that has arrived as a batch. This means that the good time manager does not interrupt his/her other work and does not build up a backlog of unprocessed emails.
The good time manager will also pay attention to weeding out sources of email that are not productive so that the volume is kept to a reasonable amount, and will be disciplined about not getting distracted by individual emails. Both of these are easier to do when dealing with email as a batch because one is much more conscious of exactly how much email remains to be processed.
Now the principle used here by the good time manager is applicable to many things other than email, eg paperwork, phone calls, minor tasks, etc. The principle is to:
Let's now look at another cause of poor work practices - meetings.
Poor time manager - whenever poor time managers are asked to attend a meeting, they:
Good time manager - by contrast, good time managers:
In this case too, the principles used by the good time manager are applicable to other situations. The good time manager is conscious of the length of the queue. He or she makes sure that the only things allowed into that queue are those that are relevant to their core commitments. They are also conscious of the 'opening hours' of the queue. They know that they must leave enough time in their schedule to process work they take on. And above all they do not take on distractions.
Realising that 'time management' is actually about managing a queue enables us to take far more realistic action to manage our work flow. By paying attention to the three areas in which a queue can go wrong, we can successfully get through our work. By imposing a queue in the first place, we can avoid the fractured and random nature of many working days.
'Do it tomorrow, and other secrets of time management' is published by Hodder (£7.99) ISBN 0 340 90912 9
Author: Mark Forster is an author and life coach specialising in personal
This article was published by the Finance and Management Faculty (Issue 141, February 2007).