Knowledgebase

Structuring Teams and Channels Print

  • microsofttechnology, microsoft, guide, howto, solution, zillionkinghost, hosting, support
  • 0

Organising collaboration.

WHAT TO CREATE A TEAM FOR

A group of people working together over time.

WHAT NOT TO CREATE A TEAM FOR

A single conversation A short project, unless it will be archived Every department subdivision

WHAT TO USE CHANNELS FOR

Distinct topics within that team's work.

HOW MANY CHANNELS

Few. Enough that people know where to post.

WHY

Too many, and conversation fragments and nobody follows any of them.

WHAT TO NAME CHANNELS

Descriptively, and consistently.

WHAT TO DO ABOUT TEAM SPRAWL

Restrict creation, or require a request process Review inactive teams periodically Archive teams that are finished

WHAT ARCHIVING DOES

Preserves content in a read-only state.

WHY THAT IS BETTER THAN DELETING

History remains available.

WHAT TO ESTABLISH ABOUT MEMBERSHIP

Owners for every team, and more than one.

WHY MORE THAN ONE

A team whose only owner leaves cannot be administered.

WHAT TO REVIEW

Teams with no owner, which accumulate.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot