The Workplace is naturally attractive to soft questions, and soft questions, more often than not, attract a lot of answers. That's good, but after a point answers start becoming horribly repetitive, adding very little, if anything, to the discussion. It's a problem we've identified before, on various Meta discussions:
- FAQ proposal: Back It Up and Don't Repeat Others
- Does this site need a "back it up" rule?
- Do we need a policy on bad/"me too" answers?
- What can we do about me-too answers?
- What can we do about one line answers?
- How do we define Constructive on this site?
Our current Area 51 stats shows that we have 3.8 answers per question, which I think is a very healthy ratio, but we shouldn't let it raise a lot. Programmers (then NPR), had 7.0 answers per question at the end of beta, and although the stats label the ratio as "excellent", it's not, it was one of the warning signs that the site was turning into a forum. And we all know what happened to NPR (for those who don't, NPR is no more).
One good way to keep our answers per question ratio reasonable, I think, would be to lower the Community Wiki automatic conversion threshold to 10 answers. Right now, the threshold is 30 answers, the default for all Stack Exchange sites, and some sites have opted for a lower threshold, Programmers and Super User are at 15. The goal of reducing the threshold is obvious, remove the reputation incentive to post yet another answer at a point were it's extremely unlikely that the question hasn't been sufficiently answered. Of course, if you really want to answer the question, you still can, the only difference being that you don't get any reputation. You'll still earn badges though ;)
In the Meta discussions I've linked to, and various other discussions in chat it has been argued that answers can sometimes play a deciding role on closing a borderline "not constructive" question. If a question is borderline to begin with (and most of our questions are), getting a ton of repetitive answers will most certainly lead to closure, curating and safeguarding an extremely popular question with 15+ answers is an extremely tedious job. Lowering the Community Wiki threshold will possibly be an easy way to avoid all these "me too" / one line answers.
These questions would have been wikified if we had a 10 answer threshold from the beginning. Notice that I'm searching for questions with 11 answers, a 10 answer threshold means that the eleventh answer triggers wikification. 6 questions out of a current total of 306, this is mostly a proactive measure for bike-shed questions than something that would massively affect the site.