Information Architecture and Microsoft Teams - What You Need to Know! #OTSTWIT E22

Joy T. Apple, or Joy of SharePoint, took time with Craig & Jay to talk about the many considerations you should have when considering the Information Architecture of your Teams.

Joy starts with a walk down memory lane, reminding us the relationship between sites, site collections, and content databases before discussing how the information architecture for Microsoft Teams and SharePoint has changed over the past decade.

We then talk about the relationship between SharePoint and Microsoft Teams and importance of today's flat architecture instead of building deep folder structures within your Teams files.

For example, did you know you can build different views for your files AND view them from Teams?

Then we discuss Private Channels - and should we use them? Private Channels are an EXCEPTION, not a rule. Each Team provides a security boundary, and within teams, Channels provide a contextual boundary, but when does it become appropriate to provide additional security to that contextual boundary? If you've ever been a SharePoint admin, Joy compares Private channels to the breaking of SharePoint permissions - so true.

But what about my Teams List? Joy tells us she cleans her Teams list up weekly - hiding each Team she isn't active in at the beginning of each week.