SharePoint Spring Workshop & Expo: The Future of SharePoint

Editor's Notes

• #4: Microsoft announced some great new SharePoint capabilities that recognize organizations will not fully move to the cloud so fast, but do want to take advantage of great new cloud capabilities, like new features, rapid patching, and reduced maintenance costs.
• #5: SharePoint 2016 is inspired by the cloud, it is a key element of the cloud first, mobile first world, it is a bridge a stepping stone toward a gradual move to the cloud. That why the main innovation of SharePoint 2016 is the support of an hybrid architecture. Microsoft has also brought to on-premise SharePoint some of the expertise and experience gained by hosting millions of users on Office 365. Probably on the largest business cloud and Microsoft has delivered some infrastructure improvement which were initially developed for Microsoft hosting service. There are also some key enhancements to the user experience both for mobile and the browser. And compliance improvement.
• #6: Will we again face poor SharePoint adoption? Business users ignoring SharePoint, continuing to send attachments, or claiming that they can’t find anything on SharePoint? That’s a double-whammy – organizations are not getting the value out of SharePoint AND they still can’t find important documents and emails when needed.
• #7: In order to fix that we need to recognize that this is not just about technology but about psychology. We can’t be just be IT experts, we must be also adoption experts.
• #9: Microsoft announced some great new SharePoint capabilities that recognize organizations will not fully move to the cloud so fast, but do want to take advantage of great new cloud capabilities, like new features, rapid patching, and reduced maintenance costs.
• #10: First…email refers to content, to those (usually relatively short) messages that we exchange about work; questions, answers, project status updates, gossip, and many other forms of information exchange. More and more that information is the form of document attachments, a relatively late addition to the original idea of email, being added in 1992 – twenty years after email had been invented. Second, email is a service – it where the email gets stored, processed, and routed. Services like Exchange, Gmail, and IBM Verse are three examples of business email services, and there are many consumer versions of this. Lastly, email is an interface, and here we have many…on the desktop, in the browser, and on mobile devices. Outlook is an example of the desktop, which works by the way, with other email services besides Microsoft’s, such as Gmail. On mobile devices, there are many options, ranging from native apps like Outlook and OWA, Gmail and Inbox, and Verse to third party apps like Mailbox. Today, when people talk about their reliance on email and their affinity (or hatred) of email, they are often referring to the interface.
• #11: The email interface, the Outlook client we are all using on the desktop for instance, is where we spend our workday. According to a recent poll, we spend almost 80% of our work time in the email client. Not because we are sending so much correspondence, but because the email interface is the one place where everything comes together. Like what?
• #12: Tomorrow, email will be used more, not less. Because two additional capabilities will find their way and expand into the email interface. In fact, according to the Radicati Group, tThe biggest growth in email is due to more and more services sending notifications there – notifications that you need to take some action. Notification from business apps, social networks, project status changes, and the like. And why are folks sending notifications there? Because that is where you spend so much time. You are guaranteed to see the notifications and won’t mess up by missing out. Notifications are a natural, particular for mobile email, where people expect to get real time alerts. But how will be able to make sense of all the incoming and disconnected notifications? For that we will need to add some smarts.
• #13: Intro and background…. Mention experience working with Liberty Intl underwriters (insurance claims), SCE (Legal matters), Tarpon Energy (oli and gas services), Exxon, Citi, …just start working a project with House of Commons (CA govt) both collaboration and basically – managing Public Works (office renovations, etc)
• #14: Office Groups, ad hoc, easy to assemble, tear down – are great for event planning, short lived projects… While SharePoint with all the bells-and-whistles, possibly including additional 3rd parties, such as Gimmal for RM … can be applied to meet the requirements of your organization.
• #15: The good news on the governance, compliance side, is that many of your orgs are already investing in these areas; and if you manage your projects on SP you get the benefits….whether ir’s simply mgmt. of the platform – data backup, server maintenance, accessibility … to additional tools for eDiscovery.
• #16: Business requirements: Publish/Save content - Findability/Seachability Collaboratioing on content Mobility Real time updates Sharing content