Giving question feedback in private - a moderating system to reduce conflicts

I don't think that giving any messages (feedback) in private will be a good idea. There's two reason:

1. If you add a feature where user can "message" in private (1:1 no one else even moderator can't access/see) than, some user will use abusive/harmful words. So, 1:1 isn't a good idea.
2. Now, what if moderator can access them. So, no 1 won't happen. So, is the feature OK? No, totally not! Cause, there's lot of user. If you see a poor quality post than you will feedback in private which only moderator only can access. Then, if I see the same post I will do the same thing. So, the author will get tons of private feedback which are saying the same thing.

So, messaging (giving feedback) in private won't be good feature.

Deleting posts “as slowly as possible”. Bad questions get slowly grinded down into the dust by down votes, comments, close votes, all in public, really rubbing it in. And even when it sits there with 5 close votes and -10 score, it is still published for everyone to see.

It's a good idea. Cause, In SE there's lot of poor quality post which have no answer and, they are closed. However I update the post SE doesn't open it. I don't know why. I had faced the issue. Poor quality post should be deleted cause, user like me review old posts. If user sees posts like this we(user) feel annoyed. So, it would be a good idea to delete posts like them.

Most of new user (like me) don't know how to ask a good question. And, we don't want to search a lot to search for how to ask a good question. While it's completely like we are just wasting time. So, when user creates an account in Codidact. Then, they should be redirected to a page where they can read about How to ask a great question?, How to use MathJax?, What is meta?(Not every understand how meta works . I was one of them also. @MonicaCellio told me in a post) and some more. And, there should be a logic given the user can't ask any question until he reads "How to ask a great question". If user gets knowledge how to ask a good question than it will very useful for others (answerer).

I'd like to propose a different way of thinking about the problem (and I agree there are problems here).

Some premises:

• New users don't know how things work, so we need to keep it simple.

• Many non-veteran users are deterred by bad "people" experiences -- if your question is off-topic then ok no harm, but if people leave comments, especially public ones, that you read as criticizing you, that feels bad. Prevention is better than cleanup, because first impressions matter.

• Many engaged community members want to lend a helping hand, but don't want to do redundant work or be part of a pile-on. Posters also don't want to be on the receiving end of an unintended pile-on ("this is the 27th person who's privately told me that"). If feedback is private, some sort of status information still needs to be public, like "3 users have given private feedback in the last 24 hours".

• Not all users want to receive private feedback; some would prefer everything be public. (This has already been demonstrated in a comment.) People shouldn't be required to engage in private discussions.

• People giving private feedback benefit by being able to work together. We've seen enough "joint debugging" in comment threads to know this. Private does not mean 1:1.

I envision a system where, by default, a new post gets a "private-ish feedback" thread (after we have threaded comments). A poster can turn it off, by post or as a user preference. For a post that has this thread, people with some ability to be determined (to keep out drive-by trolls) can see the thread and participate. Other people can see that the thread exists -- something conveying that private discussion is happening already.

For questions, the asker should be able to directly put the question on hold while addressing feedback. (If the owner alone put it on hold, then the owner alone can reopen it -- otherwise people won't do it.)

The question isn't hidden or relocated; that'd be more confusing than helpful, I think. I'd like to think that the combination of it being on hold and the visible presence of private feedback would be enough to signal to other community members "we're working on this; be back later". "Regular" comments wouldn't be affected; this is about adding one special thread, not removing anything else.

There are a lot of details to work out were we to take this approach, but I want to get feedback on the high-level idea before tackling them. Thoughts?

posted over 3 years ago

CC BY-SA 4.0

Monica Cellio‭ staff

64 372 2259 824

I strongly against of the idea of a private feedback for the reasons that were already named in other answers. No point to repeat them one more time.

But I find an idea of the Sandbox, Workshop, whatever we call it amazing. Moreover in a different community I had proposed something similiar to it by myself. I was quite frustrating about big amount of Qs from begginers who didn't know to write Q properly and were turned down just because of that.

Some thoughts about implementation:

• I think it should be like a chat section cause I imagine discussion about how to improve Q would be active so comments won't fit. But if it is hard to implement best to start with usual answers and comments and change it later if needed.

• A separate category sounds reasonable but I don't think it makes sense to hide it from general view. Those who have no interest in such helping could ignore that category.

• I think that all Qs that were closed should be moved to this new category automatically and removed from there after some period of time. Not certain about this one but I definitely don't want to see closed Q with no chances to improve because they seemed off-topic to someone.

• I would prefer don't have voting system in a new category at all - some people really cares about downvotes.

posted over 3 years ago

CC BY-SA 4.0

FoggyFinder‭

15 12 96 16

We know from over 10 years of experience from SE/SO that one of the most common sources of drama, snark, rudeness, escalating arguments, conflicts, users feeling unwelcome, the community getting accused of elitism and so, all originate from comments left as feedback to a potentially bad question.

Yes, disagreement can create all that. But is that the fault of the comment mechanism? Are the escalations caused by disagreement, or the vehicle it was delivered with?

Humans often simply don’t take kindly even to constructive criticism, especially not when given in public for the world to see.

The basics of leadership & keeping people motivated is to give praise loudly in public but to give criticism discreetly in private. This makes people far more likely to actually listen to the criticism and change.

I agree that people don't want to lose face, and are therefore more likely to admit potential for improvement in private.

However, the social environment of a company is markedly different from a community run website. We don't have leaders in control of the financial well being of contributors. In a company, losing face threatens your livelihood. On Codidact, we're losing face in front of strangers whose opinion has little impact on our lives.

That's why I think that the visibility of feedback on codidact matters little, and thus little could to be gained by moving feedback private.

However, I fear much would be lost, because public feedback has a number of important advantages:

• it helps prevent redundant feedback
• it improves feedback quality, because people can give feedback on feedback, and see how others give feedback
• it increases the reach of feedback, by showing the feedback to more people, some of which are likely to benefit, too

Overall, this makes giving feedback more efficient, effective, and therefore also less frustrating, which tends to result in more productive feedback and fewer escalations.

That is not say that we should not try to improve this point of friction. But I fear that privacy will do more harm than help.

posted over 3 years ago

CC BY-SA 4.0

3y ago

meriton‭

0 1 4 1

It's been a long time since this question was asked, and in the meantime there have been lots of changes to the platform. It turns out we can do most of what you're asking for now, although some key steps are restricted to moderators and aren't yet available to people with other abilities. I'll describe what is technically possible now; how to apply it is largely a matter of policy, which should be decided by individual communities.

• Give trusted users and community moderators the powers to instantly close a post and move it to a "post feedback" area.
• This could possibly be a special kind of site category only viewable by those with an interest of helping new users. A slight tweak to the current category system perhaps?
• The post will instantly disappear from the main site and normal users will no longer see it. These is no longer a need to pile on down votes and close votes.

More specifically, moderators can move a post from one category to another. The categories must share a tag set and support the same post types, so questions in Q&A can be moved to questions in Workshop (a separate category using the Main tag set). We can't turn them into articles (and that would add complications for already-existing answers anyway), but moderators can also close questions.

So, in principle, a community that wants to could, today, have the following setup:

• A category called Workshop (or whatever you want to name it).
• Moderators can move questions to Workshop and close them, perhaps with a new close reason that includes some workshop-flavored guidance.
• Moving the question to another category does not change its URL (I just tested this), so if the OP kept it open in a browser, that still works.

The category would remain visible; there's no need for privacy, and if the OP has signed out we don't want to give the impression the question was nuked entirely. It's a separate category; people who don't want to be involved won't go there.

• Feedback is given in comments as usual, but now only by people actually interested in helping.

Handled because the question would be closed in the Workshop category.

• Once the post has been edited into shape by the OP, a copy of the improved question can be restored to the main site by the same users/mods that had the privileges to remove it.

Copies are hard (and would break the URL), but it can be moved back. This means comment threads would move, so as part of moving it, mods could archive or delete comment threads as appropriate. We shouldn't place the entire burden here on mods, so people participating in the Workshop should use flags to help identify what should go away.

We can't reset votes as part of this. We can make votes in the Workshop have 0 effect on reputation, but we can't change the actual votes.

If any community would like to try something like this, please discuss it in your Meta category, including what makes a question suitable for workshopping (how do people know what should be sent there?) and how the community would signal that the question is ok for reopening now. Some proposed text for the category description (what you see at the top of the category) and close reason would also be great. It's clear from the voting on this Meta proposal that there are conflicting opinions about the idea, so we'd like to see something resembling consensus from the active participants on a community before doing this. We are happy to set it up if a community wants to try a workshop. We're here to help, not to either require or forbid community-level policies.

posted 7 months ago

CC BY-SA 4.0

Monica Cellio‭ staff

64 372 2259 824

I initially was lukewarm about this proposal but now I think I like it, at least in the broad strokes. In particular, I prefer the idea of a separate place where work-needed questions are temporarily held—I'll call it the Workshop—with its own comments, over an optionally-private comment thread.

The reasons to have a separate Workshop all stem from the ways that interacting with questions being workshopped (should) differ from interacting with acceptable questions. These differences include:

• The audiences are different. The audience for regular questions is the set of people interested in answering questions. The audience for questions in the Workshop is the set of people interested in improving other people's questions. Different audience members should see the things they're interested in.

• The available actions should be different. A question in the Workshop should not be answerable. This prevents answerers from wasting their effort on answering what they think the question is, as opposed to what the final form of the question will be. It also, of course, provides real motivation to askers to work with the community to graduate their questions from the Workshop. We might also want voting in the Workshop to work differently—I have a pretty loose sense that a question upvote currently means ‘I'd like to see someone answer this question,’ and a downvote ‘I think this question doesn't belong here or needs improvement,’ and in the Workshop neither of those conditions really apply. But maybe we'd want to have a vote to graduate a question, instead of making it a single user's decision?

• The nature of the commentary is different. Threaded comments might be an acceptable way to separate question-feedback comments from other comments, but keeping the question-feedback comments in the Workshop seems like it would do an even better job of showing people what they want to see by default.

I'm not as excited about the proposed mechanism for how questions end up in or get graduated from the Workshop, but it'll do as a starting point.

posted over 3 years ago

CC BY-SA 4.0

r~~‭

4 9 46 8