Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to 7 Steps for Sustainable Adoption (SharePoint- and Project Server-based PMIS)
Similar to 7 Steps for Sustainable Adoption (SharePoint- and Project Server-based PMIS) (20)
Recently uploaded
Recently uploaded (13)
7 Steps for Sustainable Adoption (SharePoint- and Project Server-based PMIS)
- 1. 7 steps to Sustainable Adoption SP & PS based (PMIS) Mike Taylor, PMP Founder and CEO
- 2. 2 Why won’t this one fit?
- 5. We all know: Most Projects Fail 5 ~75% don’t meet key objectives first time It’s bad for everyone Really bad if the project is implementing a PMIS!
- 6. Timeless Issues 6 Ill defined and/or incomplete requirements System breakage and/or bad user experience Lack of user buy-in/adoption Training? Support? VALUE?
- 7. 7 SharePoint a modern Business Platform
- 8. SharePoint Complexities 8 The platforms have embedded capabilities that evolved over years Most don’t understand vast array of capabilities & how to best utilize Organizations have their unique and often somewhat ad hoc processes Pre-conceived notions applied Over customization in many SharePoint implementations raising complexity & cost and lowering sustainability
- 9. Traditional Approaches not Working 9
- 10. I’ve seen the enemy and it’s me… 10
- 11. Adoption 1st, Value will follow
- 12. Sustainability Top Priority 12 If these solutions are used – they WILL deliver value. It’s self- evident. In most cases, it is a waste of valuable resources (time and money) trying to fully justify solutions up front.
- 14. Identify Needs Implement Grow Prioritize Iterative approach – it’s truly a Journey!
- 15. 7 Steps to Sustainable Adoption
- 16. 1. Rapid Results Get something that works – fast! • Address a limited set of pain points. • Prioritized by what can be ADOPTED, not necessarily top value or relative pain to the enterprise.
- 17. 2. Use it – As is Adjustment period • No customizations or changes • Fosters understanding of how platform works • Avoids ‘chasing your tail’ requirements that waste time & money
- 18. 3. Improve Usability Tweak through minor iterations • Processes • Reporting • Adoption support – i.e. learnings, videos, etc.
- 19. 4. Onboard Open up access to system • New users in initial groups • New groups, departments, etc. .
- 20. 20 Making Things Simple Is Not Simple
- 21. 5. Enable Advanced Capabilities Layer in advanced features addressing • More dimensions of project management & collaboration • Specific business pain points
- 22. 6. Integrate & Automate Better accuracy & robust capabilities • Data integration with out LOB systems • Custom automation of advanced processes
- 23. It’s All About Business Value 23 Expedite Innovation Facilitate EngagementFinancial Gains $
- 24. 7. Surface Successes & Value Realization Gain ongoing support and investment • Begin with informal reporting of successes • Create formal reporting structures for surfacing value realization • Use business value metrics such as ROI,CSI, etc. wherever possible
- 26. Project Challenges • Core PM practices and processes are incomplete and/or undefined • While pockets of expertise exists, organizational project management maturity is low • Speed, agility, and scalability are critical
- 27. Solution Approach: Project Management on Your Terms™ • Rapid integration • Phased approach balancing technology, process maturity, and personnel • Application Maintenance & Organizational Adoption (AMOA)
- 29. Program Status
- 30. Program Detail
- 31. Project Status
- 32. Recap Laser Focus on Adoption 7 steps: 1. Rapid Results 2. Us It – as is! 3. Improve Usability 4. Onboard 5. Enable Advanced Capabilities 6. Integrate & Automate 7. Surface Successes & Value Realization
Editor's Notes
- Tech heavy approach – throw it together Process heavy approach – analysis paralysis This graphic can show many things – I like the way it demonstrates balance of doing, analyzing, and iterative success….
- Been around for awhile… Developer, Network Engineer, Consultant, Project & Program Management. Worked with many of the worlds largest global companies & many very successful smaller niche companies Believe strongly that it is the job of technology to remove redundancy from our daily lives so we can focus on creative innovation and do great things. Interestingly enough, we’ve been in this transition for awhile. I was in NYC back in November and saw the co-founder of Yammer speak. He pointed out that studies show less and less of our work is repeated/operational tasks.
- We’ve all heard the stats about the high percentage of projects that fail Users grow weary of that next great thing – ‘here we go again’…. Management hard to get resources (people, time, money) – failed or troubled projects YOU & your career – want to get a promotion or at least that next great project – make your boss look great. Make them look bad, guess what happens…
- Software suites built to provide the foundation to address ongoing business challenges: Evolved with input & feedback from customers and solution providers.
- Tech focused – goal is to ‘GO LIVE’ and in operational support. No business level support…. Project churns over ill defined processes People don’t understand the platform and what it can do… These platforms have evolved over years and have great capabilities there for a reason…. Don’t GO TO CODE. In the end, without something in it for them, users lose interest and use less and less of the system…
- There’s a reason people invest in the software, services and everything else – MS Project is $1B business/year One government DOT looked at PMIS we implemented – noticed a CM charge that was 30% of spend to date … At Yammer event in November – interesting non-scripted discussion when someone asked the 5 panelist about getting investment for social. To a person they all said that the early justification/biz cases were a waste of time & money. Building small solutions, showing value, then growing was path to success for all…
- isn’t a new concept, but it is so often overlooked in favor of a ‘big bang’ approach. The highest priority (i.e. biggest pain points) are often the most complex to solve. Adding complexity to the initial solution increases the chances for failure.
- Rapid Adoption Core stakeholders use technology they are already familiar Actionable information surfaced via reports and dashboards from day one AMOA Solidifies adoption and helps minimize disruption Provides for enhancements between phases