I recently received an email from "Jeff // Stack Overflow" (no relation), containing a link to a survey. Before the survey was an email address, and an invitation to send feedback to it.
… Unfortunately, I forgot to write this email address down. Hence the openness of this open letter.
TL;DR: Some questions in this survey are wrong, and don't allow frame-challenge responses. I wouldn't be able to draw correct conclusions from this survey, so I suspect Jeff might struggle. I advise Jeff to consult meta, in future, before investing time and effort into experimental design. (Since the company's on an AI kick, here's a metaphor from Eliezer Yudkowsky about “wise old wizards”.)
Attn: Jeff the Product Manager.
Hi there,
We're excited to invite you to participate in our latest round of user research! This survey will help us better understand what question quality means on Stack Overflow.
This survey boils down to scoring questions against a three-category rubric:
Category Definition Context and Background The question provides comprehensive context, including necessary details, background research, and a Minimum Reproducible Example (if applicable) to ensure full understanding of the problem. Previous attempts to solve the problem are also documented. Expected Outcome The question clearly states the desired outcome or goal to solve the problem. Formatting and Readability The question is well-formatted with correct grammar and spelling, and includes properly formatted, easy-to-understand code when relevant.
There's a much more detailed rubric later in the survey, which has clearly had a lot of effort put into it. Unfortunately, it's completely wrong. You've confused our guidance for new users for some kind of "how to write an awesome question!" instructions. Really, they're more "ensure there's enough raw information to make a good question out of" instructions.
There are questions that score very highly on the rubric, yet are long-winded and unuseful, and/or (to use one of your examples) exact duplicates of existing questions. Your survey doesn't provide a way of explaining why I disagree with the rankings, so there's no way for me to give this feedback.
(The answers I have been able to give would appear to validate your rubric, because this survey does not seek to disprove that hypothesis. I'm a little concerned that you might read the survey results as supporting it. Adding an "is this a good question?" Likert might've helped: that would at least have tested how well your proxy metrics correspond to the perceived ground truth.)
Likewise, the #2 top question (by votes) on the network, How do I undo the most recent local commits in Git?, would get 2/2/5 (out of 5) on your rubric. It contains no research effort¹, nor an MCVE, nor documentation of previous attempts. The goal is stated vaguely: as you can see from the answers, many different things might be meant by the words in the question. And it's a better question for all of this. Questions are for people who don't know the answer, and want to find the correct answer.
It would've saved you a lot of time, had you asked the first question from your survey:
(Optional) As a reviewer, are there any additional categories you consider when evaluating the quality of a question that are not listed here?
on meta, before doing all this work. (Preferably main meta: you might struggle to interpret SO-specific aspects of question review until you understand the general basics.) This might get you a list such as:
- Is the question narrow enough to be answered within the Stack Exchange format? (yes = good)
- Is it broad enough for answers to be generally-useful? (yes = good)
- Does the title describe the general case of a problem while the question body asks about a specific case? (no = good) If so, I'll usually edit to fix that.
- Is it on-topic? (yes = good)
- How are the tags looking?
- Is this an X/Y problem? (e.g. querent is asking some ridiculous academic question like "how can I implement RFC 1149 without a bird?", with enough specific details to make me think they're serious)
- Are the results of failed attempts given, or are attempts just described as "failed"? (results given = good)
Except, y'know, meta answers tend to be better than this.
¹: See Does a well explained question nullify a "no research effort" downvote? and How does "proof of effort" make a question better?.