Skip to content

Commit 32bbf9a

Browse files
committed
I dug up this guide that still has a lot of helpful tips.
1 parent 0704528 commit 32bbf9a

File tree

1 file changed

+110
-0
lines changed

1 file changed

+110
-0
lines changed
Lines changed: 110 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,110 @@
1+
---
2+
layout: post
3+
title: Thanks for the diamond. Now what?
4+
tags: stack_overflow moderation
5+
---
6+
7+
Below is a guide I wrote for new employees at Stack Overflow to help
8+
them avoid having a bad time moderating the sites. This is an early
9+
draft so it might not reflect what Stack Overflow uses internally
10+
now. The principles, however, remain relevant for each new
11+
organization I have been a part of.
12+
13+
---
14+
15+
## How to use your new superpowers.
16+
17+
When community managers, developers, and other employees need
18+
"administrative access" to one of our sites, we give them similar
19+
privileges as moderators chosen from within the community. The diamond
20+
♦ that appears next to your activity can sometimes generate a bit of
21+
apprehension about your role in the site. Whether you are speaking in
22+
an official capacity or are simply participating as "just another
23+
user", it is helps to remember that your words and activities carry a
24+
little more weight… and will likely be more scrutinized than the
25+
average user's. The tips below are designed to avoid the appearance of
26+
omnipotence and those sticky situations where a conflict of interest
27+
is perceived.
28+
29+
* **Remember that users will assume what you say is "Official Policy”**
30+
31+
We all have opinions to share and "default public" generally means
32+
we should be part of the conversation. But users will treat what you
33+
say as canon. So, when you are delving into controversial issues
34+
that either have not been decided, or where your view may diverge
35+
from any actual official guidance: **Try to make it clear that you
36+
are simply sharing an opinion that is not the "official” word on the
37+
topic.** You don't need to plaster a disclaimer on your posts, but
38+
make sure that you are not (unintentionally) ending the conversation
39+
with the final verdict of policy where there is none. You will be
40+
quoted as policy. Often.
41+
42+
* **Get Backup, and never moderate your own activity.**
43+
44+
Or anyone coming anywhere near it. A good rule of thumb: When users
45+
disagree with you, avoid doing anything a regular user cannot
46+
do. Avoid closing their posts. Don't flag (delete) comments that do
47+
not agree with you. If you genuinely feel moderator intervention is
48+
needed, call on someone else to look into the situation. Generally
49+
speaking, take it to the the community team chat room. We're happy
50+
to mediate sticky situations. Assuming the person agrees with you,
51+
they'll solve the problem without the appearance of "censorship” or
52+
"abuse of power”. Once someone starts shouting those words,
53+
everything else gets harder.
54+
55+
* **When you're not making progress with someone, you're probably
56+
making things to argue with.**
57+
58+
If you find you've had two back-and-forths in the comments with no
59+
movement toward the middle, you can probably give up on convincing
60+
this particular person. Which means that more comments probably just
61+
make the whole interaction (about their presumably wrong-minded
62+
point) more visible to others. Leave `em with the last word, and
63+
move on.
64+
65+
66+
* **Don't take it personally.**
67+
68+
Joel says in his [Seven steps to remarkable customer
69+
service](https://www.joelonsoftware.com/2007/02/19/seven-steps-to-remarkable-customer-service/)
70+
"There is only one way to survive angry customers emotionally: you
71+
have to realize that they're not angry at you; they're angry at your
72+
business, and you just happen to be a convenient representative of
73+
that business." Most of the time, users are not yelling at you;
74+
they're lashing out about the situation. Don't yell back. You will
75+
also be yelling at the people listening in over their shoulders.
76+
77+
* **Agree with anything you possibly can, and don't be afraid to
78+
apologize.**
79+
80+
Whenever possible, lead with something the other person can agree
81+
with:
82+
83+
> You raise a great point about the need to deal with all these
84+
> giant hamsters - they make me crazy. But I'm not sure that your
85+
>'Napalm Catapult' plan is the best approach because…
86+
87+
Someone else feeling bad is usually a good enough reason to say "I'm
88+
sorry,” even if you haven't done anything wrong.
89+
90+
> Sincere apologies - it truly wasn't my intent to imply that. I
91+
> should have been clearer that I agreed with your approach, but
92+
> thought that the implementation would cause other problems….
93+
94+
And, of course if you did slip up, apologizing is just the right
95+
thing to do. It bears repeating: **Failing to apologize when you are
96+
in the wrong causes much more damage than taking blame when you did
97+
nothing wrong!**
98+
99+
## Key powers employee moderators have:
100+
101+
* Close, delete, and reopen votes are unilateral and instant (you need
102+
to be really comfortable playing Judge Dredd here).
103+
* Flagging a comment deletes it.
104+
* You have the power to edit any comment at any time.
105+
* Deleted comments can be shown and undeleted.
106+
* All user profiles are editable.
107+
* Reviews, tag synonyms, and tag wiki edits are unilateral.
108+
* Every site becomes a possible migration target.
109+
* You can create private chat rooms and see deleted chat items.
110+
* All privileges are granted without the need to earn them.

0 commit comments

Comments
 (0)