SPSDFW Bottom Up SharePoint Design
Download as PPTX, PDF1 like1,533 views
This document discusses building an intranet from the bottom up rather than the traditional top-down approach. It advocates starting simply with personal collaboration tools like OneDrive and building out ad hoc collaboration sites before establishing departmental sites and a centralized landing page. This bending of the value curve allows for quick wins that generate momentum. The document provides an example of an oil and gas company that takes this approach, first promoting safety and providing reports before upgrading their unstable SharePoint farm. It emphasizes an iterative process of defining vision, mapping to value, working solutions, evaluating and adapting as the intranet is developed incrementally from the ground up.
Ad
More Related Content
What's hot (20)
Similar to SPSDFW Bottom Up SharePoint Design (20)
Ad
More from David Broussard (16)
Ad
Recently uploaded (20)
SPSDFW Bottom Up SharePoint Design
- 1. Building Your Intranet From The Bottom Up SharePoint Saturday DFW2015 March 7th, 2015
- 3. The four verbs of the Intranet Intranet Engage Produce Innovate Decide
- 4. How have we always built them? Landing Page Division Front Doors Department Collaboration Ad Hoc Collaboration OneDrive for Business Messaging Collaboration G o v e r n a c e
- 5. But…it takes so long Nielsen Norman Group – Intranet Design Annual 2013,2014,2015
- 6. A highly structured organization is at risk of becoming irrelevant in a quickly changing marketplace… And it’s hard to change
- 8. What matters most to the user?
- 9. The traditional approach… Focus on the Landing Page
- 10. What is the Landing Page?
- 11. What is the Landing Page?
- 12. The Pyramid of SharePoint Value Landing Page Division Front Doors Department Collaboration Ad Hoc Collaboration OneDrive for Business
- 13. The Information Portal as Landing Page
- 14. HEB Grocers – Information Portal Case Study
- 15. HEB – Regional Grocer Scenario: • 60,000 users across many locations • Onboarding process is unique for each job level • Security of information is essential. Need: • Personalized portal for each of my users where they can find life event information, benefit forms, online training and access to other applications quickly and easily. • Especially for the Store Leaders because they manage all types of employees.
- 17. Traditional Top Down How does it get built?
- 18. MSF Waterfall Approach – In Theory Envisioning •Vision/Scope Document •Project Plan and Schedule Planning •BRD •TSD •Governance •Test Plan Developing •Code Assets •Test Scripts Stabilization •Test Results •Training Deploying •Deployment Guide •Project Close- Out
- 19. MSF In Reality Envisioning •Vision/Scope Document •Project Plan and Schedule Planning •BRD •TSD •Governance •Test Plan Developing •Code Assets •Test Scripts Stabilization •Test Results •Training Deploying •Deployment Guide •Project Close- Out
- 20. So, what’s the big issue?
- 21. Build from the Bottom Up A New Approach
- 22. What are our Goals?
- 23. Oh, well, that’s simple then…
- 25. Top Down and Bottom Up Landing Page Division Front Doors Department Collaboration Ad Hoc Collaboration OneDrive for Business
- 26. Turning This… Envisioning •Vision/Scope Document •Project Plan and Schedule Planning •BRD •TSD •Governance •Test Plan Developing •Code Assets •Test Scripts Stabilization •Test Results •Training Deploying •Deployment Guide •Project Close- Out
- 28. Bending the Value Curve Day 1 - OneDrive Month 1 – Ad Hoc Sites Month 2 – Department Sites Month N – Continual Improvement
- 29. Coming all together… Landing page Functional Areas Perm Collab Ad Hoc Collaboration Personal Collaboration
- 30. What does the journey look like?
- 31. Oil and Gas Services Company Practical Example
- 32. Oil and Gas Services Company Scenario: • 3,000 users across many locations, 700 Information Workers • No “owner” for intranet • Currently on SharePoint 2003 with unstable farm • Own Office 365 E1 Plan for 700 users Need: • Promote culture of Safety throughout company • Provide reports to decision makers throughout the company • Must get off unstable farm • Build momentum with quick wins to gain traction across the company
- 34. Map to Value
- 36. Evaluate, Adapt, & Iterate
- 37. Wrap Up
- 38. Pros and Cons
Editor's Notes
- #6: Jakob Nielsen Top 2013 Intranets
- #7: This organizational model has worked well to an extent. But it imposes costs. A highly structured organization is oftentimes a rigid, inflexible organization that cannot adapt quickly to a changing marketplace.
- #13: What does the pyramid mean? One interpretation (original) was that it showed the increasing number of instances at each level (1 landing page, a few DFDs, 1 Dept for each dept, many ad hoc collab, 1 MySite/OneDrive for each employee) I used to show this in the reverse (to show the importance of the top and decreasing amount of work as you go down But, this also shows the value proposition…especially when you look at value against development cost
- #14: By combining lots of personalized widgets, we can craft a page that is specific for a particular use…with specific content for them
- #21: Let me know how that works for you…
- #22: Still, the landing page is hard to build, and take a long time. We have to get it just right
- #26: Craigellachie, British Columbia Craig – uh- loxie -- I THINK!!! Between Revelstoke and Sicamous