 | 
Articles To help Project Leaders |  |
|
|
 | |  |
|
|
Putting gas in this morning, I read the sign at the pump. The sign says "Brand X helps to clean your intake valves". This is good news, because just last night I woke up at 11:47 PM in a cold sweat, wondering if my Honda's intake valves are clean. Will you be able to sleep tonight with a clear conscience?
In fact, I wonder how many drivers and car owners who don't have a mechanical training like myself, have opinions on any of the following topics:
1. What is an intake valve, and why should I care?
2. What about the exhaust valves. Do I nee to purchase brand Y of gas to help clean the exhaust valves? Should I do 1/2 Brand X for the intake valves and 1/2 a tank of brandy Y for the exhaust valves?
3. What about other components for internal combustion engines? Does brand X clean the intake manifold, fuel injectors, exhaust system as well, or do I need brand Z to cover all of these components?
4. How have I been able to live all these years without knowing the cleanliness of my intake valves? Will I need to see a psychologist to help me work through my oversight and regret?
The list goes on and on.
The bottom line is: Who cares how clean or dirty the intake valves are? As long as my Honda gets me where I want to be, I can live with clean or dirty intake valves.
However, the lesson for your IT projects is clear - focus on the important goals. Don't get caught up in irrelevant debates and don't create nonsensical status reports or dashboards. I don't care if you have 127 test scripts to run. Put it in perspective of my project success. Will be on target, or not, and what do you need from me to help you address any issues?
|
|
|
