Archive for January, 2007

Important Vs Urgent

I’m sure most of us were in situations where we had too many things to do and not enough time to do them.

Between work, family, friends, social activities and other obligations 24 hours a day is just not enough. So how to manage your tasks or to-do’s ? A lot is written on that subject (and probably in more depth) but here’s what i think (learned and read about) during my previous experiences:

Classify your tasks into  2 categories, Important and Urgent.

“Urgent” examples:

  • Pressing or burning imperatives that must be completed immediately.
  • Critical or vital tasks that someone else insists be performed without delay.
  • Unrelenting and persistent routine demands on your time.

An “Important” task would be:

  • An activity that makes a significant and lasting positive impact on others.
  • An unselfish act that will bring happiness or joy to others.
  • Actions and activities that promote balance in my life.

 In real life examples, usually Urgent always wins over Important but the key is to manage wisely the “urgent” but still focusing on the “important”.  A good technique would be to take few moments to truly analyse the priority and the impact of the next task in hand.

Try to minimise the “Urgent” things to do, plan ahead and achieve what’s Important.

Leave a Comment

Communication/Project failure!

Do i need to add anything else ?!

cell_011.jpg cell_02.jpg
1-How the Customer explained it 2-How the Project leader understood it
cell_03.jpg cell_04.jpg
3-How the Analyst designed it 4-How the Programmer wrote it
cell_06.jpg cell_07.jpg
5-How the consultant described it 6-How the project was documented
cell_08.jpg cell_09.jpg
7-What operations installed 8-How the customer was billed
cell_10.jpg cell_13.jpg
9-How it was supported 10-What the customer really needed

Comments (1)

Seligman’s research

As a young psychology student at Pennsylvania University in the sixties, Martin Seligman was troubled. He’d designed a ground-breaking experiment which involved giving dogs mild electric shocks that would be unpleasant but not harm them in any way. Should he go ahead and perform it? Would the potential benefits of the experiment outweigh the discomfort of the dogs? After talking it over with his advisor he went through with it and his findings shocked (no pun intended) the world of psychology.
Three dogs went through each experiment. The first dog was placed in a special cage and given electrical shocks through the floor, which stopped whenever the dog pressed a panel with its nose. It received shocks but had the power to stop them and quickly learned to do just that. The second dog got shocks whenever the first dog got them. This means that it received exactly the same amount and duration of electrical shocks as the first dog, but it had no chance to affect them. The third dog got no shocks.
Then each dog was placed in a so-called shuttlebox. Here the dog was given an electrical shock through the floor that it could easily escape by jumping over a low barrier into another part of the box. Dog number one (who’d received shocks it could turn off itself) quickly jumped over the barrier. So did dog number three that had gotten no shocks. But dog number two just lay there, feeling powerless to change its conditions. It had learned that electrical shocks were not something it could control. It had learned helplessness.

From Happy hour is 9 to 5

I can see similar behaviour in some work places, people sometimes just surrender and decide that the problem they have is something they cannot control or avoid.

The secret is in being Positive. i’m not suggesting to forget the problem or to pretend it doesn’t exist. Focus on the solution, be positive, it will make you happier and will definitely make you more productive.

Leave a Comment

Agile

During coffee last week, someone brought to my attention a methodologie called Agile (Yeah, maybe i should have heard about it earlier). So here’s my modest opinion:

thanks Wikipedia
Agile software development

a conceptual framework for undertaking software engineering projects.
Most agile methods attempt to minimize risk by developing software in short timeboxes, called iterations, which typically last one to four weeks. Each iteration is like a miniature software project of its own, and includes all of the tasks necessary to release the mini-increment of new functionality: planning, requirements analysis, design, coding, testing, and documentation. While an iteration may not add enough functionality to warrant releasing the product, an agile software project intends to be capable of releasing new software at the end of every iteration. At the end of each iteration, the team reevaluates project priorities.

in today’s IT market, many methodologies are found and many are being created and modified each day.
Each has a different combination of old ideas and new ones.

The Agile’s iteration concept isn’t totally new, Prince2 suggests the same concept and call them Stages.

What i found interesting was the little emphasis on written documentation while using Agile. It prefers face-to-face communication.
We all know how writing documentation (of any kind) is a nightmare but still is an important aspect of any project. It’s true it is time consuming and can get boring, but doing it through all the stages can make it easier.
Add to that, while working on big projects that can last for several months,a written document is always a good reference to what is required,who required it and why.

Ford once said: “a fool with a tool is still a fool” , so having a management software in your hand won’t make your project a success. It will just help you track the different phases and remind you of what might be needed and ease the paper work.

The key to success is You.

Leave a Comment

the Candidate and the Salt

A candidate applying for a big company went to his final job interview.

He was very confident he’ll get the job, the interview was going so well that they (the company’s recruiting people or if you prefer HR) decided to invite him for lunch and continue talking.

Once in the restaurant, the candidate ordered a steak and some wine. 

Everything was going fine until after lunch he was informed that the company will not hire him.

In shock,he asks why! at that point the CEO interfered and told him the following:

“when you got your steak,the first thing you did was adding salt to your food without even tasting it. Your steak may have not needed additional salt or maybe was too salty or maybe actually needed the salt you added. I expected you to taste your steak before adding the salt since it tells me a lot about your approach.”

bottom line is: Check your steak before adding the salt! 

Leave a Comment

Welcome to my Blog.

Hello Everyone..

Welcome to my Blog where we talk about Management.

I’ve always been a big big fan and in this blog ill try to look deeper into management skills,techniques and methodologies.

It will motivate me to read more and research more. Hopefully you will find it useful.

Feel free to drop me any comment or idea.

Happy blogging!

Comments (7)