How to ask a question a community can answer

Every community has a quiet corner where someone has just posted a question and is waiting. Sometimes the replies arrive within the hour, warm and useful. Sometimes the question sits there for days with nothing under it but a view count. The difference is rarely about luck, and it is almost never about whether the people reading are kind. Most of the time it comes down to how the question was asked.

Asking well is a small skill, and like most small skills it can be learned in an afternoon and practised for years. What follows is how we would go about it, whether you are posting in a hobby forum, a comment section or a busy discussion board. None of it is a rule. It is simply what tends to make it easy for a stranger to help you.

Look around the nook before you knock

Before you write anything, spend five minutes looking. Search the community for the words you would use in your question, and then for the words someone else might use. Read the pinned posts and any frequently asked questions. Skim the last week or two of threads in the place where your question belongs.

This is not about avoiding a telling-off. It is about saving yourself time. Often the answer is already there. When it is not, you will usually find a near miss: a thread that covers half your problem, or one where the advice did not work for you. Both are worth mentioning when you do post, because they show readers where to start and what to skip.

It also tells you about the local customs. Some communities like a short tag in the title, some want questions in a weekly thread, some prefer you to reply to an old thread rather than start a new one. A few minutes of reading saves an awkward first post.

Put the real question in the title

A title is the only part of your post that most people will ever read. In a list of threads, “Help please!” and “Quick question” look the same as a hundred others, and they give a helpful reader no reason to click. A title that names the actual problem does the opposite: it lets the right person recognise, at a glance, that they know the answer.

Compare these:

• Weird problem with my bread
• Sourdough loaf is dense in the middle even though the crust browns well

The second is longer, but someone who bakes will know within a second whether they can help. Aim for a title that would still make sense if it were the only thing anyone saw. If you can phrase it as a question, do.

Say what you want, what you tried and what happened

The body of a good question usually has three parts, and they are worth keeping in this order.

1. What you are trying to do. Not just the step that went wrong, but the goal behind it. People can often suggest a better route to the goal than the one you were stuck on.
2. What you tried. List the things you have already done, including the advice you found while searching. This stops readers repeating suggestions you have ruled out.
3. What happened instead. Describe the result as plainly as you can. If there was an error message, copy the exact words rather than paraphrasing them. If something looked wrong, say what you expected to see and what you saw.

Include the details that matter: the version of the software, the recipe you followed, the model of the thing that broke. If you are not sure whether a detail matters, include it briefly. It is easier for a reader to ignore a line than to drag it out of you over three replies.

And leave out the apologies. “Sorry if this is a stupid question” takes up the first line, which is where the useful part should be. You are allowed to ask.

Make it small enough to answer

A question that tries to cover everything is hard to answer at all. “How do I get better at drawing?” could fill a book. “How do I stop my figure drawings looking stiff when I work from photos?” can be answered in a reply.

If your problem is large, break it up. Ask about the part you are stuck on now and mention the bigger picture in a sentence. If you have three separate questions, consider three separate posts; each one will get a clearer answer, and each will be easier for the next person to find.

For technical problems, the same idea has a name: the minimal example. Strip your problem down to the smallest version that still shows the issue. Very often you will find the cause yourself while doing it, which is its own kind of answer. Wikipedia has a short explanation of the minimal reproducible example if you want the longer version.

Stay for the replies

Posting is half of asking. The other half is coming back. Check in a few times over the next day or two. When someone asks for a detail, answer it in the thread rather than in a private message, so that the next reader can follow along. When someone suggests something, try it and say what happened, even if it did not work. “That changed the error, here is the new one” is enormously useful to the people helping you.

If a reply solves it, say so, and say which one. Thank the person by name. If you worked it out yourself, post the solution anyway. There is a particular kind of loneliness in finding, years later, a thread that describes your exact problem and ends with the original poster writing “never mind, fixed it”. Do not be that thread.

When nobody answers

Sometimes a good question still gets silence. People are busy, the right person has not seen it, or the question is simply harder than it looks. Give it a reasonable amount of time before doing anything; what counts as reasonable depends on how busy the community is.

Then reread your post as if you were a stranger. Is the title specific? Is there enough detail to start from? Is it in the right place? If you can improve it, edit the original post or add a reply with the new information, rather than posting the same question again elsewhere. A short, polite bump with something new in it (“I have since tried X, same result”) is usually welcome. Posting identical copies across several corners of a community usually is not.

If you are asking in a comment section here, remember that comments are held for review and appear once a moderator has approved them, so a short delay is normal. Our guidelines cover what belongs in comments, and the help page explains how commenting works.

A well-asked question is a small gift to the community as well as a request. It gives someone the chance to be useful, and it leaves a trail for everyone who comes after. When it is your turn to reply, our companion piece on writing a helpful answer picks up from the other side of the table.