Webinar Slides SharePoint is Not PS
- 1. Welcome to the “SharePoint is NOT PS” Webinar We will be starting at the 1PM EST While you’re waiting to begin please chat about the following: “What challenges do you find with using SharePoint as PS both from a design and end- user perspective?” Copyright Ontuitive 2012 0
- 2. SharePoint is not Performance Support! Bob Mosher Chief Learning Evangelist Conrad Gottfredson Chief Learning Strategist John Hall Director of Product Management Copyright Ontuitive 2012
- 3. Some Common Challenges Documented across the Industry: “The inability to find information quickly and easily is one of biggest frustrations for business users. Many organizations have been using SharePoint for years, but it remains nothing more than a glorified file share. In many cases SharePoint has made things worse as users try to find information spread over sprawling sites, web pages, wikis, discussion threads, and document libraries.” (sharepointsemantics.com) • Enterprise Complexity: Business & Technical • No single version of the truth • Costs • No Content Management strategy • Capacity Planning • Application response time • Adoption • Limited mobile support • Search Foundation • Not embedded • Governance • Not Contextual • IT skills dependent Copyright Ontuitive 2012 2
- 4. Question: Have you ever tried to saw a board with a hammer or drive a nail with a saw? This is NOT a discussion around how SharePoint a is “bad” thing… Rather one around better leveraging SharePoint to become an effective part of an overall embedded PS Solution Copyright Ontuitive 2012 3
- 5. Two Performance Support Scenarios: • We use performance support in-house to help our sales team be more productive. They use it constantly. We also have SharePoint. • Let’s walk through an performance support scenario: • Sales rep just got off a call • Can’t remember if the lead should be converted into an opportunity or how to do it in our Salesforce.com CRM • Scenario 1: Uses SharePoint for support • Scenario 2: Uses Performance Support Copyright Ontuitive 2012 4
- 6. Chat: What were some fundamental differences you noticed between the two scenarios? Copyright Ontuitive 2012 5
- 7. Performance Support Sustains Competence in an Ever-Changing Performance Environment On-the-Job Competence Concept & Task Mastery Leaving this to chance extends “Time to Competency” TIME TIME TO COMPETENCYTIME TRAIN TRANSFER VAL U E R E AL I Z AT I O N Value Realization Copyright Ontuitive 2012 6
- 8. Performance Support Sustains Competence in an Ever-Changing Performance Environment Reference and critical skills Training Ready Technology Is the “Game Changer” TIME TO COMPETENCY (Average 50% reduction in Time to Competency) TRAIN TRANSFER VAL U E R E AL I Z AT I O N Software Authored Embedded Performance Support Solution (EPSS) Copyright Ontuitive 2012 7
- 9. The 7 FUNDAMENTAL PS Principles 1. Aligned to deliver business impact. 2. Embedded in the workflow (2 clicks in 10 seconds). 3. Contextual access by process, roles and circumstances. 4. Just enough to get the job done right. 5. Integrated with formal learning. 6. Trusted Always up to date. 7. Scalable across multiple projects and learning solutions Copyright Ontuitive 2012 88
- 10. SharePoint falls short on 6 of the 7 Principles: 1. Aligned to deliver business impact. 2. Embedded in the workflow (2 clicks in 10 seconds). 3. Contextual access by process, roles and circumstances. 4. Just enough to get the job done right. 5. Integrated with formal learning. 6. Trusted Always up to date. 7. Scalable across multiple projects and learning solutions. 9 Copyright Ontuitive 2012 9
- 11. SharePoint falls short on 6 of the 7 Principles: 2. Embedded in the workflow (2 clicks in 10 seconds). Lengthy Immediacy Instant Apply Close distant Proximity 10 Copyright Ontuitive 2012 10
- 12. SharePoint falls short on 6 of the 7 Principles: 2. Embedded in the workflow (2 clicks in 10 seconds). 11 Copyright Ontuitive 2012 11
- 13. SharePoint falls short on 6 of the 7 Principles: 3. Contextual access by process, roles and circumstances. 2-clicks & 10-seconds Workflow 12 12 Copyright Ontuitive 2012
- 14. SharePoint falls short on 6 of the 7 Principles: to specific roles and varying access needs (role and 3. Contextual circumstance) 2-clicks & 10-seconds Job Role 13 13 Copyright Ontuitive 2012
- 15. SharePoint falls short on 6 of the 7 Principles: to specific roles and varying access needs (role and 3. Contextual circumstance) 2-clicks & 10-seconds Incentive Statements View Monthly Incentive Details View Sales Template View Referral Template View Active Checking Template View Insurance /Investments View Quarterly Incentive Details View Incentive Summary Software Structure Incentive Payout View Payout Approval Approve Payout Approval Pay Adjustment Request Request Pay Adjustment Pay Adjustment Approval Approve a Payment Adjustment Goal Input Input a Goal View Goals Edit a Goal Delete a Goal Sales Scorecard View Sales Scorecard Summary View Sales Scorecard Details Sales Adjustments Search for a Sale Request a Sales Adjustment Adjust a Sale Approve a Sales Adjustment Delete a Sale Management Reports View Salary Incentive Payout View Stack Ranking by Segment View Stack Ranking by Job Code View Average Payout Summary 14 View Payout by Component View Percent of Salary and Incentive Payout 14 Copyright Ontuitive 2012
- 16. SharePoint falls short on 6 of the 7 Principles: 4. Just enough to get the job done right. 15 Copyright Ontuitive 2012 15
- 17. SharePoint falls short on 6 of the 7 Principles: 5. Integrated with formal learning Reference and critical skills Training Ready Technology Is the “Game Changer” TIME TO COMPETENCY (Average 50% reduction in Time to Competency) TRAIN TRANSFER VAL U E R E AL I Z AT I O N Software Authored Embedded Performance Support Solution (EPSS) 16 Copyright Ontuitive 2012 16
- 18. SharePoint falls short on 6 of the 7 Principles: 6. Trusted Always up to date. 17 Copyright Ontuitive 2012 17
- 19. SharePoint falls short on 6 of the 7 Principles: 7. Scalable across multiple projects and learning solutions. Insert Demo Ontuitive Sales Workflow screen here – Could we also use the Shell –unbranded one here??? It’s more of an overall dashboard for multiple systems and processes 18 Copyright Ontuitive 2012 18
- 20. Actually, SharePoint falls short on all 7 Principles: 1. Aligned to deliver ROI and specific business benefit 19 Copyright Ontuitive 2012 19
- 21. Final Perspective… “Microsoft SharePoint? It’s like my grandmother’s attic. What I put in there I can never find,” Benioff said. “That’s how I feel about our corporate data.” Marc Benioff - CEO Salesforce.com Copyright Ontuitive 2012 20
- 22. Next Steps… • We would love your feedback • Let’s talk to see what this means to you • Someone from Ontuitive will be in touch in the next 24 hours to gather your feedback • If we can help, let us know! • THANKS for joining us!!! Copyright Ontuitive 2012 21
Editor's Notes
- #6: Get them to help us identify the 7 principles and SP’s shortcomings….
- #9: Reinforce our 7 principles. “We are often asked what are the main reasons a PS solution fails, OR what are the organizations who are making PS work doing right” – They are following 5 or more of the 7 principles!
- #10: The title basically says it all. – IMHO, SP falls short in 6 of the 7 principles
- #11: It is NOT embedded – 2 clicks 10 seconds. You have to “leave” your workflow and moment of apply to find it.
- #12: It is NOT embedded – 2 clicks 10 seconds. You have to “leave” your workflow and moment of apply to find it.
- #13: Although SP can recognize who I am and do some things around making content “intelligent”. It’s not a contextual in the workflow. It does not do a good job of managing the experience and mapping to a workflow. Could use something like Konami to show the importance of entry points like workflow and/or role.
- #14: Although SP can recognize who I am and do some things around making content “intelligent”. It’s not a contextual in the workflow. It does not do a good job of managing the experience and mapping to a workflow. Could use something like Konami to show the importance of entry points like workflow and/or role.
- #15: Although SP can recognize who I am and do some things around making content “intelligent”. It’s not a contextual in the workflow. It does not do a good job of managing the experience and mapping to a workflow. Could use something like Konami to show the importance of entry points like workflow and/or role.
- #16: Pyramid!!! NO pyramid in SP!!!!!
- #17: I’m afraid that this may be too much to cover in the short time we have… I’d prefer RampUp/Rampdown here to keep it simple.
- #19: Building ONE SP site is one thing, BUT replicating it across multiple projects is expensive and time consuming. Plus multiple modalities like mobile and such totally out!! As well as reuse. We could also talk about the “umbrella” dashboard idea here like Shell did. HARD to do, if not impossible across multiple SharePoint sites, OR creating in one site.