What to be? Quick or Correct?

The problem with several managers is that, they want to take too much time to evaluate things, before acting. In this competitive environment we may not have such luxury.

One of the Cutomers I talked to has a different way of doing things. As he explained it, as a CEO, he would quickly decide on the 10 issues in front of him. He might actually be wrong in 3 issues. Can he afford it?

His answer was an emphatic yes. He explained that, as all his were quick, he had adequate time to correct those 3 mistakes, before they were out of hand. He claimed that the net time taken was less than that, required to execute the solutions AFTER a fool proof analysis for all 10. Therefore he actually saved time and money. In essence, he meant "Be quick than accurate".

The point was emphasized by Jack Foster in "How to get Ideas?", where he demonstrated that students delivered more ideas when they were given shorter time-lines. My CIO tells us, not to wait for a 100% of things to fall in place to start the projects. They will actually do, AFTER we put things in motion. We will resolve issues on the go.

I do know some "proper" managers, who wants to make sure that every things is done slowly, steadily and correctly. I pity them.

Comments

Popular posts from this blog

Continual Service Improvement 2 of 2: The Processes

Service Transition 1 of 2: What do you need to know?

ITIL v3 Phases