Documentation & Written Communication

Using Collaborative Tools Effectively (Comments, Shared Docs)

Introduction

Modern work relies on collaborative tools—Google Docs, Figma, Miro, shared project management systems. Used well, they enable async collaboration and transparency. Used poorly, they create confusion, lost feedback, and fragmented communication.

Why This Skill Matters

Tool chaos leads to lost information, unclear decision history, confusion about what's current, and time wasted searching. Good tool practices create clarity, preserve context, and enable efficient async collaboration.

Core Principles

  1. One source of truth - Don't fragment discussions across multiple places
  2. Use comments for specific feedback - Not for decisions or major discussions
  3. Resolve completed threads - Keep active items visible
  4. Tag appropriately - Make sure right people see comments
  5. Summarize scattered feedback - Pull together themes
  6. Elevate important decisions - Don't let critical info live only in comment threads
  7. Version clearly - Make it obvious what's current

Good Examples

Good comment: "@Sarah - Line 47: This wording could be clearer. Suggest: 'Users can export data in CSV format.' Thoughts?"

Good synthesis: After review with 15 comments, send summary: "Key feedback themes: 1) Navigation needs simplification, 2) Color contrast concerns, 3) Missing export feature. I'll address all three and post updated version Friday."

Why It Works

Specific, actionable, tagged appropriately, summarizes for clarity.

Bad Examples

Bad

[Scattered comments across email, Slack, Google Doc, and text messages about same topic]

Why It's Bad

Fragmented, no single source of truth, information will be lost.

Bad

[Critical decision made in comment thread of doc, never elevated or documented elsewhere]

Why It's Bad

Decision gets lost, no visibility, future team members won't find it.

Tips

  1. Agree on tool usage norms at project start
  2. Use threaded comments for back-and-forth
  3. Resolve comments when addressed
  4. Summarize feedback rather than forcing clients to read 50 comments
  5. Take decisions/important info from comments to main document or separate decision log
  6. Use @mentions to ensure visibility
  7. Don't mix async (comments) with sync-required (urgent) items
  8. Keep current version obvious - archive old versions clearly
  9. Provide brief guidance for clients unfamiliar with tools

Connection to Other Skills

Supports proactive communication, creating digestible updates, following through (track feedback systematically), managing expectations about response times, and collaboration effectively.

Action Items

  • Audit current tool usage - is information fragmented?
  • Establish single source of truth for each type of info
  • Create commenting norms: When to comment vs. discuss?
  • Practice summarizing scattered feedback into themes
  • Resolve completed comment threads regularly
  • Elevate key decisions from comment threads to main docs
Back to Topics