Lesson 6.2: Comments & Real-Time Co-Authoring

Feedback Without Overwriting

Imagine you've shared your deck with a colleague for feedback. They open it, disagree with your third slide, and — trying to be helpful — simply rewrite it. Your careful wording is gone, replaced by theirs, with no note explaining why. You now have to reconstruct what you had, guess what they meant, and have the conversation you should have had in the first place. That's not collaboration; it's a quiet act of erasure, and it's the single most common way shared decks go wrong.

There's a better model, and it rests on one principle: separate saying "I think this should change" from actually changing it. A comment is a note attached to a slide or an object that says "here's my thought" without touching the content. The author reads it, decides, and makes the change (or doesn't). Nothing is lost, the reasoning is visible, and disagreements become a conversation instead of a silent overwrite war. This is why, in a healthy shared deck, reviewers comment and authors edit — a division of labor that keeps everyone's contributions intact.

That's the whole philosophy of this lesson. PowerPoint gives you two collaboration tools — comments for feedback and real-time co-authoring for building together — and both work best when you treat someone else's slides with the same care you'd want for your own. The features are easy. The habit of suggesting before replacing is what makes a team's deck better instead of just more edited.

🧠 Mindset

A shared deck is a shared space, like a kitchen you cook in with others. You can be enormously helpful or quietly infuriating depending on whether you clean up after yourself and ask before rearranging someone else's ingredients. Comments are how you say "have you considered…" without grabbing the knife out of someone's hand. Lead with them, and people will actually want to collaborate with you.

Comments: New, Reply, Resolve

A comment in PowerPoint is a small note pinned to a slide — or to a specific object on it, like a title or an image. It lives with the deck, so the feedback and the thing it's about never drift apart. Here's the full lifecycle.

Adding a comment

Select the slide (or click the specific object you're commenting on) and choose Review > New Comment, or click the Comments button in the top-right to open the comments pane and add one there. Type your note and post it. A little comment marker appears on the slide, and your note joins the pane on the right. Because the comment is anchored to the slide or object, anyone opening the deck sees exactly what you were reacting to — no more "on the slide with the blue chart, third bullet…" guesswork.

Replying — a comment is a thread

Comments aren't one-shot notes; they're threads. Anyone with access can Reply beneath a comment, so a single question can hold a whole back-and-forth: "Should this number be Q2 or Q3?" → "Q3, updated." → "Perfect." Keeping the discussion inside the thread — rather than scattering it across email and chat — means the reasoning stays attached to the slide forever, which is a gift to anyone who revisits the deck later and wonders why a choice was made.

Resolving — closing the loop

When a comment has been dealt with, mark it Resolved (the checkmark on the comment). Resolving doesn't delete the thread — it tucks it away as "handled," so the comments pane shows only what still needs attention. This is the discipline that keeps a busy deck sane: a pane full of open comments is a to-do list, and resolving them one by one is how a review actually reaches "done." You can reopen or delete a resolved comment later if you need to; resolve is a status, not a shredder.

Action	Where	What it does
New Comment	`Review > New Comment` or the Comments pane	Pins a note to the current slide or selected object
Reply	Under an existing comment	Continues the thread — keeps the discussion in one place
Resolve	The checkmark on a comment	Marks it handled and hides it from the active list
Delete	Comment menu	Removes the thread entirely — use sparingly

graph LR A["✍️ New Comment
on a slide or object"] --> B["💬 Reply
discuss in the thread"] B --> C{"Handled?"} C -->|"Not yet"| B C -->|"Yes"| D["✅ Resolve
tucked away as done"] D -.->|"Needed again?"| A

Notice the loop: a comment opens, gets discussed, and closes when resolved — and can reopen if the issue comes back. A well-run review is just this cycle repeated until the pane is empty. When you see zero open comments, the feedback round is genuinely finished, and everyone can see that at a glance.

💡 Where comments live

Comments travel with the deck, whether it's opened on the web, the desktop app, or mobile — and they sync in real time when the deck is on OneDrive. The core New / Reply / Resolve flow is available on the free web app, which is where most of your reviewing will happen. Comment on a slide from your phone on the bus and your teammate sees it on their laptop moments later.

@Mentions — Assigning Feedback

A comment left in the open is a message in a bottle — it might be read, eventually, by someone. An @mention turns it into a direct message with a name on it. Type @ in a comment, start typing a person's name, and pick them from the list. Their name becomes a link in the comment, and — this is the powerful part — they get notified by email (and in Teams, if your organization uses it) that they've been mentioned, with a link straight to that comment.

This does two jobs at once. It directs the feedback — "@Priya, can you confirm this Q3 figure?" leaves no doubt about who needs to act — and on Microsoft 365 it can assign the comment as a task to that person, so it shows up as something they own rather than a note anyone might or might not pick up. Accountability, built into the feedback itself. No more "I thought you were handling the intro slide."

⚠️ @Mentions reach real inboxes

An @mention sends a real notification to a real person. That's the feature working as designed — but it means the person must already have access to the deck (you shared it with them in Lesson 6.1), and it means you shouldn't @mention someone casually into a deck full of sensitive content they weren't meant to see. Mentioning can even prompt PowerPoint to offer sharing the deck with them if they don't have access yet. Mention deliberately: you're pulling someone into the deck, not just tagging a name.

A small habit makes @mentions genuinely effective: write the comment as a clear request, not a vague gripe. "@Sam this feels off" gives Sam nothing to act on. "@Sam the title overlaps the logo on slide 4 — can you nudge it down?" is a task Sam can finish in thirty seconds and resolve. Specific, named, actionable — that's the trio that turns comments from noise into progress.

✅ Pro Tip

When you're the author receiving @mentions, resolve them as you address them — it's the courteous "done" signal that tells the mentioner they can stop worrying about it. And if a mentioned change sparks a real disagreement, reply in the thread rather than silently ignoring or overwriting; the whole point of comments is that decisions stay visible and discussable.

Real-Time Co-Authoring

Comments are for feedback. Co-authoring is for building together — two, three, or more people editing the same deck at the same time, each seeing the others' work appear live. It is genuinely a little magical the first time you watch a teammate's edits ripple onto your screen, and it's the capability that most closed the gap between PowerPoint and the tool that made it famous, Google Slides.

How it works

The prerequisite is the one from last lesson: the deck lives on OneDrive and you've shared it with edit access. When two people open it, PowerPoint shows:

Presence indicators — small colored avatars or initials, usually top-right, showing exactly who else is in the deck right now.
Live cursors and selection flags — a colored marker showing where each person is working and which slide or object they have selected, so you can see, in the moment, that a teammate is editing slide 5 while you're on slide 2.
Changes streaming in — edits appear as they happen (near-instant on the web and modern 365; the desktop app may sync in small bursts as people save).

Because everyone edits one deck on OneDrive, there are no copies to reconcile and no "final_v3" to chase. The version you see is the version everyone sees. Autosave and version history (Lesson 6.3) run underneath the whole time, so even a chaotic co-editing session can always be rolled back if something goes sideways.

You'll see…	What it tells you
Avatars / initials (top-right)	Who else is in the deck right now
A colored flag on a slide	Someone is working on that slide or object
Text or shapes changing on their own	A collaborator's live edits arriving
An "updates available" prompt (desktop)	Save/refresh to sync everyone's latest changes

💡 Web vs desktop, honestly

Co-authoring is smoothest and most instantaneous on PowerPoint for the web and current Microsoft 365, where changes and cursors update continuously. Older desktop versions still co-author, but they may sync in bursts around saves rather than keystroke-by-keystroke, and you might see an "updates available" nudge. If real-time smoothness matters most, the web app is your friend — another case where the free, browser-based PowerPoint quietly holds its own.

Collaboration Etiquette

The tools are the easy half. The habits that keep a shared deck pleasant — and prevent the awkward moment when two people rewrite the same slide in opposite directions — are the half worth internalizing. None of this is enforced by software; it's simply how considerate collaborators behave.

Comment, don't overwrite

The golden rule from the top of this lesson, restated because it matters most: if it's someone else's slide and you're not certain, leave a comment rather than silently rewriting it. Correcting an obvious typo on the fly is fine and welcome; reworking a colleague's argument without a word is not. When in doubt, suggest. The author will thank you for the note far more than for the surprise edit.

Divide the deck by section

Two people editing the same slide at the same time is where co-authoring gets bumpy — cursors collide, and one person's change can land on top of another's. The clean fix is coordination: agree who owns which slides or sections before you dive in. "You take slides 1–5, I'll take 6–10" almost entirely eliminates collisions. The Sections feature you met earlier in the course is perfect for this — carve the deck into named sections and assign them, and everyone has their own lane.

Announce, resolve, and tidy

Say hello. A quick "I'm jumping into the deck now" in chat means nobody is startled by things moving on their screen.
Resolve what you finish. Close the comments you've handled so the open list stays meaningful.
Don't hoard edit access. If someone only needed to review, drop them back to Can view (or Can review, where your plan offers it) when they're done (Lesson 6.1). Fewer editors, fewer surprises.

⚠️ Watch Out

Two people on one slide, one deleting a text box while the other types into it, is the classic co-authoring collision. It rarely destroys anything permanently — version history has your back — but it's disorienting and wastes effort. The cure is social, not technical: divide the work and talk to each other. A thirty-second "who's taking what?" saves a frustrating tangle.

PowerPoint vs Google Slides — Honestly

It would be dishonest to teach PowerPoint collaboration without naming the tool that defined it. Google Slides made real-time co-editing feel effortless years before PowerPoint matched it — born in the browser, cloud-first, with live cursors and comments that "just worked" from day one. For a long stretch, if seamless simultaneous editing was your top priority, Slides was the honest answer.

That gap has largely closed. Through the web app and Microsoft 365 on OneDrive, PowerPoint now offers a co-authoring experience that is, feature for feature, very close: live presence, cursors, comments with @mentions, resolve — nearly the same shape, often nearly the same words. The honest, current picture:

What you care about	Microsoft PowerPoint	Google Slides
Real-time co-editing	Strong now via web / 365 & OneDrive	Best in class — effortless, the original
Comments & @mentions	Yes — New / Reply / Resolve, assign via mention	Yes — the same shape ("Commenter" role)
Cost to collaborate	Free web app works; deepest features on 365	Free with a Google account
Smoothest on…	The web app / modern 365	Any browser — it's all browser
Design depth alongside collaboration	Deeper — Morph, richer design, then co-edit it	Lighter design, superb collaboration

The fair summary: Slides pioneered effortless collaboration and is still the benchmark for frictionless co-editing; PowerPoint has caught up and now does it well — while keeping the deeper design toolkit that's this course's whole reason for being. You get to co-author a genuinely well-designed deck, not just a co-authored one. And because the concepts and even the vocabulary overlap so heavily, learning to collaborate in one makes you instantly capable in the other.

💡 Your skills transfer either way

Comment, reply, resolve, @mention, live cursors, dividing work by section — every one of these exists in both tools with nearly identical names and behavior. Whichever your team lands on, the collaboration habits you're building here travel with you. You are never learning a dead end.

🎯 Project: Comment & @Mention

Now you'll run the full feedback loop yourself. The ideal version involves a friend or colleague, but you can complete every step solo — @mention yourself, and even open the deck in a second window to watch live co-authoring in action. The goal is to feel the comment lifecycle and, if you can, see a live cursor that isn't yours.

🏋️ Leave a comment, @mention, and resolve

Objective: Run a comment through its whole life — created, directed at a person, replied to, and resolved — and, if possible, experience real-time co-authoring.

Instructions (about 15 minutes):

(2 min) Open your deck (on OneDrive from Lesson 6.1). If a partner is joining, make sure they have more than Can view — viewers can't comment. Pick a slide you have a real question about — a figure to confirm, a title to reconsider.
(3 min) Select the slide or the specific object and choose Review > New Comment. Write a clear, actionable comment — a request, not a vague gripe.
(3 min) In the comment, type @ and mention someone with access — a collaborator, or yourself if you're working solo. Notice how the name becomes a link and triggers a notification.
(3 min) Reply to your own comment as if answering the question ("Confirmed — updated to Q3"). See how the thread holds the whole exchange.
(2 min) Mark the comment Resolved. Watch it leave the active list. Reopen it once to prove resolving doesn't destroy it.
(2 min) Bonus — live co-authoring: open the same deck in a second browser window (or have a friend open it with edit access) and edit a slide. Watch the presence avatar and live cursor appear, and the change arrive on the other screen.

💡 Hint — anatomy of a good comment

A weak comment:
  "this slide is off"          <-- vague, no owner, no action

A strong comment:
  "@Jordan the Q3 revenue here reads $42k but the
   Excel source says $48k -- can you confirm which
   is right and update? Thanks!"

Why it works:
  - @mention  -> a named owner who gets notified
  - specific  -> exactly what and where
  - a request -> something Jordan can finish and resolve

Then: Jordan replies "Fixed -- it's $48k", you Resolve. Done.

If you're solo, @mention yourself and play both roles. The muscle memory of write → mention → reply → resolve is exactly the same, and it's what you'll use on every real team deck.

✅ Project Completion Checklist

You added a clear, actionable comment to a specific slide or object
You used an @mention to direct it at a person (yourself is fine)
You replied within the thread to continue the discussion
You marked the comment Resolved and saw it leave the active list
Bonus: you saw a live cursor or presence indicator from a second editor

🎯 Quick Quiz

Question 1: A teammate disagrees with your slide's wording. What's the respectful, collaboration-friendly move?

Question 2: What does adding an @mention to a comment do?

Question 3: What's the best way to avoid collisions when several people co-author one deck live?

Best Practices for Collaborating

✅ Do's

Comment before you change someone else's slide. Suggesting keeps their work intact and the decision theirs.
Write specific, actionable comments and @mention the owner. A named request gets done; a vague note gets ignored.
Divide the deck by section for live co-editing. Everyone in their own lane means no collisions.

❌ Don'ts

Don't silently overwrite a colleague's content. It erases their work and the reasoning behind it — the number-one way shared decks go wrong.
Don't let resolved and open comments pile up unmanaged. Resolve what you finish so the open list stays a real to-do list.
Don't @mention someone into a deck they shouldn't see. A mention pulls a real person toward real content — mention deliberately.

💡 Pro Tips

Start a co-editing session with a quick "who's taking what?" — thirty seconds of coordination saves a tangle of collisions.
As the author, resolve @mentions as you address them; it's the courteous "done" that tells the mentioner they can relax.

📓 Learning Journal

Keep a learning journal as you work through this course — a separate document, a note, or even a slide at the end of the deck you're building. After each lesson, take a few minutes to write down:

Key concepts you learned
Techniques that clicked for you
Questions or confusion points to revisit
Ideas you want to try in your own decks
Your progress and feelings about learning this — including where your confidence grew

✍️ This lesson's prompt: Recall a time you gave or received feedback on shared work — a deck, a document, a project. Did it feel like collaboration or like being overwritten? How might comments and @mentions have changed that experience? Then write one etiquette rule from this lesson you want to hold yourself to the next time you're editing someone else's deck.

📝 Lesson Summary

🎓 Key Takeaways

Comment, don't overwrite. A comment says "I think this should change" without touching the content, keeping everyone's work intact and the reasoning visible — the core etiquette of shared decks.
Comments have a lifecycle: Review > New Comment pins a note to a slide or object, Reply keeps the discussion in one thread, and Resolve closes the loop while keeping the record.
@mentions direct and assign feedback: typing @ notifies a specific person and, on 365, assigns the comment to them — turning a note into an accountable task. Write specific, actionable requests.
Real-time co-authoring lets multiple people edit one OneDrive deck live, with presence avatars and colored cursors showing who's where. Smoothest on the web and modern 365; divide the deck by section to avoid collisions.
Honest comparison: Google Slides pioneered effortless collaboration and remains the benchmark for frictionless co-editing; PowerPoint has caught up and now does it well — while keeping deeper design. The concepts transfer both ways.

🎉 What You've Accomplished

Your deck can now be reviewed and built by a team, and — just as importantly — you know how to do that graciously. You can pin feedback exactly where it belongs, direct it at the right person, run a review to a clean "zero open comments" finish, and co-edit live without stepping on anyone. Those are the habits that make people want you on their deck.

❓ Common Questions at This Stage

Can I add comments on the free PowerPoint for the web?

Yes. The core comment flow — New Comment, Reply, Resolve, and @mentions — works on the free web app when your deck is on OneDrive. It's exactly where most reviewing happens, and it syncs in real time to everyone else in the deck. A few advanced review touches vary by version, but the essentials are all there for free.

If two of us edit the same slide at once, will we break something?

Almost never permanently. Co-authoring is designed to merge changes, and version history (next lesson) can undo a bad moment. But two cursors on one slide is disorienting and wasteful, so the real fix is social: divide the deck by section and agree who owns what before you start. Coordination beats collision.

What's the difference between a comment and just editing the slide?

Editing changes the content directly; a comment suggests a change without touching it. Editing is right when you're a co-author building the deck and the change is clearly yours to make (or a plain typo fix). A comment is right when it's someone else's slide, when the change is a matter of opinion, or when you want the decision discussed and visible rather than silently applied.

🔭 Looking Ahead

In the next lesson — Lesson 6.3: Version History, Linking Excel Charts & Embedding — we add the safety net that makes all this collaboration fearless. You'll browse and restore earlier versions of your deck (and name the important ones), paste-link a live Excel chart so it updates when the data changes — a concrete PowerPoint-plus-Excel win — and learn to embed and export your deck for the wider world.

✅ Before the Next Lesson

Confirm you can add, reply to, @mention within, and resolve a comment on your deck
If you have a simple Excel chart or some data handy, keep it nearby — you'll link it next lesson
Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

Great collaborators aren't the ones with the fanciest features — they're the ones who make everyone else's work better without stepping on it. You now have both the tools and the manners to be that person on any deck. Comment kindly, build together, and enjoy watching a shared deck become more than any one of you could make alone. 📽️

📽️ Lesson 6.2: Comments & Real-Time Co-Authoring

📚 What You'll Learn