Return to Answer

What makes a high quality open-ended question?

We already have guidelines on how to write “constructive subjective” questions in the Help Center. Askers should (always have been /) be linked to that appropriately in the Ask Question flow, or it should just be automatically shown to any participant in Q&A that are “opinion-based” now that the meta tag exists (for better or for worse).

As for asking for tooling recommendations, guidance on MSO is to ask how to do the thing you want to do (and be clear about what you want, which is just generally true of any good question), and let answerers recommend a tool if they think it’s truly an appropriate solution to the problem. In fact, guidance on how to handle questions that ask for resource recommendations is to remove the resource recommendation request if the question already asks how to get what they actually want.

I think these sets of guidance work, for the most part. If anything, the issue I see is that people are not aware of them enough, and that goes equally well for reviewers / close-voters / curators as for askers. I don't see an immediate reason why these sets of guidance should change. What I do think needs changing is their visibility.

I think I've mentioned these things in some shape or form in every single interaction I've had on posts about this subject. It frustrates me because (in my eyes,) the way to get the benefits of these existing guidelines is through changes to site UI/UX, and we can't make those changes. Only the company can. So I guess here's to hoping that it happens.

Want data to guide discussion and decision-making? If you can’t pull it yourselves, let us know what you want to see and we’ll do our best.

I’m pretty sure requests have already been made to have data for this content in SEDE (Make Discussions posts available in SEDE ? *waves to myself from over two years ago). If not, and switching the content to fit the general Q&A won’t automatically result in that, please put it in SEDE.

Is this a good time to mention that the usability of SEDE continues to exist in a degraded and sorry state?

Create some new questions here on Meta and start talking about what’s most important.

What tag/tags should we include to make sure staff on this project “approach” see the discussion?

What makes a high quality open-ended question?

We already have guidelines on how to write “constructive subjective” questions in the Help Center. Askers should (always have been /) be linked to that appropriately in the Ask Question flow, or it should just be automatically shown to any participant in Q&A that are “opinion-based” now that the meta tag exists (for better or for worse).

As for asking for tooling recommendations, guidance on MSO is to ask how to do the thing you want to do (and be clear about what you want, which is just generally true of any good question), and let answerers recommend a tool if they think it’s truly an appropriate solution to the problem. In fact, guidance on how to handle questions that ask for resource recommendations is to remove the resource recommendation request if the question already asks how to get what they actually want.

I think these sets of guidance work, for the most part. If anything, the issue I see is that people are not aware of them enough, and that goes equally well for reviewers / close-voters / curators as for askers. I don't see an immediate reason why these sets of guidance should change. What I do think needs changing is their visibility.

I think I've mentioned these things in some shape or form in every single interaction I've had on posts about this subject. It frustrates me because (in my eyes), the way to get the benefits of these existing guidelines is through changes to site UI/UX, and we can't make those changes. Only the company can. So I guess here's to hoping that it happens.

Want data to guide discussion and decision-making? If you can’t pull it yourselves, let us know what you want to see and we’ll do our best.

I’m pretty sure requests have already been made to have data for this content in SEDE (Make Discussions posts available in SEDE ? *waves to myself from over two years ago). If not, and switching the content to fit the general Q&A won’t automatically result in that, please put it in SEDE.

Is this a good time to mention that the usability of SEDE continues to exist in a degraded and sorry state?

Create some new questions here on Meta and start talking about what’s most important.

What tag/tags should we include to make sure staff on this project “approach” see the discussion?

What makes a high quality open-ended question?

We already have guidelines on how to write “constructive subjective” questions in the Help Center. Askers should (always have been /) be linked to that appropriately in the Ask Question flow, or it should just be automatically shown to any participant in Q&A that are “opinion-based” now that the meta tag exists (for better or for worse).

As for asking for tooling recommendations, guidance on MSO is to ask how to do the thing you want to do (and be clear about what you want, which is just generally true of any good question), and let answerers recommend a tool if they think it’s truly an appropriate solution to the problem. In fact, guidance on how to handle questions that ask for resource recommendations is to remove the resource recommendation request if the question already asks how to get what they actually want.

I think I've mentioned these things in some shape or form in every single interaction I've had on posts about this subject. It frustrates me because (in my eyes,) the way to get the benefits of these existing guidelines is through changes to site UI/UX, and we can't make those changes. Only the company can. So I guess here's to hoping that it happens.

Want data to guide discussion and decision-making? If you can’t pull it yourselves, let us know what you want to see and we’ll do our best.

I’m pretty sure requests have already been made to have data for this content in SEDE (Make Discussions posts available in SEDE ? *waves to myself from over two years ago). If not, and switching the content to fit the general Q&A won’t automatically result in that, please put it in SEDE.

Is this a good time to mention that the usability of SEDE continues to exist in a degraded and sorry state?

Create some new questions here on Meta and start talking about what’s most important.

What tag/tags should we include to make sure staff on this project “approach” see the discussion?

What makes a high quality open-ended question?

We already have guidelines on how to write “constructive subjective” questions in the Help Center. Askers should (always have been /) be linked to that appropriately in the Ask Question flow, or it should just be automatically shown to any participant in Q&A that are “opinion-based” now that the meta tag exists (for better or for worse).

As for asking for tooling recommendations, guidance on MSO is to ask how to do the thing you want to do (and be clear about what you want, which is just generally true of any good question), and let answerers recommend a tool if they think it’s truly an appropriate solution to the problem. In fact, guidance on how to handle questions that ask for resource recommendations is to remove the resource recommendation request if the question already asks how to get what they actually want.

I think these sets of guidance work, for the most part. If anything, the issue I see is that people are not aware of them enough, and that goes equally well for reviewers / close-voters / curators as for askers. I don't see an immediate reason why these sets of guidance should change. What I do think needs changing is their visibility.

I think I've mentioned these things in some shape or form in every single interaction I've had on posts about this subject. It frustrates me because (in my eyes,) the way to get the benefits of these existing guidelines is through changes to site UI/UX, and we can't make those changes. Only the company can. So I guess here's to hoping that it happens.

Want data to guide discussion and decision-making? If you can’t pull it yourselves, let us know what you want to see and we’ll do our best.

I’m pretty sure requests have already been made to have data for this content in SEDE (Make Discussions posts available in SEDE ? *waves to myself from over two years ago). If not, and switching the content to fit the general Q&A won’t automatically result in that, please put it in SEDE.

Is this a good time to mention that the usability of SEDE continues to exist in a degraded and sorry state?

Create some new questions here on Meta and start talking about what’s most important.

What tag/tags should we include to make sure staff on this project “approach” see the discussion?

What makes a high quality open-ended question?

We already have guidelines on how to write “constructive subjective” questions in the Help Center. Askers should (always have been /) be linked to that appropriately in the Ask Question flow, or it should just be automatically shown to any participant in Q&A that are “opinion-based” now that the meta tag exists (for better or for worse).

As for asking for tooling recommendations, guidance on MSO is to ask how to do the thing you want to do (and be clear about what you want, which is just generally true of any good question), and let answerers recommend a tool if they think it’s truly an appropriate solution to the problem. In fact, guidance on how to handle questions that ask for resource recommendations is to remove the resource recommendation request if the question already asks how to get what they actually want.

Want data to guide discussion and decision-making? If you can’t pull it yourselves, let us know what you want to see and we’ll do our best.

I’m pretty sure requests have already been made to have data for this content in SEDE (Make Discussions posts available in SEDE ? *waves to myself from over two years ago). If not, and switching the content to fit the general Q&A won’t automatically result in that, please put it in SEDE.

Is this a good time to mention that the usability of SEDE continues to exist in a degraded and sorry state?

Create some new questions here on Meta and start talking about what’s most important.

What tag/tags should we include to make sure staff on this project “approach” see the discussion?

What makes a high quality open-ended question?

We already have guidelines on how to write “constructive subjective” questions in the Help Center. Askers should (always have been /) be linked to that appropriately in the Ask Question flow, or it should just be automatically shown to any participant in Q&A that are “opinion-based” now that the meta tag exists (for better or for worse).

As for asking for tooling recommendations, guidance on MSO is to ask how to do the thing you want to do (and be clear about what you want, which is just generally true of any good question), and let answerers recommend a tool if they think it’s truly an appropriate solution to the problem. In fact, guidance on how to handle questions that ask for resource recommendations is to remove the resource recommendation request if the question already asks how to get what they actually want.

I think I've mentioned these things in some shape or form in every single interaction I've had on posts about this subject. It frustrates me because (in my eyes,) the way to get the benefits of these existing guidelines is through changes to site UI/UX, and we can't make those changes. Only the company can. So I guess here's to hoping that it happens.

Want data to guide discussion and decision-making? If you can’t pull it yourselves, let us know what you want to see and we’ll do our best.

I’m pretty sure requests have already been made to have data for this content in SEDE (Make Discussions posts available in SEDE ? *waves to myself from over two years ago). If not, and switching the content to fit the general Q&A won’t automatically result in that, please put it in SEDE.

Is this a good time to mention that the usability of SEDE continues to exist in a degraded and sorry state?

Create some new questions here on Meta and start talking about what’s most important.

What tag/tags should we include to make sure staff on this project “approach” see the discussion?