Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Driving project success across the enterprise final jlw

1,090 views

Published on

Project Management: 7 Keys to gaining cross-functional buy-in for a technology project.
This presentation is especially relevant to enterprise software implementations.

Published in: Business
  • Be the first to comment

Driving project success across the enterprise final jlw

  1. 1. Driving Project Success across the Enterprise 7 Keys to Cross-functional buy-in JL Watson Consulting Know Your Customers. Grow Your Business.
  2. 2. www.jlwatsonconsulting.com Why should you care? “No-one is certain of the real cost of failed software projects, but in the US alone it is estimated to be upwards of $75 billion a year in re-work costs and abandoned systems.“ Computer Weekly Magazine, December 31, 2007
  3. 3. www.jlwatsonconsulting.com Bigger than the GDP of 67% of the countries in the world. - The World Bank, 2009 How big a problem is $75 billion?
  4. 4. www.jlwatsonconsulting.com Top 5 Causes of Project Failure 1. Lack of Customer Involvement 2. Poor Requirements 3. Scope Creep 4. No Change Control System 5. Poor Testing My Management Guide September 1, 2010 by Eric Morkovich
  5. 5. www.jlwatsonconsulting.com The BIG Question: Who are the customers, and how do you get them involved?
  6. 6. The Silo Effect
  7. 7. Different departments work differently. Sales Marketing Support
  8. 8. Goal: Coordinate functions across departments. Sales Marketing Support Single Centralized System Remove silos; join and centralize functions, processes and information.
  9. 9. www.jlwatsonconsulting.com Our Challenge: Establish Cross-functional buy-in.
  10. 10. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship 3. Give ownership to the business (not IT). 4. Cross-functional representation in the requirements definition. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  11. 11. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship 3. Give ownership to the business (not IT). 4. Cross-functional representation in the requirements definition. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  12. 12. 1. Align the project with the Organization’s Strategy.
  13. 13. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship. 3. Give ownership to the business (not IT). 4. Cross-functional representation in the requirements definition. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  14. 14. www.jlwatsonconsulting.com 1. Get Executive Sponsorship.2. Executive Sponsorship.
  15. 15. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship. 3. Give ownership to the business (not IT). 4. Cross-functional representation in the requirements definition. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  16. 16. www.jlwatsonconsulting.com 3. Give ownership to business stakeholders. (not IT.) It’s a business project…
  17. 17. www.jlwatsonconsulting.com 3. Give ownership to business stakeholders. (not IT.) …not a technology project.
  18. 18. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship. 3. Give ownership to the business (not IT). 4. Define requirements across all functions. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  19. 19. www.jlwatsonconsulting.com 4. Define requirements across all functions. 3 Key Steps 1. Business Process Mapping 2. Business Process Validation 3. Business Process Revision
  20. 20. www.jlwatsonconsulting.com 1. Business Process Mapping Give Process Profile Worksheets to Process Owners. 4. Define requirements across all functions. 3 Key Steps
  21. 21. www.jlwatsonconsulting.com 4. Define requirements across all functions 1. Business Process Mapping
  22. 22. www.jlwatsonconsulting.com 4. Define requirements across all functions. 1. Business Process Mapping
  23. 23. www.jlwatsonconsulting.com 4. Define requirements across all functions. 3 Key Steps 1. Business Process Mapping 2. Business Process Validation 3. Business Process Revision
  24. 24. www.jlwatsonconsulting.com 4. Define requirements across all functions.  Business Process Validation Sales Marketing Service
  25. 25. www.jlwatsonconsulting.com 4. Define requirements across all functions. 3 Key Steps 1. Business Process Mapping 2. Business Process Validation 3. Business Process Revision
  26. 26. www.jlwatsonconsulting.com 4. Define requirements across all functions.  Business Process Revision 1. Streamline the processes. 2. Become customer-focused.
  27. 27. www.jlwatsonconsulting.com 4. Define requirements across all functions.  Business Process Revision 1. Streamline the processes.  Reduce delays  Eliminate waste  Simplify for speed
  28. 28. www.jlwatsonconsulting.com 4. Define requirements across all functions.  Business Process Revision  Design the process for the customer.  Reduce customer effort.  Maximize customer value. Be more customer-focused.
  29. 29. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship. 3. Give ownership to the business (not IT). 4. Define requirements across all functions. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  30. 30. www.jlwatsonconsulting.com 5. Involve the end-users. "If McDonalds were run like a software company, one out of every hundred Big Macs would give you food poisoning ... and the response would be "we're sorry, here's a coupon for two more..." -- The Software Conspiracy
  31. 31. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship. 3. Give ownership to the business (not IT). 4. Define requirements across all functions. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  32. 32. www.jlwatsonconsulting.com 6. Communicate the Functional Advantages. WIIFM (What’s in it for me?)
  33. 33. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship. 3. Give ownership to the business (not IT). 4. Define requirements across all functions. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  34. 34. www.jlwatsonconsulting.com 7. Post-live follow-through You’re not live until you have R.O.I.
  35. 35. www.jlwatsonconsulting.com 7. Post-live follow-through Reinforce the buy-in. Don’t skimp on the training budget. Form internal user groups. Assign “Super User” Roles in each department. Incentivize learning.
  36. 36. www.jlwatsonconsulting.com 7 Keys to Cross-functional buy-in 1. Align project with corporate strategy. 2. Get executive sponsorship 3. Give ownership to the business (not IT). 4. Define requirements across all functions. 5. Involve the end-users. 6. Identify and Communicate Functional Advantages 7. Post-live follow-through
  37. 37. www.jlwatsonconsulting.com Questions? Comments? Feedback? Contact Jim Watson at: jlwatson@jlwatsonconsulting.com 207.741.9047 www.jlwatsonconsulting.com Thank you.

×