The document discusses organizational readiness and its importance for project success. It identifies the top three factors for why projects fail as resistance by employees, inadequate executive sponsorship, and unrealistic expectations. It advocates using organizational readiness to address these failure factors by gaining consensus on problems, understanding their impacts, and defining rewards from solutions. The document provides steps for assessing organizational readiness, including analyzing current issues, determining financial impacts, gaining employee consensus, and defining goals and communication plans to guide projects to success.

1. Organizational Readiness “Project Success Planning” Part 1 February 2011

3. Inadequate Executive Sponsorship

4. Unrealistic ExpectationsUse Organizational Readiness to combat these failure factors and guarantee the success of your next project!

6. Organizations lack consensus on the actual cause and impact of the problem

8. Most project initiatives become about “What” needs to be fixed :

9. Better reporting

10. Better tools

11. New System

13. What workflows are contributing to our problem?

14. Have our employees been trained in a detrimental way?

15. Do our systems detract from our workflow and staff?

16. Does our systems or process enable our desired outcomes?

17. Impact – Understanding the current impact will enable the project team to ensure they address the proper “What”

18. How much money is the problem causing?

19. Does the problem prevent us from doing our jobs?

20. Are our goals being hindered by the problem?

21. Reward – What business benefits will be gained by solving the problem

22. Will we increase revenue or decrease costs?

23. Does the solution make our employees more efficient?

25. Focusing on features and functions does not equate to project success

26. Time and budget expectations are often misaligned with the ability of the project to reach its goals* The Standish Group 2009 Chaos Report Statistics on Project Success

27. Top Reason for Project Failure Source: Deloitte CIO Survey – Top reasons CIOs give for IT Project Failure

29. Resistance by Employees

30. Inadequate Sponsorship

31. Unrealistic Expectations

32. No Organizational Change Plan

34. Change Valence – “Do the participants value the impending change?”

35. Change Efficacy – “Do the participants feel they can complete the necessary tasks of change?”

36. Outcomes of the Change – “How will the change affect me?”

38. Executives can allocate the resources to make change possible

40. Address Business Issues not a Feature & Function Checklist

41. Measuring Adoption is a must

42. Set Project Team Roles and Responsibilities

43. Define Project Owners

45. Determine the financial impact the Critical Business Issues are having on business goals and objectives

46. Consensus with the employees on the need for change

47. Communication plan on the need for change and the change management process

49. Organizations will know the rewards they will gain upon completion of the project

50. “Skin in the Game!” – Engaging employees in the Organizational Readiness process will make them part of the solution

51. Organizations will have a Roadmap to guide them to project success

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

54. Leveraging consensus & collaboration in helping firms determine their Organizational Readiness

55. Organization Readiness Process that leads to 100% Success Rate