Organizational Readiness<br />“Project Success Planning” Part 1 <br />February 2011<br />
Organization Readiness = Project Success<br />The 3 biggest factors why technology projects fail:<br /><ul><li>Resistance ...
Inadequate Executive Sponsorship
Unrealistic Expectations</li></ul>Use Organizational Readiness to combat these failure factors and guarantee the success o...
Houston we have a problem!<br /><ul><li>Most problems are known throughout an organization
Organizations lack consensus on the actual cause and impact of the problem
Most problems don’t get addressed until some event triggers an emotional reaction</li></li></ul><li>We need a Project!<br ...
Most project initiatives become about “What” needs to be fixed :
Better reporting
Better tools
New System
Projects need to look at the “How” & “Why” to achieve the desired outcomes</li></li></ul><li>Issue - Impact - Reward<br />...
What workflows are contributing to our problem?
Have our employees been trained in a detrimental way?
Upcoming SlideShare
Loading in …5
×

Organizational Readiness - Project Success Planning

2,429 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,429
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Organizational Readiness - Project Success Planning

  1. 1. Organizational Readiness<br />“Project Success Planning” Part 1 <br />February 2011<br />
  2. 2. Organization Readiness = Project Success<br />The 3 biggest factors why technology projects fail:<br /><ul><li>Resistance by Employees
  3. 3. Inadequate Executive Sponsorship
  4. 4. Unrealistic Expectations</li></ul>Use Organizational Readiness to combat these failure factors and guarantee the success of your next project! <br />
  5. 5. Houston we have a problem!<br /><ul><li>Most problems are known throughout an organization
  6. 6. Organizations lack consensus on the actual cause and impact of the problem
  7. 7. Most problems don’t get addressed until some event triggers an emotional reaction</li></li></ul><li>We need a Project!<br /><ul><li>Select group or individual is tasked with creating a project to fix the problem
  8. 8. Most project initiatives become about “What” needs to be fixed :
  9. 9. Better reporting
  10. 10. Better tools
  11. 11. New System
  12. 12. Projects need to look at the “How” & “Why” to achieve the desired outcomes</li></li></ul><li>Issue - Impact - Reward<br /><ul><li>Issue – Most problems result from multiple factors
  13. 13. What workflows are contributing to our problem?
  14. 14. Have our employees been trained in a detrimental way?
  15. 15. Do our systems detract from our workflow and staff?
  16. 16. Does our systems or process enable our desired outcomes?
  17. 17. Impact – Understanding the current impact will enable the project team to ensure they address the proper “What”
  18. 18. How much money is the problem causing?
  19. 19. Does the problem prevent us from doing our jobs?
  20. 20. Are our goals being hindered by the problem?
  21. 21. Reward – What business benefits will be gained by solving the problem
  22. 22. Will we increase revenue or decrease costs?
  23. 23. Does the solution make our employees more efficient?
  24. 24. Will we reach our goals?</li></li></ul><li>Project Success<br /><ul><li>Only 32% of projects are successful; on time, on budget and meet the required features and functions*
  25. 25. Focusing on features and functions does not equate to project success
  26. 26. Time and budget expectations are often misaligned with the ability of the project to reach its goals</li></ul>* The Standish Group 2009 Chaos Report Statistics on Project Success<br />
  27. 27. Top Reason for Project Failure<br />Source: Deloitte CIO Survey – Top reasons CIOs give for IT Project Failure<br />
  28. 28. Start Your Project Off Right<br /><ul><li>Use Organizational Readiness to solve your failure factors:
  29. 29. Resistance by Employees
  30. 30. Inadequate Sponsorship
  31. 31. Unrealistic Expectations
  32. 32. No Organizational Change Plan
  33. 33. Acknowledgement and an action plan to address each factor will enable your organization to truly understand the cost of change</li></li></ul><li>Resistance by Employees<br /><ul><li>Project implementations are a ‘team sport’, requiring full support of the team
  34. 34. Change Valence – “Do the participants value the impending change?”
  35. 35. Change Efficacy – “Do the participants feel they can complete the necessary tasks of change?”
  36. 36. Outcomes of the Change – “How will the change affect me?”
  37. 37. Engaging users is critical to adoption success</li></li></ul><li>Inadequate Sponsorship<br /><ul><li>Many will except change if a thought leader supports it
  38. 38. Executives can allocate the resources to make change possible
  39. 39. Lack of understanding of the impact on current problems can be detrimental to the organization or group reaching their goals</li></li></ul><li>Managing Expectation<br /><ul><li>Measurable Goals = Project Success
  40. 40. Address Business Issues not a Feature & Function Checklist
  41. 41. Measuring Adoption is a must
  42. 42. Set Project Team Roles and Responsibilities
  43. 43. Define Project Owners
  44. 44. Communicate to the organization its role in the project</li></li></ul><li>Organizational Readiness Game Plan<br /><ul><li>Analysis of the impact of the current Critical Business Issues
  45. 45. Determine the financial impact the Critical Business Issues are having on business goals and objectives
  46. 46. Consensus with the employees on the need for change
  47. 47. Communication plan on the need for change and the change management process
  48. 48. Define the goals for making change</li></li></ul><li>Rewards of Organizational Readiness<br />By implementing an Organizational Readiness Process the following goals will be realized:<br /><ul><li>It will be known (before the project starts) if the problem (issue, need, or want) is worthy of a project
  49. 49. Organizations will know the rewards they will gain upon completion of the project
  50. 50. “Skin in the Game!” – Engaging employees in the Organizational Readiness process will make them part of the solution
  51. 51. Organizations will have a Roadmap to guide them to project success
  52. 52. Knowing the current cost of a problem and the rewards for solving the problem organizations can determine a budget that will allow for a successful project
  53. 53. Organizations will understand the resources need for a successful project and they can determine the impact on other initiatives and the business environment </li></li></ul><li>Project Success Planning <br /><ul><li>“PSP” – Achieving our clients business goals by applying an industry-proven method for efficiently managing each phase of a software project
  54. 54. Leveraging consensus & collaboration in helping firms determine their Organizational Readiness
  55. 55. Organization Readiness Process that leads to 100% Success Rate</li>

×