Online Collaboration Tools

Pick the Right Tool for the Job

Not every conversation needs a meeting. Use this decision chart:

• Quick question, one person, not urgent → Chat message (Slack, Teams, WhatsApp).
• Quick question, whole team → Post in a team channel. People answer when they can.
• Discussion that benefits from back-and-forth → Schedule a 15–30 minute video call with a clear agenda.
• Status update, no discussion needed → Write it in a shared document. Don't hold a meeting.
• Complex decision with multiple stakeholders → Async document first with comments, then a short meeting to resolve open points.
• Emergency, need answer now → Call. Don't send "Hi" in chat and wait.

Video Meetings That Don't Waste Everyone's Time

Before the Meeting

• Share an agenda at least 24 hours ahead. If you cannot write an agenda, you probably do not need a meeting.
• Test your audio and camera 5 minutes before. Do not be the person troubleshooting while eight others wait.
• Mute notifications on your phone and computer. A meeting is not multitasking time.

During the Meeting

• Mute when not speaking. Background noise — chickens, traffic, construction — is distracting for everyone else.
• Use the chat for links and questions. It keeps the audio clear and creates a written record.
• Share your screen, not your whole desktop. Nobody needs to see your browser tabs or message notifications.
• End with clear action items. Who is doing what, by when? Write this in the chat before signing off.

Bandwidth-Saving Tips for Zambia

• Turn off your video if your connection is unstable. Audio-only uses a fraction of the data.
• Close other tabs and apps during the call — they consume bandwidth in the background.
• Zoom and Teams both have "low bandwidth" modes. Enable them in settings.
• If video is essential, use "Speaker View" rather than "Gallery View" — it only streams one high-quality feed.

Chat Tools: Slack, Teams, and WhatsApp

Chat tools are great — and they can also be exhausting. Here is how to use them well:

• Use threads. Reply in a thread instead of the main channel. It keeps conversations contained and makes it easy to catch up later.
• Write the whole message at once. Do not send "Hello" and wait. Send: "Hello — quick question about the report. Do we have the Q2 numbers yet?" People can answer when they see it.
• Set your status. If you are in a meeting, deep in focused work, or off for the day — set your status. It tells people not to expect an immediate reply.
• Respect quiet hours. Unless it is urgent, do not send work messages after 7 PM or on weekends. Schedule them to send the next morning instead.

Shared Documents: The Real Collaboration Engine

Shared documents (Google Docs, Office 365) are where most real collaboration happens. Here is how to make shared documents work for your team:

• One document, not many. Do not email "Report_v3_Tuesday_FINAL.docx." Have one shared document. Everyone works in the same place.
• Suggesting mode, not editing mode. When reviewing someone else's work, use Suggesting mode (Google Docs) or Track Changes (Word). The author accepts or rejects each change.
• Comments, not inline edits. If something is unclear, leave a comment. "Should we add data to support this claim?" is better than silently rewriting it.
• @-mention for attention. Type @name in a comment to notify a specific person. Use this instead of sending a separate message.
• Clear naming conventions. Name documents so anyone can find them: [Project] — [Document Type] — [Date]. Example: "AI Literacy Programme — Lesson Plan — 2026-07-25."

Async-First: The Mindset Shift

The best collaboration does not happen in real time. It happens asynchronously — people contribute when it works for them, not when a meeting time forces everyone into the same hour. This is especially important for teams spread across time zones, or where internet access is inconsistent.

Three habits that make async collaboration work:

• Write things down. Decisions, context, progress — if it is not written, it does not exist for people who were not in the room.
• Default to public channels. Ask questions in team channels, not DMs. The answer might help someone else.
• Over-communicate intent. In async work, tone is easily misread. "Can we review this?" sounds neutral. "Why wasn't this reviewed?" sounds accusatory. Write the kinder version.