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  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:

Are you burned out? can help you get out of it.


From: <> On Behalf Of Patrick Lambe via
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. 




Patrick Lambe


+65 62210383

twitter: @plambesg

Knowledge mapping made easy:


On 5 May 2020, at 12:53 AM, Catherine Shinners <catherineshinners@...> wrote:




If you are broadening from SharePoint to the full O365 capabilities, you might consider careful adoption and engagement programs along with the guidance and governance that Dan Ranta mentioned. 


I have noticed in projects I've seen that energy towards enablement and training often drops off quickly after "rollout" leaving a gap in people's understanding of the different contexts for using the capabilities .    Developing good use case scenarios can be helpful.   Sustained adoption support is vital


Here are some questions or use cases that I've seen omitted or not addressed well.

  • When should we use Teams, when is Yammer a good idea?
  • How can we integrate various tools for different contexts? 
  • Should we use Yammer for Corporate Communications? Teams for teamwork, 1:1 messaging,?
  • Would SharePoint with Yammer integration be good for Communities of Practice?



Without this kind of explicit use case development and sustained adoption support, the capabilities may be frequently misapplied leading to user frustration and subsequently languishing.   Rollout is a technology project concept.  Sustained enablement applied to use cases and workflows is a separate concept.


Recent links

Image removed by sender.


DIGITAL WORKPLACE for Business Transformation

650.704-3889 Silicon Valley USA   

Image removed by sender.Image removed by sender. 

digital workplace | communications  |  knowledge management | community management | Prosci certified change professional


Join to automatically receive all group messages.