blog header-cdh2.png

Insights Blog

Providing thought leadership around hot topics in technology

Check and Configure SharePoint User Permissions

on Jan 2, 2019 2:33:50 PM By | Clay Osborn | 0 Comments | SharePoint Microsoft Microsoft Office Office 365 intranet Governance
Ever have a SharePoint gotcha problem before? It’s highly likely that your answer is yes and you are not alone. SharePoint has lots of gotchas and it can be difficult to troubleshoot sometimes. However, there are some really simple yet powerful features that are built right into the interface. Site collection administrators will find these features easily accessible and usable to trouble shoot why somebody doesn’t have access to certain resources. This blog covers the features that allow you to check guest permissions in SharePoint.
Read More

Reduce Noise Level and Manage Membership in Microsoft Teams

on Dec 18, 2018 6:00:00 AM By | Ryan Charnock | 0 Comments | Microsoft communication Collaboration Microsoft Teams Governance
If you have a large family like I do, you know that sometimes the holiday party gets really noisy because there are just a lot of people. Same goes for Microsoft Teams within , especially in a large organization. 
Read More

Microsoft Teams Naming Convention

Let’s start with a question.
Read More

Coaching Governance Committees

on Nov 13, 2018 10:04:09 AM By | Ryan Charnock | 0 Comments | Insider communication Technology Consulting Governance
Five months ago I handed off a new Office 365 environment to an inspired governance team. They had clear direction, set goals, metrics to define success, and a game plan to gather low-hanging fruit. #MyWorkHereIsFinished   Yesterday, I attend their monthly governance meeting. Coming into this meeting my curiosity was g centered around what level of success they had, and what I can do to keep them organized for the next sprint. We met in the same room we did five months ago, and I lead with the following question: Where have you had success? Everyone from the 10 person teams chimed in "Yammer"! I said "tell me about it". They went on with glowing reports about, the reduction of "All -company" informational emails, and that they have lots of engagement from users. I probed and asked "Is it just corporate communications that is posting content, or are other areas of the organization contributing?" They said "No, all the business units are posting.  Sales deals, updates from construction sites, and other 'good to know' stuff that is happening in the company".  Within the same breath the team also had clear ideas about the struggles they have had with Yammer. "Some user's don't 'DO' Yammer. They say they don't have time for that." Company culture information is not business critical and understandable if someone is in a busy season and just doesn't have time for it all.” Personally, I get it, I get busy and company culture takes a back seat to my more pressing needs. This is why I like having this information segmented into a single App or area. So when I do I have time I can choose when I engage with that content. If it came into my inbox as email, it would just be noise and add more for me to manage or distract me during a busy season. The key is being empowered to choose when is a good "appropriate" time to review and engage with the broader organization.   I followed up with the question "What would you like to do about those who are Not-engaged and are missing out?" The team quickly spun up a few ideas, like: Each department champion going one-on-one to make sure that everyone is aware of what content is on Yammer, and they know how to use the tool and set up the notifications that fit their tastes.  That sounded like a great idea. Notice I didn’t come up with the idea the team did. So then I changed gears away from Yammer and went more general. "What has not gone well?" they said "There has been a lot of change over the last five months. We have a new Executive team that is not located here at the corporate offices in Michigan." Now THAT is a challenge. A few things rattled through my mind:
Read More