Skip to main content
Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Required fields*

Help us make "Not Constructive" and "Not a Real Question" closures more effective [closed]

In the recent off-topic discussion, Pekka 웃 suggested that other close reasons could be further broken out as well . We've got some more specific ideas along those lines, and we want your input and suggestions. Get comfy; this one's long.

Goals for "Not a Real Question" and "Not Constructive"

These goals will look familiar if you read the Off-Topic closing post, but the solution will likely differ. Here's what we want to achieve:

  • make the problem clear — the close reason should make it as clear as possible to the OP exactly what is wrong with their post
  • make them want to fix it — the language and workflow should encourage editing wherever possible (improving a post should seem more logical than arguing against closure.)
  • make those things happen in-line — if we send them to another page, we'll lose some users
  • minimize site-specific solutions — site by site differences should be limited to places it's truly necessary. "Off-topic" is literally defined differently on each site, so it needs customization, but we want the names and verbiage for the rest to be consistent.

Why are we doing this? Is there really a problem today?

Again, these reasons are working. If my choices were to keep em as is, or dump em entirely, I'd keep em, as they are doing a damn good job ensuring that our sites don't ever look like this site does. (Those all came from their front page.)

But, while we don't need to change what these reasons do, we can improve two things about them:

1. The problem they describe needs to be clear and specific

Consider this closed question from our apple site: What's special about Apple Airport Extreme?

Imagine you're the OP — since he's not spamming, trolling, etc., we can assume he thought he was doing the right thing when he posted his question. So, when his question is closed as "Not Constructive", he presumably won't think "oh, of course!" — he needs more information to figure out what's wrong. Let's see what we give him:

enter image description here

the question is "Not Constructive" I'll revisit that phrasing in the next section, but it's safe to say that it does little to identify the exact problem.

We expect answers to be supported by facts, references, or specific expertise. "Well, that's perfect! I'm actually looking for all those things in your answers, and I specifically highlighted a couple I thought might be relevant (Wifi range, transfer speeds, etc.)"

This question will likely solicit debate, arguments, polling, or extended discussion. "Will it? It's about the specific specs that make An Apple router different from other, similar ones; it's not exactly 'who's right and wrong in the Middle East'"

If you feel that this question can be improved and possibly reopened "Improved how? I still don't know what I did wrong. Re-opened? How can I prepare my case for some appellate court when I don't even know what I did wrong yet??"

see the FAQ for guidance:

enter image description here Yup. That's the same definition, complete with a link to itself.

So, what's actually wrong with this question? For this discussion, it doesn't really matter. What's important is that whatever's wrong, the current close reason doesn't convey it to the OP, so he still can't improve or avoid it.

I used a "Not Constructive" example, but NARQ has a similar problem. It reads:

enter image description here

There are five possible things that might be wrong there, and while the closer may know exactly which one is the problem, the asker presumably doesn't start from the position that his post is any of those undesirable things, which makes guessing which one applies to him challenging.

2. The wording shouldn't make you defensive

"Not constructive" seems polite to us, because we feel like we're essentially using it instead of

"that has no answer; stop wasting our time"

or

"you're kind of ranting and being a jerk"

But that's not the context for the asker. The asker thinks they asked a perfectly reasonable question. As such, they're unlikely to respond by thinking, "I could be more constructive". From their perspective, it sounds like something a slightly detached guidance counselor might say to a child.

And even if they just got back from some meditation, and are just really, really open-minded, there's still no opening to say, "okay, I should try to fix that," because it isn't specific enough. So, their only logical response is defiance: "Why isn't it constructive?"

And the same is true of "Not a Real Question". Everyone thinks they've asked a real question. I imagine myself being told by a colleague at work, "I read your email. That isn't a real proposal". It's almost impossible to honestly convince myself that I'd think "Huh that's odd. I thought it was. I wonder how I can improve it to make it a real one".

Which is part of why NARQ closures tend to elicit arguments citing the prominent inclusion of question marks, rather than legitimate attempts to correct problems.

Okay, enough complaining. What can we do about it?

Well, we want to continue to close the questions these currently are used for, but we need to make the feedback clearer, and incentivize improvement (or at least learning). Here's what we came up with:

Eliminate "Not Constructive" and "Not a Real Question", and replace them with more specific reasons:

unclear what you’re asking — Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking.

too broad — There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.

primarily opinion-based — Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.

In all three cases, not only is it clear what the problem is, it should also be clear what you need to do (when possible) to make the question acceptable. It's slightly less explicit in the last reason, but that's because fewer of those are savable.

To see if these reasons seemed to cover us, we had both community team members and mods try to apply them to a largish sample of previously closed questions.

Based on that review, we believe that these reasons will cover almost all current NC and NARQ questions — our sample had 94% well-covered, with the remainder pretty easily addressed using site-specific Off-Topic reasons, as proposed here.

That was long. Did you want something?

Of course! We want your input. We got a lot of these ideas from meta posts, and we've done enough testing (both inside and outside our echo chamber) to feel good about the approach, but we want to know what you think and how you might tweak or improve it.

Part of the close reason rework project:

  1. Changes to "close as duplicate" (part deux)
  2. Help us make "Off-Topic" close reasons clearer to the OP
  3. Help us make "Not Constructive" and "Not a Real Question" closures more effective
  4. Every "close" has its thorn: replace "close" with "on hold" for the first five days

Answer*

Draft saved
Draft discarded
Cancel
27
  • 1
    I don't disagree with your reasoning, but I don't want to leave comments on everything that I've voted to close. If you have pre-canned responses to close votes, then you're not really getting ideal feedback from the closers at all times. Commented Mar 14, 2013 at 17:22
  • So you don't want to leave a comment. Which is the points I was making; Most people won't bother to. Which leads the asker to be confused, and leave, or later ask on meta why their question was closed. Wouldn't it be better to type at least once sentence, for the askers sake? Like "You need to include a code snippet of what you tried". There are only so many canned responses, and many of them are not specific enough to be clear to the user. What I'm asking for would potentially take less time than leaving an answer. Commented Mar 14, 2013 at 17:26
  • 9
    Each close voter should be required? No. I do take the time to write a comment when useful, and while I haven't made any statistics, I'm sure that's only a small minority of my votes to close. And often when I'm not the first close voter and a comment is useful a previous close voter has already left a satisfactory one. Commented Mar 14, 2013 at 19:44
  • @Gilles If you do, that's great. Most people don't. And I would say a satisfactory comment would be one not quoting the FAQ, wouldn't you agree? Commented Mar 14, 2013 at 19:46
  • 1
    @Luke No, sometimes a satisfactory comment does quote the FAQ (a specific section, not the thing as a whole). Commented Mar 14, 2013 at 19:59
  • 4
    @Luke: It has been my experience that users who ask questions I VtC are those most likely not to improve their question. Usually any comment I leave ends up being ignored or argued. It is not worth my time to comment. If it is worth my time to comment, I usually will spend it editing instead. Basically, Vote to Close or Edit, those are the only two options that produce a better signal to noise ratio. Commented Mar 14, 2013 at 20:04
  • @Gilles That is not always the case. I've had a question of mine closed where the commentar quoted the FAQ but was not specific enough why they felt the question was that way. I posted on meta and got more specific direction and the question was improved and re-opened. Commented Mar 14, 2013 at 20:06
  • 1
    @sixlettervariables It shouldn't be a comment - I agree. That's why I suggested it be something separate to go along with the description of the canned close reason. I'm just saying providing more specific information is more helpful to the asker than a canned response. I'm glad some people take the time to leave a helpful comment, but not everyone does. Commented Mar 14, 2013 at 20:08
  • @Luke: my point is I shouldn't have to leave a comment, the VtC should be comment enough. If I can comment and substantially improve upon the information conveyed by the VtC reason, then I probably should spend the time editing. Comments are noise. Commented Mar 14, 2013 at 20:11
  • 2
    @sixlettervariables You can't always edit a question to improve it. In my case, there wasn't enough information. My question was closed as being too broad - and the commentator stated that. But they failed to say how it was broad, and what I could do to improve it. I was then left with a closed question with no idea what to do. It wasn't until I posted on Meta I got a clear and concise answer from Bill. If people aren't willing to write a single comment explaining their point of view, why should they be allowed to close vote? Why leave answers at all? Askers shouldn't have to go to Meta. Commented Mar 14, 2013 at 20:17
  • 1
    @Luke: you're an odd duck compared to the average user on SE who have a closed question. Most have no desire to change or completely misunderstand SE. I've given up on doling out comments because it isn't worth my time. A VtC is sufficient enough and provides enough for a user who could benefit the community to figure out what to change. You seemed to figure it out and are now benefiting the community. I'd say the process works. Commented Mar 14, 2013 at 20:22
  • 1
    @Luke: none of the VtC reasons are offensive unless you read into them inappropriately. Regardless, your question was one in a sea of many many many lower quality questions. Like I said, unless you spend the time to ask for clarification, we have no reason to assume you want to know why it was closed. Experience tells us you'd rather not and would rather do it your way (nb: plural form of you and your). Commented Mar 14, 2013 at 21:04
  • 2
    @sixlettervariables Of course there are standards. We're not arguing that. We're talking about requiring a single sentence why you think the question should be closed and anonymously given to the asker as guidance. Something that should already be in-mind after examining the question and deciding which category it should be closed under. A good question can come from a bad one. Hand-holing only applies when helping the same person multiple times who doesn't get it. Assuming "it's not worth it" with every person doesn't improve anything - it causes bad experiences for people like me. Commented Mar 14, 2013 at 22:04
  • 1
    If something like this were implemented, you'd have to somehow make it very clear that the notes left by the CVers are not necessarily "official" reasons for closing things. What's to prevent someone from leaving a note like "no, that's stupid?" It sounds nice, but in practice it might be too chaotic. Probably better just to allow canned responses. Maybe some kind of custom note in addition to canned responses could work, though. Commented Mar 23, 2013 at 23:54
  • 1
    @Luke: "I'm sure other people will be more specific." I'm sure that, in many if not most cases, no other people will be more specific. Commented Apr 3, 2013 at 20:07

AltStyle によって変換されたページ (->オリジナル) /