Creating value out of SharePoint and getting your company to love you
•Download as PPTX, PDF•
0 likes•872 views
Creating value out of SharePoint and getting your company to love you, as presented by Patrick O'Toole at SharePoint Fest Chicago 2014
Recommended
Recommended
More Related Content
What's hot
What's hot (10)
Viewers also liked
Viewers also liked (19)
Similar to Creating value out of SharePoint and getting your company to love you
Similar to Creating value out of SharePoint and getting your company to love you (20)
Recently uploaded
Recently uploaded (20)
Creating value out of SharePoint and getting your company to love you
- 2. Your company has SharePoint but your team, your department or your entire company do not seem to get much value out of it
- 3. How can I make a difference in such a big problem?
- 5. Change your process Ensure long-term success
- 6. 1. Be the role model 2. Be inspired! Change your process Ensure long-term success
- 7. 1. Be the role model SharePoint ^ “Be the change you wish to see in the world” -- PMaatrhicaktm Oa’ TGoaonledhi
- 8. 1. Learn 2. Test functionality 3. Evangelize 4. Do the right things, always
- 9. 1. Break up monotony 2. Find something fun every day 3. Think differently about your role
- 10. 1. Technical support 2. Cost center 3. Disruptive 1. Problem solvers 2. Add business value 3. Innovative
- 11. “[Steve] Peltzman told me his job is… ‘helping define and drive our business strategy, as well as being responsible for how we use technology to ‘win, serve, and retain’ customers.’”
- 13. Change yourself Ensure long-term success
- 14. 1. Identify problems 2.Solution & build 3. Wrap up Change yourself Ensure long-term success
- 15. 1. Identify problems 2.Solution & build 3. Wrap up
- 16. 1. Identify problems 2.Solution & build 3. Wrap up
- 17. 1. Identify problems Listen to your coworkers, Identify pain points, Document and Prioritize your conversations
- 18. Why identify? “Do not assume that anything you create will provide value …for anyone”
- 19. Listen and identify 1. Ask the right questions 2. Listen for problems and dive deeper Do not think about a solution yet
- 20. Listen and identify: bad questions 1. “What can SharePoint do for you?” 2. “How can we help you?” 3. “Would an approval workflow help you?”
- 21. Listen and identify: good questions 1. “Tell me about a typical day.” 2. “What tasks take you the longest?” 3. “What is most frustrating to you?” 4. “Tell me about the last significant issue you faced.”
- 22. Listen and identify: good questions 1. “What are some of your short term (or long-term) goals as a team, department, etc.” 2. “What parts of your strategy seem most difficult for you to obtain?”
- 23. Document and prioritize 1. Document the problems you discovered 2. Take a guess at impact Do not think about a solution yet
- 24. What to document 1. Stakeholders 2. Problem details 3. Success criteria 4. Impact (1-5)
- 25. 1. Identify problems 2.Solution & build 3. Wrap up
- 26. 2. Solution & build Spend time solutioning the problems your heard, choose a single solution and build
- 27. Solutioning Simple Low support Extensible
- 28. Solutioning Simple Low support Extensible 1. OOtB 2. Create less 3. Limit changes
- 29. Solutioning Simple Low support Extensible 1. Will business change? 2. Users/IT extend 3. Anticipate
- 30. Solutioning 1. You should not support Simple Low support 2. Over-document 3. Change behavior Extensible
- 31. Solutioning Simple Low support Extensible
- 32. Choose and build 1. Choose 2. In case of ties – select higher impact 3. Consider stakeholders 4. Build, test and demo
- 33. 1. Identify problems 2.Solution & build 3. Wrap up
- 34. 3. Wrap up Communicate value & review your solution
- 35. One pager 1. Business problem 2. Solution 3. Value
- 36. Elevator pitch Be prepared to tell a 2-3 minute story about your solution ...and USE IT Setting Characters Conflict Resolution Results
- 37. Formally communicate value 1. Email (copy their managers) 2. Display on team site 3. Use elevator pitch
- 38. Review solution Introducing Ad hoc governance Creating and reviewing rules on a solution-by-solution basis
- 39. Review governance policies: How? Review 1. Features used 2. People involved 3. Processes created Ask Should any standard rules be applied?
- 40. 1. Document technical solution 2. Present solution details to a team member 3. Note any lessons learned
- 42. Change yourself Change your process
- 43. Your work is just beginning!
- 44. 1. Training plan 2. Support plan 3. Manage incoming request Stick to your guns!
- 45. Explore future functionality Anticipate big solutions 1. New features (Yammer, Delve) 2. Custom development
- 47. Slalom Consulting University of Illinois Capricorn @OToolePatrick Patrick O’Toole
- 49. The Problem: “Frustration” – Reuben Stanton What Can I Do?: “Lazy dog” – Héctor García Be the Role Model: “Leadership” – Pedro Ribeiro Simões Identify: “Ehtsham & Alexander in Conversation” – Erik Ogan Wrap-up: “DSC_2680 copy” – Philip Watts Long-term success: “2010 Stanley Cup Champions Chicago Blackhawks Parade” – critiqual
- 50. Appendix
- 51. Simple (details) 1. Use out of the box features 2. Limit the amount of collateral 3. Limit the changes to the existing Simple environment (permissions, features, etc.)
- 52. Extensible (details) 1. Think about how business problem might evolve Extensible 2. Provide users with ability to extend 3. Anticipate additional requirements
- 53. Low support (details) 1. Create an application that requires little support from you 2. Do not change behavior 3. Provide documentation as needed Low support
Editor's Notes
- Change title according your content
- There are a lot of ways to approach this. This presentation focuses on tips tricks and tactics that you personally (or your small team) can do to create SharePoint value, and in the process get your company to love you
- Learn Read blogs Attend SharePoint Saturdays A good place to start: http://en.share-gate.com/blog/begin-learning-sharepoint-office365-between-two-farms Search Channel 9 SharePoint Conference Test functionality on yourself or your team. Experiment with the product before you encourage anyone else to use it Evangelize the technology. Never complain about it. Do the right things Upload documents to Libraries Use categories over folders Keep your site’s information current
- From article in the Harvard Business Review Steve Peltzman – Forrester Research Title: IT Has Finally Cracked the C-Suite Link: http://blogs.hbr.org/2014/07/it-has-finally-cracked-the-c-suite/
- “If you build it, they will come” is certainly not true for SharePoint.
- This can be a formal process (scheduled meeting) Or an informal conversation at the ‘water-cooler’ or at happy hour!
- Don’t ask questions that are - Require your colleague to know what SharePoint is Are vague and open ended Use any technical jargon (approval workflow, document library, etc.) Or begins to hint at a solution
- You can ask vague questions if you are prepared to delve deeper!
- You can also ask about future thinking
- DO NOT start thinking of the solution until you’ve identified problems
- You may want to document more!
- The three things I think about every time I solution Keep it simple Use out of the box technology when possible Favor toward less collateral (less lists, libraries, columns, web parts, etc.) Plan for extensibility Think outside of the initial complaint/problem Think of ways this may be extended There should be little to no support involved with your solution As needed provide documentation or training with the solution
- Favor out of the box features and features with which you have experience Limit the amount of content (lists, libraries, workflows, web parts, pages, etc.) that you need to create Limit the changes to the existing environment
- Think about how business problem might evolve. Ask the user if they can think of ways the business problem might evolve. Ask them how it has changed so far. Provide users with ability to extend Anticipate additional requirements
- Create an application that requires little support from you Provide documentation as needed Consider all the actions that will be taken and provide documentation on all (or at least some) of them Do not change behavior. Or at least limit it at first (especially when getting buy in)
- The three things I think about every time I solution Keep it simple Use out of the box technology when possible Favor toward less collateral (less lists, libraries, columns, web parts, etc.) Plan for extensibility Think outside of the initial complaint/problem Think of ways this may be extended There should be little to no support involved with your solution As needed provide documentation or training with the solution
- There is only 1 bullet point in this whole presentation that talked about the building and testing process. This is intentional. These solutions should be simple and require little testing. Feel free to add additional rigor to this step (test scripts, UAT, sign-off, etc.) – you will likely have to do this later when you build more complex solutions anyway.
- Business Problem Solution Value Note any value provided. Include numbers if possible.
- Prepare to tell a story and include characteristics of stories Introduce the setting Introduce the characters Make sure to use human characters or give technology human characteristics Describe the conflict Provide the resolution Embellish the results Consider posting these one-pagers or Elevator Pitches on your team site for others to see
- Send email (and potentially acknowledge involved people on your team site) Store collateral (PUBLICALLY) on team site USE the elevator pitch on doubtful employees, other colleagues, friends & family *As part of her overall adoption strategy, Sarah Haase does a good job with communicating this value. Check out her SharePoint Conference presentation for more information: http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC296
- Example 1: Document Library for the Sales team Features: Document Library, versioning, out of the box columns displayed (created, created by, modified, modified by) People: 15 members of the sales team that ae “members” of the site so they can edit documents Processes: When a new sales pursuit is started, the lead team member creates a PowerPoint (using the standard template) and uploads it to their library. The name of the document should follow the format ClientName_ProjectTitle.pptx
- Favor out of the box features and features with which you have experience Limit the amount of content (lists, libraries, workflows, web parts, pages, etc.) that you need to create Limit the changes to the existing environment
- Think about how business problem might evolve. Ask the user if they can think of ways the business problem might evolve. Ask them how it has changed so far. Provide users with ability to extend Anticipate additional requirements
- Create an application that requires little support from you Do not change behavior Provide documentation as needed Consider all the actions that will be taken and provide documentation on all (or at least some) of them