As Microsoft 365 practitioners, it’s our job to help information workers and end-users understand how to work with Microsoft Teams, Planner, SharePoint, OneDrive, etc. Having a common set of defined terms helps your users stay on top of M365 feature changes and capabilities. If your organization hasn’t done so already, I recommend coming up with a M365 “style guide.” The style guide should define the way in which you refer to M365 products and features. For example:

• How will you refer to a Microsoft Teams team? And how will you distinguish that team from the Teams product or from a SharePoint team site?
• Will you double-up on descriptive terms like “Planner plan” and “Teams team” when you refer to specific M365 groups?
• Will you use capitalization alone to denote an individual plan from the Planner product?

In this episode of M365 Voice, we discuss the challenge of building our enterprise Microsoft vocabulary. Listen in for ideas on how you can consistently refer to your M365 features and products. Enjoy!

Have a Microsoft 365 question? Submit it online! Your question may be featured in a future podcast episode.