« 5 Key Components of a Project That You Need to Get Right
The Project Management Office and Why You Need It »

Variance Analysis And Course Correction

December 14, 2011 | Author: PM Hut | Filed under: Performance Reporting, Project Management Best Practices

Variance Analysis And Course Correction
By Douglas E. Castle

If there is a difference between the results which you projected (or budgeted), and your actual results, you have a variance. Calculating the amount and composition (isolating each of its contributing components) of that variance is important — but the key to using it as an analytic tool for course correction is to understand how and why the disparity occurred. The most unproductive use of this data is to use it like a light switch, i.e., “This thing didn’t work, so let’s scrap it and start over with a different approach.” Used properly, you can use the “how” and the “why” to minimize trail and error, minimize time and resources lost, and not, in essence sell your car because it has run out of gasoline.

Incidentally, by “variance” I absolutely refer to deviation from the expected result, and not deviation from a statistical mean. This is not a statistics exercise in standard deviation or sampling. This is a briefing on how to use information obtained through simple arithmetic and observation in order to find out precisely what might have gone wrong, and what may be done to get on the proper path. The process involves reasoning as well as computing.

Some Considerations For Business Planners And Project Managers:

  1. Break the variance down. What was high? What was low? Did certain “winning” (better than budgeted) areas subsidize some “losing” (worse than budgeted) areas? This type of camouflaging often causes business to keep do unproductive things because their failings are ‘covered’ or ‘hidden’ by successes in other areas. Isolate before you generalize.

  2. Examine each of the components on a line-by-line basis. If the variance is negative, was it performance-related, circumstantial or was it a function of unrealistic planning? Similarly, if the variance was positive, was it performance-related (and how may me further leverage this ability, if so), circumstantial (i.e., we were - phew - awfully lucky), or were we too conservative in our planning. The results of these analyses become course correction (or map correction) tools.

  3. Compare month-to-month variance report results. The variances which are increasing should be given special attention and the fastest managerial intervention. These must be closely monitored and worked on as necessary. If they’re favorable, we want to water them and watch them grow. If they’re unfavorable, we want to treat them before they metastasize.

  4. Every variance analysis should be followed by an agenda of actionable items, and swift implementation.

Variance Analysis as a means of monitoring and adjusting either project planning or management is one of the most valuable tools in your arsenal for victory.

Douglas Castle is a senior level expert in all matters of high-level corporate negotiations, deal structure, and strategic planning. He speaks, consults and writes frequently about these subjects, as well as about key aspects of leadership and crisis management.

Mr. Castle has been, and continues to be a seasoned and acclaimed advisor, director and trustee to emerging enterprises and growing companies worldwide, across a broad variety of industries on matters of organizational development, strategic planning, financing (both institutional equity and debt), international incorporations and negotiating of co-ventures, mergers and acquisitions. Mr. Castle’s current passions are centered upon leveraging his wealth of experience in high-stakes corporate negotiations, deal structure, organizational engineering, strategic planning and financing to foster innovation and entrepreneurial growth and success. You can read more from Douglas on his professional blog and personal blog.

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

This entry was posted on Wednesday, December 14th, 2011 and is filed under Performance Reporting, Project Management Best Practices. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

No comments yet.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

The Stevens Enterprise Project Management Master's Program

Project Management Categories