📊 Lesson 6.2: Comments & Real-Time Co-Editing

✨ The Superpower: Many People, One Live Deck

Let's start by celebrating, because this deserves it. For decades, "working on a presentation together" meant a miserable dance: someone made a copy, emailed it, you edited it, emailed it back, they merged your changes by hand, someone else had also edited the old copy, and now there are three versions and nobody knows which is real. The dreaded pitch_final_FINAL_v3.pptx.

Google Slides deletes that entire problem. There is one deck, it lives in the cloud, and everyone works on the same one at the same time. Open a shared deck and you'll see little colored markers — your collaborators, right now, moving through the slides. Someone retypes a title and you watch the letters appear. Nobody merges anything, because nothing ever forked. The deck is always current, for everyone, instantly.

Layered on top of live editing is a quieter but equally powerful tool: comments. Comments let you have a conversation about the deck without changing the deck itself — a margin note, a question, a suggestion, a task handed to a teammate. Together, live editing and comments are why a shared Slides deck can become a whole team's working space the night before a big talk.

💬 Adding Comments on Slides & Objects

A comment is a note pinned to the deck that starts a little discussion thread. You can attach one to a whole slide or to a specific object — a text box, an image, a shape — which makes it crystal clear what you're talking about.

How to add one

• On a specific object: click the object to select it, then use the comment control — the speech-bubble-with-a-plus icon near the top-right toolbar, or right-click and choose Comment. The comment anchors to that object.
• On a slide in general: with nothing selected, add a comment the same way and it attaches to the current slide.
• Type your note and click Comment. A small marker appears; click it any time to reopen the thread.

Anyone with Commenter or Editor access can add comments and reply to yours, building a threaded conversation. Replies stack under the original, so a discussion about slide 3's headline stays neatly attached to slide 3's headline — not lost in an email chain. This is exactly why we gave reviewers Commenter access last lesson: they can talk richly about the deck without touching it.

⚠️ Important Note: Comments are a different feature from speaker notes. Speaker notes (Lesson 5.1) are your private script for delivering the talk and travel with the deck for the presenter. Comments are a collaborative conversation among the people sharing the deck, and they don't appear when you present. Don't confuse the two — notes are for you at the podium; comments are for the team building the deck.

📣 @-Mentions, Assigning & Notifications

A comment nobody sees is a comment wasted. The fix is the @-mention. Inside any comment, type @ followed by a person's name or email and pick them from the list. Three useful things happen:

• They get notified — an email (and an in-app nudge) lands, pulling their attention straight to that exact comment on that exact slide.
• If they don't yet have access, Slides offers to share the deck with them right there — a lovely shortcut that folds sharing into the conversation.
• You can turn it into an assigned task. When you @-mention someone, an option appears to Assign to that person. The comment becomes an action item with their name on it — a checkbox-style task the whole team can see is "owned."

Assigning is how a shared deck becomes a lightweight to-do board. "@Priya can you rework the pricing slide by tonight?" — assigned to Priya, visible to everyone, and marked done when she resolves it. No separate project tool needed; the tasks live right where the work is.

✅ Resolving Comments & Comment History

Comments have a life cycle, and closing them off is what keeps a deck from drowning in old notes. When a discussion is settled — the change is made, the question answered, the task done — click Resolve (the checkmark) on the thread. The comment marker disappears from the slide, keeping your working view clean and signaling to everyone "this one's handled."

Resolved doesn't mean deleted, though. Open the Comment history — the comment/clock icon near the Share button at the top — and you'll see every comment on the deck, open and resolved, with who said what and when. From there you can reopen a resolved thread if it turns out it wasn't so settled after all. Nothing is ever truly lost; it's just tidied away.

This is the natural rhythm of collaborating on a deck: a comment raises something, the team discusses it in the thread, someone acts, and the comment gets resolved. Raise → discuss → resolve, over and over, until the deck is ready. The comment history is the paper trail of every one of those little decisions.

🖱️ Real-Time Co-Editing & Avoiding Conflicts

Now the headline act. Share a deck as Editor with a few people, and all of you can build it simultaneously. Here's what you actually see and feel:

• Colored cursors. Each collaborator gets a color. As they click into a text box or move a shape, a labeled colored cursor shows exactly where they are, live.
• Presence. Avatars near the top show who's in the deck right now. You always know if you're alone or building alongside three teammates.
• Simultaneous edits. One person restyles the theme while another rewrites slide 4 and a third drops in an image on slide 7 — all at once, all saved instantly, no toes stepped on.

Why it (almost) never conflicts

The word processor / spreadsheet worry — "what if we both edit the same thing?" — barely applies here. Slides syncs keystroke by keystroke through the cloud, so edits merge continuously rather than colliding at save time. There's no "save" moment to clash on, because there's no manual save at all. The only genuinely messy case is two people typing in the exact same text box at the exact same instant — and the colored cursors make that obvious, so you naturally avoid it.

The human protocol that keeps it smooth

The technology rarely conflicts; the people occasionally do. A couple of light habits prevent the only real friction:

• Divide the slides. "You take 1-5, I'll take 6-10." Working in different areas means you never even brush against each other.
• Comment before you overwrite someone's work. If you disagree with a teammate's slide, don't silently rewrite it — drop a comment and discuss. Overwriting a colleague's work with no word is a social conflict, not a technical one, and it's the fastest way to sour a collaboration.
• Watch the cursors. If someone's colored cursor is parked in the box you're about to edit, wait a beat or ping them. Presence is there to be used.

🌙 The Night Before the Pitch — and an Honest Comparison

Picture it. It's 9 p.m. before a big pitch. Three of you are in the same deck from three different homes. Priya's colored cursor is polishing the pricing slide. You're tightening the story on slides 2-4. Sam drops a comment: "@you the opening feels slow — cut slide 3?" You reply, agree, delete it, and resolve the thread. Someone's boss, shared in as a Commenter, leaves three notes overnight that you knock out with coffee in the morning. By the time you present, the deck reflects everyone's best thinking — and there was never a single emailed copy, never a merge, never a "which version is real?" That evening is what this whole module is for, and it's genuinely delightful.

🎯 Project: Exchange Comments on Your Deck

Your deck is already shared from last lesson — now let's make it come alive. You'll bring in a collaborator (a friend, a classmate, or simply a second Google account of your own), exchange comments both ways, try an @-mention, and resolve a thread together. You'll feel the collaboration loop — raise, discuss, resolve — for real.

Two windows, two roles:

Window A  (owner account)      Window B  (collaborator account)
-----------------------        -------------------------------
1. Add comment on slide 2  ->  2. See marker, reply in thread
                               3. New comment on slide 4,
4. Get @-mention, reply    <-     @-mention the owner
5. Assign / discuss        <->  6. Discuss
7. Make the edit + Resolve  ->  (marker disappears for both)
8. Open Comment history -> the resolved thread is still on record

🧭 Best Practices for Collaborating

✅ Do's

• Anchor comments to the exact object you mean, so there's zero ambiguity about what you're discussing.
• @-mention to assign. Naming a person turns a floating wish into an owned task with a notification.
• Divide the slides up front and watch the colored cursors, so editors never collide.

❌ Don'ts

• Don't overwrite a teammate's slide silently. Comment first — it's the module's golden rule.
• Don't hoard open comments. Resolve generously; the history keeps everything and progress stays visible.
• Don't confuse comments with speaker notes. Notes are your private script; comments are the team's conversation.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've used the feature that makes Google Slides genuinely special. You added and anchored comments, @-mentioned and assigned a teammate, resolved a thread, found the comment history, and experienced a live deck with more than one person in it. You now know both the technology and the human protocol that keep collaboration smooth — which is exactly what lets a team build a great deck together the night before a pitch.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 6.3: Version History, Embedding & Linking Sheets Charts — we cover the safety net that makes all this fearless. You'll explore version history (named versions, restoring, seeing who changed what), learn to make a copy and embed a deck in a website or Doc, and pull off the Workspace-glue trick: linking a live chart from Google Sheets into a slide that updates when the data changes. It's how the whole Google Workspace ties together.

✅ Before the Next Lesson

• Make sure your running deck has at least one comment thread on it (resolved or open) to explore next lesson
• If you have a Google Sheets file with a simple chart, keep it handy — you'll link it into a slide
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Add comments & assign tasks in Google files (Google Support)
• Share files & collaborate in Google Drive (Google Support)
• slides.google.com — open the app