If you are able to understand Shog's graph you will notice that NAAs handled by the moderators are twice as much as those handled by "community", which considering that the community is more strict handling NAAs (there's a stat saying that community tend to reject more flags on the low quality review queue than moderators, can't find it) it doesn't make sense that the "exception handlers" handle something so mundane like NAA flags where the community could, arguably, do this job.

Taking into account the above, I think we are incurring an opportunity cost by not allowing the community to handle more flags (since there are many more users than moderators, moderators' time is more valuable). But for that we need the data to identify if this hypothesis holds any water or if there is something else at play.

For that I would need the following:

  • Number of NAA/VLQ flags on answers that had to be elevated to the moderator queue (not being handled on the LQRQ), the reason was:
    • The answer was score >0
    • The answer was accepted
    • The timeout was reached (one hour after the flag is raised, it moves to the moderator queue)
      • What was the LQRQ leaning towards, and it agreed with the action taken by the moderator?
  • Break down of number of flags handled by the LQRQ in 5 minute brackets and its outcome. (I think average, std and median should be given as general measure too)

That would help us to identify whenever the LQRQ needs tuning and what exactly needs to be tuned.

share
5  
As a moderator, it's very easy to observe that the Low Quality Posts review queue is unable to handle the volume of "very low quality" and "not an answer" flags that come in at present. If moderators do not handle a significant volume of these, that queue backs up immediately. I've seen this happen again and again with the ebb and flow of the size of the overall moderator flag queue. I've made a couple of proposals related to this, one of which has been partially implemented. – Brad Larson 20 hours ago
1  
Bunch of tangentially-relevant stuff here: meta.stackoverflow.com/questions/340866/… – Shog9 20 hours ago
2  
For analysis, I'd split "not an answer" flags apart from the "very low quality" ones, because as you can see from those stats these are handled differently (67.6% moderator handled for the former, 32.1% for the latter). While it would be great for the community to handle more of the "not an answer" flags, the vast majority are trivial to process by moderators. When 90+% percent of them are on obvious gibberish or follow-on questions, they're easy to handle. The narrow scope of the flag makes these easier to process, as compared to the fuzzy nature of VLQ, which I tend to avoid handling. – Brad Larson 19 hours ago
7  
@BradLarson from my point of view, a moderator handling NAA's is a waste of time, basically because community can (and should) be able to handle those on their own. Even if you handle 10k NAA's flag vs sussing out a voting ring, the later is a more productive use of your time, since no one but a moderator can do it. – Braiam 19 hours ago
1  
@Braiam - I agree that eventually the tooling should move to a stage where the community handles everything but a handful of tasks, and talked about a long-term vision for that here, but in the short term I'd look at dealing with "very low quality" and "not an answer" flags in different ways. They are handled differently, and I'd put more effort into figuring out how the community could handle the remaining 32.1% of the "very low quality" flags in a sustainable way, instead of how it could take on more "not an answer" flags right now. – Brad Larson 19 hours ago
2  
@BradLarson All you need to do to have the community handle them is stop having the moderators spending so much time on it. The community handles them just fine, but lots of mods spend lots of time handling flags like this when they're only a few minutes old. No new tooling is needed; the mods just need to ignore these flags. (And if they can't, then the only tooling change would be to not show these flags to mods.) – Servy 19 hours ago
    
@Servy the thing is that they can't ignore it... once it's on their queues, it's out our queues, and all bets are off. – Braiam 19 hours ago
4  
@Braiam That's actually not correct. While the mods don't get the flag for 60 minutes, once they see it in their dashboard, it can also exist in the review queue. – bluefeet 18 hours ago
1  
@Servy - I'd love for all "very low quality" flags to be hidden from moderators completely, but community review is currently unable to keep pace with the rate of items coming into this review queue. Changes would first need to be made to offset the increased volume and make this more sustainable. There are roughly three times as many "not an answer" flags coming in, and moderators handle many more of those, so a more radical rethinking of the process would be needed for the community to handle these as well. – Brad Larson 18 hours ago
4  
@Servy The mods don't see NAA/VLQ flags on most posts for 60 minutes, there is a delay in the process for the queue to handle it. The problem is that the queue doesn't process them fast enough which leads them to be handled by the mods. – bluefeet 18 hours ago
    
@bluefeet well, I was always working on the assumption that they are on one or the other. – Braiam 18 hours ago
6  
@Servy: did you read the first comment Brad posted? Us moderators have left the NAA and VLQ queues be often enough, only to see it spiral out of control. So no, the community is not handling them just fine. Also, it is not 'lots' of mods spending 'lots' of time on these flags. On a good day, I handle maybe 100 - 150, but only because I process hundreds of flags in general, every day. There is only one other moderator that processes flags in that kind of volume. Clearing out some NAAs is a nice distraction from the drudgery of other flag types, I certainly don't see it as a waste of time. – Martijn Pieters 18 hours ago
4  
@Braiam I'm trying to pull the numbers on this, but from my experience these items tend to linger in the review queue for days before being handled. That's not necessarily happening right now because the flag queue is under control, but when the flag queue hovers near 2k we've had NAA/VLQ flags stick around for days and the community hasn't handled them. – bluefeet 18 hours ago
3  
To add to what Brad, Martijn and bluefeet have already stated... One need only look back a few months to find numerous "why aren't my flags being handled?" questions as a counterpoint to the recent spat of "why are my flags being declined?" - when posts, especially difficult/borderline posts languish in a queue, that doesn't really solve anything. – Shog9 13 hours ago
1  
@MarkAmery, I've seen the LQPQ cross 800 in the last week of Oct. I remember that in that particular week the queue never came below 750. – Bhargav Rao 48 mins ago

You must log in to answer this question.

Browse other questions tagged .