Teams collaboration
Rule: One channel per topic, not one giant chat. Decisions live in Posts (threaded); quick pings in Chat.
Group project setup
- Team name:
CourseCode-ProjectName-Semester - Channels:
General— announcements, meeting linksResearch— sources, shared docsDrafts— work in progressDeliverables— final exports only
- Files tab: pin master Word/PPT; enable version history
- Roles: assign note-taker, editor, presenter rotation in first meeting
Meeting hygiene
| Before | During | After |
|---|---|---|
| Agenda in invite | Record only if all consent | Post notes in channel thread |
| Test mic/camera | Mute when not speaking | List action items + owners |
| Share slides early | Timebox sections | Link recording in Files if allowed |
Chat norms
@mentiononly when you need that person's input- Reply in thread to keep channel readable
- Don't paste full essays in chat — link OneDrive file
Integrations (class context)
- Assignments tab if instructor uses Teams for LMS
- OneNote class notebook if provided
- Planner tab for task board (optional for groups)
Screen share & whiteboard
- Share window not full screen (notification privacy)
- Whiteboard for brainstorming; export snapshot to Files when done
Copilot in Teams (where licensed)
- "Summarize what I missed in this channel this week"
- "Draft meeting notes from the transcript"
- "List open action items from yesterday's call"
Boundaries
- Git/code collaboration for CS projects →
cursor-team-kit+ repo, not Teams files as source of truth - Group-work honesty and citation rules →
citation-literacyplus the course AI-use policy