Version 2

    Moderation Best Practices:

    • Communicating and setting proper expectations of community areas.
    • Providing open two-way communication paths to the community moderation team.
    • Stand firm on your community guidelines, but allow for review in the event of an error.
    • Use your best judgment on content — look at it from the author’s viewpoint, as well as the other participants.
    • Continually assess the needs of various community areas, adapting to user’s needs.
    • Set internal expectations on different moderation scenarios and outcomes
    • Leverage as much filtering and “pre-moderation” capabilities to lower the burden on human resources.
    • Monitor, measure and categorize the different types of community conversations
    • Allow transparent employee participation
    • Use an “authentic” voice when dealing with abusers. 
    • Allow dissent and/or criticism on your site

     

    Moderation Bad Practices:

    • Positioning yourself on any one extreme of the moderation spectrum.
    • Shutting online areas down in response to excessive negative user activity, especially without posting a reason.
    • Throwing more moderation staff into an area with excessive negative user activity.
    • Anonymous participation by employees
    • Punishing criticism
    • Scrubbing everything you post by corp comms and/or legal
    • Deleting posts that conform to code of conduct, but might not sit well with executives/management
    • Losing courage at the first sign of conflict or criticism on your site

     

     

    Remember:

    • If your content/site voice is pushy and opinionated, you’ll get back pushy and opinionated responses, amplified.
    • If personal and tactful, you’ll get that back, amplified.
    • Encourage community members to complete their profile.  If they have a complete bio, avatar, etc., they will be less likely to be bad mannered.
    • Reward the best contributors and showcase them.  Let them be the shining example of what a good community citizen looks like.
    • Always be nice, even when banning content or users.  Give full reasons to why the action is being taken.

     

    Thoughts? Please feel free to add your own advice based on your experiences.
https://community.jivesoftware.com/docs/DOC-8186
community.jivesoftware.com
crawl=CC-MAIN-2018-39
101482
application/http; msgtype=response
sha1:NKFDVD2RVN6HBDRVBXFVUJO4XKNP3APQ
<urn:uuid:f8df40ba-f0d3-4031-8fee-4fe5ca1c3235>
2018-09-22T13:29:28Z
96.16.153.94
text/html
sha1:LUBASZELHP5K4FDJGDXBSEPQZIS2GTDA
<urn:uuid:2981ca81-7dda-4a3f-a90e-54d57011b7c6>
https://community.jivesoftware.com/docs/DOC-8186
response
<urn:uuid:3c6b25fc-88c3-4daa-9a91-d273c0afca14>
isPartOf: CC-MAIN-2018-39
publisher: Common Crawl
description: Wide crawl of the web for September 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-179-45-39.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/