1 / 28

Designing the new generation of SharePoint intranet

Designing the new generation of SharePoint intranet. Yaroslav Pentsarskyy Knowledgetech Consulting. Sponsors. Enterprise Standard. Agenda. Expected vs. Nice to have Determining solution roadmap Determining core business goal Information Architecture matters

alamea
Download Presentation

Designing the new generation of SharePoint intranet

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Designing the new generation of SharePoint intranet YaroslavPentsarskyy Knowledgetech Consulting

  2. Sponsors Enterprise Standard

  3. Agenda • Expected vs. Nice to have • Determining solution roadmap • Determining core business goal • Information Architecture matters • Trends in information architecture • User experience matters • UE adaptable to various form factors • Interaction on your sites

  4. About me Involved in SharePoint since 2003 SharePoint MVP (2009-Present) Twitter: @spentsarsky Blog: sharemuch.com My books …

  5. Our goal • Help you think on how to build better collaboration sites • Make sure you’re aware of tools to help you do that • Ensure that you get valuable tips

  6. Requirements … and why are we talking about this • Great user interface • Mobile compatibility • High availability • Extensibility • High performance • Offline caching • Fast response/per transaction • Security • Low maintenance/easy config • Nice to have • Expected

  7. SharePoint solution requirements • Great user interface • Mobile compatibility • High availability • Extensibility • High performance • Offline caching • Fast response/per transaction • Security • Low maintenance/easy config • Nice to have • Expected

  8. SharePoint solution requirements • Great user interface • Mobile compatibility • High availability • 99.9% availability • Extensibility • High performance • Offline caching • Fast response/per transaction • Security • Low maintenance/easy config • Nice to have • Expected

  9. SharePoint solution requirements • Great user interface • Mobile compatibility • High availability • 99.9% availability • Extensibility • High performance • 1 minute search crawl • Offline caching • Fast response/per transaction • Security • Low maintenance/easy config • Nice to have • Expected

  10. SharePoint solution requirements • Great user interface • Mobile compatibility • High availability • 99.9% availability • Extensibility • High performance • 1 minute search crawl • Offline caching • Fast response/per transaction • Security • Legacy system authentication • Low maintenance/easy config • Nice to have • Expected

  11. In reality … • Great user interface • Mobile compatibility • High availability • 99.9% availability • Extensibility • High performance • 1 minute search crawl • Offline caching • Fast response/per transaction • Security • Legacy system authentication • Low maintenance/easy config • Nice to have • Expected ? • Budget • Scope

  12. And the problem is … • Vaguely defined solution roadmap • Unclear business goal • …

  13. Missed future vision • Integration points are missed Results of vaguely defined solution roadmap • Important features fall off the radar • Solution becomes an ad-hoc or intermediate • Major solution rework required very quickly

  14. Unclear business case • Technical requirements only drive the architecture Results of unclear business goal • Low profile of the solution • Users end goal is not met • Cut budget • Low solution adoption • Requirements don’t meet expectation • Low solution adoption • Low reputation of the platform • Low reputation of the platform

  15. Business goal for an intranet: help to collaborate and connect

  16. Volumes of information calls for structure

  17. Structure calls for complexfeatures Features Farm Features Web Application Content DB Features Site collect. Features Top-level site Sub site Sub site List/Library [Folder] Item / Document

  18. Common intranet implementations

  19. What do usersneedfrom an intranet • Be real time • Roll up and feed information to users from multiple sources • Be helpful • Display information relevant to each user, the tools are there • Be connected • Allow user to discover new information sources • Be mobile • Let users access useful bits quickly by mobile

  20. An example of approaching all 4

  21. Demo Interactive and personalized IA

  22. The roadmap trends … mobility Search: Kyle Schaeffer Responsive masterpage

  23. Demo Mobility responsive sites

  24. The roadmap trends … deviceusability

  25. Demo Interactive sites

  26. User interface trends

  27. Sponsors Enterprise Standard

  28. REGISTER NOW! www.sharepointconference.com Join us in Las Vegas for SharePoint Conference 2012! Don’t miss this opportunity to join us in Las Vegas at the Mandalay Bay November 12-15 Engage with the community Give yourself a competitive edge and get the inside scoop about 'SharePoint 15' while learning how to better use SharePoint 2010 Share insights Learn about what’s coming next, from the people who built the product

More Related