A rule that two moderators would apply differently isn't finished yet, so this lesson is about making guidelines specific enough to act on.
  • 😲 2
  • 671

The tea break turned out to be the most useful part of the day. Several moderators said it was the first time they had talked about burnout out loud. That's why looking after your team gets a module of its own.

  • 1
  • 634

Second exercise of the day: one person plays an angry member, the other gets three messages to calm things down. Harder than it sounds, and lots of laughing once the timer ran out.

  • 663

From the in-person session for Moderation Essentials. Each table got a stack of anonymised reports and twenty minutes to sort them into act now, act later and leave alone.

  • 620

The one hard rule at the heart of module 2: nobody makes a ban decision alone. Two moderators read the member's history, agree on the outcome, and only then act.

  • 😲 1
  • 666
What to record after each moderation action, and why a shared log stops your team repeating mistakes.
  • 😲 1
  • 616
Practical moves for cooling down an argument without locking the thread or picking a side.
  • 610
A ladder of consequences that keeps decisions consistent and leaves room for people to come back.
  • 602

Opening image for the reports module of Moderation Essentials. The rule we borrowed from Moderators HQ: every report gets an acknowledgement, a decision and a note in the log, even when the decision is to do nothing.

  • 658
How to word a warning so that most members change the behaviour instead of digging in.
  • 670
A simple order of operations for clearing reports quickly without missing the ones that matter.
  • 613