Office 365 Distilled

Mickey Mouse takes the front of the stage on EP89 with a business diagram that looks at Collaboration (face) Content (right ear) and Communications (left ear).  The model identifies the core functionality of Content, Collaboration & Communication with the key tools being Exchange, SharePoint Online and MS Teams.

Steve uses the word Personae and Marijn wonders if he is ill.  

Steve has not always been a believer in the default view about personae but in this podcast, he explains that like a complex whisky there is value in personae when the audience value is understood.  He goes on to explain this is described as Focused Usability where the Personae has the Desire (aka ADKAR) because you have identified the specific value they will get from MS Teams or SharePoint Online when combined with Exchange.  Collaboration, Content and Communications

The example discussed is to only allow the personae who need sites to have the rights to create sites.

And right in the middle of this Steve’s mother calls, Wendy Barks and Marijn must drag us back to his golden nugget from this week’s podcast!!

Marijn re-iterates the value in NOT giving everyone the rights to create sites… for example not having to train the personae who do not have rights to create sites.

Viva Insights tells Steve that he responds quickly to emails and Marijn asks if that is a thing… then they get to discuss what you can do in 6 minutes!

The conclusion is that defining policies around when to use a Site, Group, MS team or yammer group depends on the business need.  However, this is a variable in that the personae obtain different values from the M365 toolset depending on the Baseline governance that drives each of the services.

If you get the Awareness and governance by Personae right, you are already halfway to setting up the Desire by identifying the value in the product.

The boys drink the Lagavulin 8-year-old created to commemorate the 200th anniversary of the founding of the Lagavulin distillery by John Johnston in 1816… and they like it a lot!!

Chats are shorter because they already have context but for emails, you often must provide the context so that people can understand the message.

Policies do need to be thought through about external access for Chats.  MS Teams and channel chats are OK as invitees are created as external users but not for Chats.

Marijn outlines the email problems with emails and the problems of losing control and treating the email string as a conversation instead of having… a real conversation.

Worth thinking about email as evidence of a decision made.  Chat can be less instinctive without the context, but the story of an email has a little more depth to describe the decisions being made.

Chat has some risks as it is not always so easy to see who can read the messages like in Email but of course, if we were all open and honest it doesn’t matter.

Chat tends to work the right and left side brains with great creativity tools.

Change program is required to drive a Chat 1st Mentality 

All the old rules apply across Chats as they do for emails, so CAPITAL LETTERS do mean I am shouting and to respond quicker than an email process. 

Marijn and Steve sound a little disappointed with the Jura 7 wood they taste at the end of EP87 but they are not, this was a very deep whisky with great notes at the end.

These are the links to the things we found cool in Barcelona.

Braeburn Podcask  https://open.spotify.com/episode/3CTjSOEP9QZpfkAa8358d1    

Kate took us to a few new Bars and was a fabulous host visiting 4 great places https://www.airbnb.com/experiences/1757637

Kates first choice was Dr. Stravinsky:  https://www.worlds50bestbars.com/the-list/dr-stravinsky.html 

But we found our spiritual home here at La Whiskeria: https://www.facebook.com/lawhiskeria which became our Barcelona home from Home