Re: SharePoint to Microsoft 365 migration #SharePoint
Robert L. Bogue
At the risk of being redundant, while I have technical tricks up my sleeve, I fully concur with what others including Patrick has said. The challenge is getting to clarity on the behaviors that you want people to have and then communicating the desired behaviors.
Simple questions occur like should I make a new team or a new channel? I’ve attempted to answer some of those questions with a whitepaper “How Many Teams, Sites, Libraries, and Folders?” which you can get at https://thorprojects.com/connect/gifts/white-papers/how-many-teams-sites-libraries-and-folders/ I’ve not publicly announced the whitepaper yet but it will be launched this month. (I just forced the page public so folks here could get it if they want, but it’s not linked from anywhere on the site yet.)
Anything that you can do to make what you want clearer will be helpful.
Robert L. Bogue
O: (317) 844-5310 M: (317) 506-4977 Blog: http://www.thorprojects.com/blog
Are you burned out? https://ExtinguishBurnout.com can help you get out of it.
From: SIKM@groups.io <SIKM@groups.io> On Behalf Of Patrick Lambe via groups.io
Sent: Monday, May 4, 2020 8:06 PM
Subject: Re: [SIKM] Sharepoint to Microsoft 365 migration #discussion-starter
Just to supplement to this great thread, the move is going to be a big change for your user communities, especially in now providing multiple options for where documents can be created and found, compared to SP2013. This IS going to produce confusion and information scatter, notwithstanding careful governance planning, migration planning and the technical fixes that Robert mentioned. This doesn’t really add anything new to the contributions, just emphasises their importance, for having great clarity upfront, and patience and persistence in working with the user communities over the medium to longer term to reshape habituated practices.
Knowledge mapping made easy: www.aithinsoftware.com