We’ve been using Teams for a week now and it’s plain to see that it will become THE UI for the everyday worker. I can actually see it being the business console for nearly everything. Sure the applications will still exist, but Teams will become the portal to access everything. Microsoft have an amazing opportunity that’s for sure.
What I’d love to do here is encourage a little debate around how to govern and control it.
As far as I can see – we have a definite hierarchy :
Teams > Channels > Tabs
1. How are people organising their Teams Structure (e.g. Teams = Projects > Channels = Functions (e.g. sales) > Tabs = Apps)?
2. Are you looking to ‘template’ a channel so it always has the same ‘Tabs’ ?
3. How can you control Teams so that you don’t end up with a mess of Channels and Tabs?
Here’s how we manage the channels for our product DocRead :
And this is how we manage the ‘Tabs’ under ‘Development’.
- Conversations = chat
- Files = Docs (stored in SharePoint)
- Notes = OneNote
- Features, Bugs, Development = Planner Boards
I wanted to link to my friend Melissa Hubbard’s article on this. She spent a lot of time writing a free white paper on this very issue: https://melihubb.com/2017/07/25/microsoft-teams-governance-planning-guide/
Most organizations dealing with sensitive data will need OOB features for Governance and Compliances.
Nice share Matthew.