Page 24 - Straight Talk On Project Management IV

How do you rate the effectiveness of the solution? Use a 1-10 scale or a descriptive “fully”,
“partially”, “not at all” scale?

Is the problem persisting? What are the chances of it happening again?

What alternative potential solutions did you consider? Are they worth documenting for future
reference?

Is there any residual potential impact elsewhere? Consider any ‘knock-on’ effects caused by your
solution to other areas of your project and portfolio, you may have reassigned resources, for
example.

And my favourite question … and this one often gets overlooked …

Has your root cause analysis created any deliverables?

It’s amazing how often new revenue streams or end user benefits are created when you address an
issue. Often project teams are so focussed on solving their problem that they are blind to potential
‘bonus extras’. Remember this; the microwave oven, superglue, Teflon were all invented whilst
trying to perfect something else, Play-Doh was created by a team working to develop a cleaning
product, even saccharin was invented when a scientist failed to wash his hands before eating and
noticed a sweet taste! Open your mind to bonus deliverables!

The benefits of being able to clearly identify the root cause of an IT Project problem and address it
are manifold:

You’ll figure out the BEST solution to a problem;

Experience sustainable measurable success (now and on future projects);

Better internal processes;

Increased efficiency;

Greater confidence in the quality of a solution;

Growth of your team's capabilities (future-proofing your team against challenges ahead);

Better quality deliverables;

Extra (bonus) deliverables;

Faster project delivery (fast identification and resolution beats head scratching and naval gazing);

Ownership of challenges and solutions builds team confidence;

Improved end-client and end-user satisfaction.

… The list goes on and on and on.