Cross-Functional · Playbook · Intermediate · Saves 30+ hours
Slack/Teams Governance Guide
A guide for governing communication tools effectively.
What's included
- Channel structure
- Naming conventions
- Usage guidelines
- Notification management
- Integration management
- Onboarding and offboarding
Best used when
- Setting up communication tools
- Cleaning up channel sprawl
- Onboarding new employees
- Improving signal-to-noise
Why this is Gold
Ungoverned Slack/Teams becomes chaos. This guide creates order and efficiency.
The template
Overview
GOVERNANCE PHILOSOPHY
Why Communication Tool Governance Matters
THE CHAOS OF UNGOVERNED COMMUNICATION TOOLS
═══════════════════════════════════════════════════════════════
SYMPTOMS OF POOR GOVERNANCE:
┌─────────────────────────────────────────────────────────────┐
│ "Where do I find information about X?" │
│ "Which channel is the right one for this?" │
│ "I didn't see the important announcement" │
│ "Why are there 47 channels with no clear purpose?" │
│ "My notifications are overwhelming" │
│ "New employees can't find anything" │
│ "Sensitive info was shared in the wrong channel" │
│ "Is #team-eng or #eng or #engineering the right one?" │
└─────────────────────────────────────────────────────────────┘
THE BUSINESS IMPACT:
• Lost productivity searching for information
• Important messages missed in noise
• Duplicate conversations in multiple places
• Security/compliance risks from sprawl
• Onboarding takes longer
• Tribal knowledge not captured
GOVERNANCE PRINCIPLES:
┌─────────────────────────────────────────────────────────────┐
│ 1. DISCOVERABILITY OVER FLEXIBILITY │
│ Consistent naming > creative names │
│ Fewer well-organized channels > many random ones │
│ │
│ 2. SIGNAL OVER NOISE │
│ Quality of notifications > quantity │
│ Threads > channel clutter │
│ Right channel > broadcast everywhere │
│ │
│ 3. DOCUMENTATION OVER CONVERSATION │
│ Important info pinned/linked > buried in history │
│ Decisions recorded > lost in chat │
│ │
│ 4. OWNER FOR EVERY CHANNEL │
│ Someone maintains, cleans, archives │
│ Channels without owners get archived │
│ │
│ 5. REGULAR HYGIENE │
│ Quarterly reviews │
│ Archive aggressively │
│ Consolidate duplicates │
└─────────────────────────────────────────────────────────────┘
COMPREHENSIVE GOVERNANCE FRAMEWORK
Section 1: Channel Architecture
CHANNEL NAMING CONVENTIONS
═══════════════════════════════════════════════════════════════
STANDARD PREFIXES:
┌─────────────────────────────────────────────────────────────┐
│ PREFIX │ PURPOSE │ EXAMPLES │
├─────────────────────────────────────────────────────────────┤
│ #team- │ Team-specific channels │ #team-engineering │
│ │ │ #team-sales │
│ │ │ #team-marketing │
├─────────────────────────────────────────────────────────────┤
│ #proj- │ Project channels │ #proj-q1-launch │
│ │ (temporary, archivable) │ #proj-website-v2 │
├─────────────────────────────────────────────────────────────┤
│ #dept- │ Department-wide │ #dept-product │
│ │ │ #dept-operations │
├─────────────────────────────────────────────────────────────┤
│ #announce- │ Announcements (read-only │ #announce-company │
│ │ or limited posting) │ #announce-hr │
├─────────────────────────────────────────────────────────────┤
│ #help- │ Support/help requests │ #help-it │
│ │ │ #help-hr │
│ │ │ #help-facilities │
├─────────────────────────────────────────────────────────────┤
│ #ask- │ Q&A for specific topics │ #ask-legal │
│ │ │ #ask-finance │
├─────────────────────────────────────────────────────────────┤
│ #social- │ Non-work topics │ #social-pets │
│ │ │ #social-books │
│ │ │ #social-random │
├─────────────────────────────────────────────────────────────┤
│ #loc- │ Location-based │ #loc-nyc │
│ │ │ #loc-remote │
├─────────────────────────────────────────────────────────────┤
│ #ext- │ External/vendor channels │ #ext-agency-acme │
│ │ │ #ext-partner-xyz │
├─────────────────────────────────────────────────────────────┤
│ #alert- │ Automated alerts │ #alert-deployments│
│ │ │ #alert-monitoring │
└─────────────────────────────────────────────────────────────┘
NAMING RULES:
☐ Use lowercase only
☐ Use hyphens (not underscores or spaces)
☐ Keep names concise but descriptive
☐ Always use the standard prefix
☐ Include dates for time-bound projects: #proj-2025-q1-launch
CHANNEL DESCRIPTION TEMPLATE:
┌─────────────────────────────────────────────────────────────┐
│ PURPOSE: [One sentence explaining what this channel is for] │
│ │
│ WHO: [Who should join this channel] │
│ │
│ OWNER: @[channel owner] │
│ │
│ RULES: [Any specific posting guidelines] │
│ │
│ RELATED: #[related-channel-1] #[related-channel-2] │
└─────────────────────────────────────────────────────────────┘
Section 2: Channel Lifecycle Management
CHANNEL LIFECYCLE FRAMEWORK
═══════════════════════════════════════════════════════════════
NEW CHANNEL CREATION CHECKLIST:
┌─────────────────────────────────────────────────────────────┐
│ BEFORE CREATING: │
│ ☐ Search for existing channels that might serve the need │
│ ☐ Consider if this could be a thread in existing channel │
│ ☐ Confirm this isn't a duplicate of an archived channel │
│ ☐ Get approval from [workspace admin/manager] if required │
│ │
│ DURING CREATION: │
│ ☐ Use appropriate naming convention │
│ ☐ Write clear channel description │
│ ☐ Set appropriate visibility (public vs private) │
│ ☐ Assign channel owner │
│ ☐ Add default members │
│ │
│ AFTER CREATION: │
│ ☐ Pin posting guidelines/welcome message │
│ ☐ Pin relevant links/documents │
│ ☐ Announce in appropriate channel │
│ ☐ Add to channel directory (if maintained) │
└─────────────────────────────────────────────────────────────┘
CHANNEL REQUEST FORM:
┌─────────────────────────────────────────────────────────────┐
│ CHANNEL REQUEST │
│ │
│ Requested name: #__________________________________ │
│ Requested by: ______________________ Date: ____________ │
│ │
│ PURPOSE: │
│ _________________________________________________________ │
│ _________________________________________________________ │
│ │
│ WHO NEEDS ACCESS: │
│ ☐ Whole company ☐ Specific teams: ________________ │
│ ☐ Project-specific ☐ External guests │
│ │
│ VISIBILITY: │
│ ☐ Public (anyone can join) │
│ ☐ Private (invite only) │
│ Reason if private: ____________________________________ │
│ │
│ CHANNEL OWNER: ________________________________________ │
│ │
│ EXPECTED LIFESPAN: │
│ ☐ Permanent ☐ Until project ends: _________________ │
│ ☐ Time-bound: ________________________________________ │
│ │
│ EXISTING ALTERNATIVES CONSIDERED: │
│ _________________________________________________________ │
└─────────────────────────────────────────────────────────────┘
ARCHIVE CRITERIA AND PROCESS:
┌─────────────────────────────────────────────────────────────┐
│ ARCHIVE WHEN: │
│ ☐ Project is complete (project channels) │
│ ☐ No activity for 90+ days (most channels) │
│ ☐ No activity for 30 days (project channels) │
│ ☐ Team/initiative no longer exists │
│ ☐ Duplicate of another channel │
│ ☐ Original purpose no longer relevant │
│ │
│ ARCHIVE PROCESS: │
│ 1. Post warning: "This channel will be archived in 7 days │
│ due to [reason]. Speak up if it should stay active." │
│ 2. Wait 7 days for objections │
│ 3. Export important information if needed │
│ 4. Archive the channel │
│ 5. Update channel directory if maintained │
│ │
│ NOTE: Archived channels are searchable and can be restored │
└─────────────────────────────────────────────────────────────┘
QUARTERLY CHANNEL AUDIT:
| Audit Item | Action |
|------------|--------|
| Channels with no owner | Assign owner or archive |
| Channels with no activity (90 days) | Archive or explain |
| Duplicate/overlapping channels | Merge or clarify |
| Channels with poor descriptions | Update descriptions |
| Unused private channels | Review access, archive |
| Channels violating naming conventions | Rename |
Section 3: Posting Guidelines
POSTING BEST PRACTICES
═══════════════════════════════════════════════════════════════
@-MENTION USAGE GUIDE:
┌─────────────────────────────────────────────────────────────┐
│ @channel (or @all) │
│ ├─ Notifies EVERYONE in the channel │
│ ├─ Use ONLY for: True emergencies, major announcements │
│ ├─ NEVER use for: FYIs, routine updates, questions │
│ └─ Approx. 1-2 times per month maximum │
│ │
│ @here │
│ ├─ Notifies only people currently active │
│ ├─ Use for: Time-sensitive but not emergency │
│ └─ Appropriate for: "Anyone available to help with X?" │
│ │
│ @name (individual) │
│ ├─ Notifies specific person │
│ ├─ Use for: Direct questions, assigning action items │
│ └─ Preferred over DM when context helps others │
│ │
│ @group (user groups) │
│ ├─ Notifies all members of a group │
│ ├─ Use for: Team-specific announcements/requests │
│ └─ Examples: @engineering, @sales-team, @managers │
└─────────────────────────────────────────────────────────────┘
THREADING REQUIREMENTS:
┌─────────────────────────────────────────────────────────────┐
│ ALWAYS USE THREADS FOR: │
│ ☐ Replies to messages (keeps channel clean) │
│ ☐ Discussions with multiple back-and-forth │
│ ☐ Questions that may generate discussion │
│ ☐ Sharing multiple related links/files │
│ │
│ POST TO MAIN CHANNEL FOR: │
│ ☐ New topics requiring attention │
│ ☐ Important announcements │
│ ☐ Time-sensitive requests │
│ ☐ Items that should be visible to all │
│ │
│ THREAD BEST PRACTICES: │
│ ☐ Check "Also send to #channel" for important updates │
│ ☐ Keep thread focused on original topic │
│ ☐ Start new thread if topic changes significantly │
└─────────────────────────────────────────────────────────────┘
POSTING ETIQUETTE:
┌─────────────────────────────────────────────────────────────┐
│ ✅ DO │ ❌ DON'T │
├─────────────────────────────────────────────────────────────┤
│ Post in most specific channel │ Broadcast to many channels │
│ Use threads for discussions │ Create long main channel │
│ │ conversations │
│ Edit messages to add context │ Post "nm" or corrections │
│ │ as new messages │
│ Use reactions for simple │ Reply "thanks" or "+1" │
│ acknowledgment │ as new messages │
│ Search before asking │ Ask without searching │
│ @mention specific people │ @channel for one person │
│ Include context in questions │ "Hey, quick question" │
│ │ with no context │
│ Schedule non-urgent messages │ Post at night expecting │
│ │ response │
│ Use proper formatting │ Wall of text with no │
│ (bullets, code blocks) │ structure │
└─────────────────────────────────────────────────────────────┘
MESSAGE FORMATTING STANDARDS:
┌─────────────────────────────────────────────────────────────┐
│ EFFECTIVE MESSAGE FORMAT: │
│ │
│ 📋 [TYPE] Brief headline │
│ │
│ Context: Why this matters/background │
│ │
│ Key points: │
│ • Point 1 │
│ • Point 2 │
│ • Point 3 │
│ │
│ Action requested: [Clear ask] by [deadline] │
│ CC: @relevant-person │
│ │
│ TYPE PREFIXES: │
│ 📋 = Action needed │
│ 📣 = Announcement │
│ ❓ = Question │
│ 💡 = Idea/proposal │
│ ✅ = Update/status │
│ 🚨 = Urgent │
│ 🎉 = Celebration │
└─────────────────────────────────────────────────────────────┘
Section 4: Notification Management
NOTIFICATION MANAGEMENT GUIDE
═══════════════════════════════════════════════════════════════
RECOMMENDED NOTIFICATION SETTINGS:
┌─────────────────────────────────────────────────────────────┐
│ TIER 1: IMMEDIATE (push notifications on) │
│ • Direct messages │
│ • @mentions of your name │
│ • Keywords you've set (your projects, etc.) │
│ • Emergency/on-call channels (if applicable) │
│ │
│ TIER 2: TIMELY (check regularly, no push) │
│ • Your team's primary channel │
│ • Announcement channels │
│ • @here mentions in key channels │
│ • Project channels you're active on │
│ │
│ TIER 3: BATCH (check 1-2x daily) │
│ • Cross-functional channels │
│ • General/all-company channels │
│ • Social channels │
│ • Info channels (newsletters, updates) │
│ │
│ TIER 4: OCCASIONAL (as needed) │
│ • Archived projects you might reference │
│ • Channels you're in "just in case" │
└─────────────────────────────────────────────────────────────┘
NOTIFICATION HYGIENE CHECKLIST:
┌─────────────────────────────────────────────────────────────┐
│ WEEKLY: │
│ ☐ Leave channels you don't need to be in │
│ ☐ Mute low-priority channels │
│ ☐ Update keyword notifications │
│ │
│ DO NOT DISTURB SETTINGS: │
│ ☐ Set DND hours for after work │
│ ☐ Use DND during focus time │
│ ☐ Configure DND override for true emergencies │
│ │
│ MOBILE SETTINGS: │
│ ☐ Only push for Tier 1 items │
│ ☐ Keep work app off personal devices if possible │
│ ☐ Schedule app to not notify after hours │
└─────────────────────────────────────────────────────────────┘
ORGANIZATION-WIDE NOTIFICATION NORMS:
| Time | Expectation |
|------|-------------|
| Business hours | Standard response times apply |
| 6-9 PM local | May not get response until next day |
| 9 PM - 8 AM local | Do not expect response |
| Weekends/holidays | Do not expect response unless on-call |
| Vacation/PTO | Set status, no response expected |
Section 5: Integration Governance
APP AND INTEGRATION MANAGEMENT
═══════════════════════════════════════════════════════════════
INTEGRATION APPROVAL PROCESS:
┌─────────────────────────────────────────────────────────────┐
│ INTEGRATION REQUEST │
│ │
│ App/Integration name: ________________________________ │
│ Requested by: _________________ Date: ________________ │
│ │
│ PURPOSE: │
│ _________________________________________________________ │
│ │
│ DATA ACCESS REQUIRED: │
│ ☐ Read messages ☐ Post messages │
│ ☐ Read channels ☐ Create channels │
│ ☐ Read user info ☐ Modify user info │
│ ☐ Read files ☐ Upload files │
│ ☐ Other: _______________________________________________ │
│ │
│ SECURITY REVIEW: │
│ ☐ Vendor security reviewed │
│ ☐ Data handling acceptable │
│ ☐ No sensitive data exposed │
│ │
│ APPROVED: ☐ Yes ☐ No │
│ Approver: _________________ Date: ________________ │
└─────────────────────────────────────────────────────────────┘
BOT CHANNEL BEST PRACTICES:
┌─────────────────────────────────────────────────────────────┐
│ FOR AUTOMATED NOTIFICATIONS: │
│ │
│ DO: │
│ ☐ Create dedicated #alert- channels for automated posts │
│ ☐ Keep bots out of human conversation channels │
│ ☐ Configure bots to post to threads when appropriate │
│ ☐ Set clear descriptions explaining what the bot does │
│ │
│ DON'T: │
│ ☐ Let bots spam main channels │
│ ☐ Allow bots to @channel without approval │
│ ☐ Forget to maintain bot channels │
│ │
│ NOISE REDUCTION: │
│ ☐ Batch low-urgency alerts (hourly/daily digests) │
│ ☐ Filter alerts to only actionable items │
│ ☐ Route to specific channels, not general ones │
└─────────────────────────────────────────────────────────────┘
INTEGRATION INVENTORY:
| Integration | Purpose | Owner | Last Reviewed |
|-------------|---------|-------|---------------|
| ____________ | ____________ | ____________ | ____________ |
| ____________ | ____________ | ____________ | ____________ |
| ____________ | ____________ | ____________ | ____________ |
| ____________ | ____________ | ____________ | ____________ |
Section 6: Security and Compliance
SECURITY AND COMPLIANCE GUIDELINES
═══════════════════════════════════════════════════════════════
CONTENT SECURITY RULES:
┌─────────────────────────────────────────────────────────────┐
│ NEVER SHARE IN SLACK/TEAMS: │
│ ☐ Passwords or credentials │
│ ☐ API keys or tokens │
│ ☐ Customer PII (unless in designated secure channels) │
│ ☐ Financial account numbers │
│ ☐ Social security numbers │
│ ☐ Medical/health information │
│ ☐ Unannounced acquisitions or material events │
│ ☐ Confidential HR matters │
│ │
│ BE CAREFUL WITH: │
│ ☐ Customer names (use private channels) │
│ ☐ Revenue/financial numbers (verify need-to-know) │
│ ☐ Competitor intelligence (appropriate channels only) │
│ ☐ Unreleased product information │
└─────────────────────────────────────────────────────────────┘
EXTERNAL GUEST MANAGEMENT:
┌─────────────────────────────────────────────────────────────┐
│ BEFORE ADDING EXTERNAL GUESTS: │
│ ☐ Confirm business need │
│ ☐ Get manager approval │
│ ☐ Limit to specific channels only │
│ ☐ Brief guest on guidelines │
│ │
│ GUEST CHANNEL RULES: │
│ ☐ Use #ext- prefix for guest channels │
│ ☐ Clearly mark channels with external access │
│ ☐ Review guest access quarterly │
│ ☐ Remove access when engagement ends │
│ │
│ GUEST ACCESS REVIEW: │
│ | Guest | Company | Access To | Expiry | Sponsor | │
│ |-------|---------|-----------|--------|---------| │
│ | _____ | _______ | _________ | ______ | _______ | │
└─────────────────────────────────────────────────────────────┘
DATA RETENTION AWARENESS:
┌─────────────────────────────────────────────────────────────┐
│ REMEMBER: │
│ • Messages may be retained per company policy │
│ • Deleted messages may still be in backups │
│ • Messages can be subject to legal discovery │
│ • Admins may be able to see private channels │
│ │
│ RULE OF THUMB: │
│ "Don't write anything you wouldn't want on the front page │
│ of a newspaper or in a legal proceeding." │
└─────────────────────────────────────────────────────────────┘
Governance Health Dashboard
| Metric | Current | Target | Status |
|---|---|---|---|
| Channels following naming convention | ___% | 95%+ | 🟢🟡🔴 |
| Channels with clear descriptions | ___% | 90%+ | 🟢🟡🔴 |
| Channels with assigned owners | ___% | 100% | 🟢🟡🔴 |
| Inactive channels (90+ days) | ___ | 0 | 🟢🟡🔴 |
| Integrations reviewed this quarter | ___% | 100% | 🟢🟡🔴 |
| @channel usage (per week) | ___ | <5 | 🟢🟡🔴 |
| Guest access reviewed | ___% | 100% | 🟢🟡🔴 |
Frequently asked questions
What is the Slack/Teams Governance Guide?
A guide for governing communication tools effectively.
Who is the Slack/Teams Governance Guide for?
It is built for Cross-Functionals and their teams working on Meetings. The AI coach adapts it to your company, stage, and goals.
What's included in the Slack/Teams Governance Guide?
7 working sections: Overview; Section 1: Channel Architecture; Section 2: Channel Lifecycle Management; Section 3: Posting Guidelines; Section 4: Notification Management; Section 5: Integration Governance; Section 6: Security and Compliance.
How long does the Slack/Teams Governance Guide take to use?
It saves roughly 30+ hours versus building from scratch. Our AI coach can tailor the playbook to your situation in minutes, then hand you a step-by-step plan.
Is the Slack/Teams Governance Guide free?
Yes. You can read the full playbook and start getting coached through it for free. Sign in to save your tailored version and track your next steps.
How does the AI coach help with the Slack/Teams Governance Guide?
The coach teaches you the framework, asks a few questions about your business, tailors the playbook to you, and gives you measurable next steps to execute.