📋 Lesson 7.2: Real-Time Collaboration: Comments, @Mentions & Notifications

Comments: Talk on the Card

Every card has a comment box at the bottom of its activity feed. It looks humble, but it's the single most important collaboration feature in Trello, and the reason is simple: the conversation lives next to the work. When you discuss a task in Slack or email, that discussion drifts away — three weeks later nobody can find why you chose the blue banner over the red one. When you discuss it in a card comment, the decision is welded to the card forever.

Here's what a card conversation looks like — this is the launch email card from your team board:

Comments support the same light Markdown-ish formatting you learned for descriptions in Lesson 2.1 — bold, italics, lists, links, and inline code. You can edit or delete your own comments, and every comment is time-stamped in the activity feed so the history is honest and complete.

@Mentions: Notify the Right Person

A comment nobody sees is a note in a bottle. To make sure the right person actually reads it, type @ followed by their name. Trello pops up a picker of people on the board; choose one and they get a direct notification — a bell badge, and (depending on their settings) an email, desktop, or mobile push. The mention also highlights their name in the comment so it's visually obvious who's being addressed.

• @username — notifies one specific person. This is your everyday move: "@priya can you approve this?"
• @board — notifies everyone who is a member of the board. Use sparingly; it's the Trello equivalent of "@here" and can annoy a big team if overused.
• @card — notifies everyone assigned to (a member of) that specific card. A polite way to nudge just the people responsible without pinging the whole board.

Here's a lovely efficiency: you can @mention someone and ask a question in a single comment, and because the whole exchange stays on the card, a stakeholder who reads it later gets the full context for free — no forwarding, no "let me catch you up."

Reactions & Keeping Discussion Focused

Not every comment needs a reply. Trello lets you add emoji reactions to a comment — a 👍 to acknowledge, a 🎉 to celebrate, a 👀 to say "I'm on it." Reactions are the low-friction way to close a loop without adding noise: instead of five people each commenting "sounds good," they each tap 👍 and the thread stays clean.

Reactions do real collaboration work:

• Acknowledge without cluttering — a 👍 says "seen and agreed" without another comment.
• Lightweight voting — reactions on a "which option?" comment reveal team preference at a glance.
• Signal status — a 👀 ("looking into it") or ✅ ("done") communicates instantly.

The Notification Inbox & Bell

All those @mentions, replies, due-date reminders, and card assignments land in one place: the notification bell (🔔) in the top-right of Trello. A red badge tells you something's waiting; click it to see your notification inbox, mark items read, and jump straight to the card in question. This is your personal "what needs me?" feed across every board you're on.

Notifications reach you through several channels, and you control each:

• In-app bell — always on; your central inbox.
• Email — configurable frequency (instantly, periodically, or never) in your account notification settings.
• Desktop — browser or desktop-app push while you're working.
• Mobile — push notifications from the Trello app, great for time-sensitive @mentions on the go.

Watching Cards, Lists & Boards

Sometimes you care about a card you're not a member of — a task another team owns that blocks yours, a decision you want to track. Watching is how you stay informed without taking ownership. Open a card and click Watch (you'll see a little 👁️ eye badge), and from then on every comment, move, and change on that card lands in your notifications.

You can watch at three levels:

• A card — follow one specific task's every update.
• A list — get notified about activity across a whole column (e.g. watch the "Blocked" list so you hear the moment something gets stuck).
• A board — track everything happening on a board; useful for a manager keeping a light eye on a project.

Team Conventions & Accountability

Tools don't make teams collaborate well — agreements do. A handful of shared conventions turn a board from a place where things get lost into a place where everyone trusts the information. Here are the ones worth agreeing on early:

• Where decisions live. "If it's decided, it's a comment on the card." No decision counts until it's written on the relevant card, so there's always a single source of truth.
• A definition of done. Agree what "Done" actually means — reviewed? shipped? invoiced? — so moving a card to Done means the same thing to everyone.
• Response expectations. An @mention is a request; agree how fast people should acknowledge one (even just a 👀 reaction) so nobody's left wondering if they were heard.
• Assign, don't assume. Every active card should have a member. An unassigned card in "In Progress" is nobody's job, which means it's stalled.

The activity feed on each card and board is your accountability record. It's not for surveillance — it's so that "who changed this and why?" always has an answer, which paradoxically makes a team more relaxed, because nothing feels mysterious or blame-worthy. Everything is simply visible.

🎯 Project: Run a Collaboration Loop

The best way to internalize this rhythm is to do it once, end to end. You'll run a complete comment → mention → reply → react → resolve loop on a single card. If you don't have a teammate handy, use a second account or a test email you invited in Lesson 7.1 — or simply play both parts yourself; the muscle memory is the same.

Card: "Publish the June newsletter"

You:      @sam the draft's ready — approve the
          subject line by Thursday?           [comment + @mention]
Sam:      🔔 opens notification → reads card
Sam:      Approved. Ship it 🚀                 [reply]
You:      react 👍 to Sam's approval            [reaction — loop closed]
You:      drag card To Do → Scheduled          [resolve — progress made]

Best Practices for Collaborating

✅ Do's

• Keep work discussion on the card. Decisions and feedback belong where the work is, not in a chat that scrolls away.
• @mention specifically. Name the one person who needs to act; reserve @board for genuinely board-wide news.
• Use reactions to close loops. A 👍 beats a fifth "sounds good" comment.
• Let Butler auto-notify for predictable handoffs so nothing depends on memory.

❌ Don'ts

• Don't @mention people who aren't on the board. They won't be notified, and you'll wrongly assume they saw it.
• Don't overuse @board. A team pinged for everything soon ignores the bell entirely.
• Don't watch every busy board. You'll flood your inbox and start tuning out the notifications that actually matter.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You now know how a team actually works together on a Trello board without the usual chaos — where conversation goes, how to reach the right person, how to stay informed without drowning, and the small agreements that keep everything trustworthy. This is the difference between a board that's technically shared and a board that a team genuinely runs on.

❓ Common Questions at This Stage

🔭 Looking Ahead

You've mastered people and conversation. Next we tackle reuse: turning boards, lists, and cards into templates so your team never rebuilds the same setup from scratch — and so every new project starts already organized, decisions and conventions baked right in.

✅ Before the Next Lesson

• Have a board with at least one real (or test) collaborator on it
• Notice one board or process you set up recently that you'd hate to rebuild by hand
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Trello Guide — collaborating on boards
• Atlassian Support — comments, mentions & notifications
• Trello Butler — automate notifications and handoffs