Prioritisation - Key To Success

- "Should I buy those gloves?"
- "How much are they?"
- "$70"
- "Hmm, that’s too expensive"

A couple was in a tiny store in the centre of Sydney buying discounted uggs and other sheepskin apparel. $70 was a significant amount for them especially comparing to the prices of other goods in the store.

In about a week she decided to buy them though. They returned back to that shop, bought the gloves and she was very excited. The excitement continued with a shopping spree at Paddy’s Market in Chinatown market which is very famous for low prices. They bought some clothes, souvenirs and other things. All those other purchases however were not as precious to her as the gloves she was aiming to buy at the beginning and were the main goal of the second trip.

Back at home they started unpacking the stuff and realised they lost the gloves somewhere.

It doesn’t matter whether the price level or the value of all these movements back and forth just to purchase some clothes is really worth considering here. For many people it is very important however.

What could be learnt from this story is when priorities are being set it is necessary to follow the basic rules:

1. Stick to your highest priority items first and exercise maximum focus on them

2. Items with lesser priority should be:
a) delegated if they are important
b) placed in queue if they are unimportant
c) forgotten after review

3. On a regular basis review the priorities and evaluate them in accordance with bigger plan.

Happy prioritisation and management!

Comments

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi

Travels etc.

Search This Blog