Support

What types of questions should I avoid asking?

Guidance on which questions aren't a good fit for Stack Internal, so your posts get the answers they need.
Applies to:
Free
Basic
Business
Enterprise

Overview

Use these tips to identify question types to avoid and improve your chances of receiving helpful answers.

Keep questions focused and answerable

Avoid posting a question if:

  • It's so broad that an entire book could answer it.
  • You want to start a discussion rather than get an explanation.
  • There's no concrete problem to solve.

Avoid these subjective question types

To prevent your question from being flagged and possibly removed, avoid subjective questions where:

  • Every answer is equally valid, for example, "What's your favorite tool for ______?"
  • You post your own answer alongside the question and expect more alternatives, for example, "I use ______ for ______. What do you use?"
  • There's no actual problem, for example, "I'm curious whether other people feel this way."
  • The premise is hypothetical, for example, "What if ______ happened?"
  • The question is a complaint in disguise, for example, "______ sucks, am I right?"

Subjective questions

Some subjective questions are acceptable, but "subjective" doesn't mean anything goes. A constructive subjective question:

  • Asks for explanations of "why" or "how."
  • Invites detailed answers, not one-liners.
  • Has a fair, impartial tone.
  • Encourages sharing real experience, not just opinion.
  • Asks contributors to back up opinions with facts or references.
  • Addresses a real challenge, not just casual social interest.

If you have questions or issues, reach out to our support team for help.

https://doc-automation.netlify.app/pdfs/docs/community/all_products/getting_started/avoid_question_types.pdf

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article