How to Ask a Question Worth Answering

I have seen the same question, or some version of it, posted in a Facebook group dozens of times. “How do I handle X situation with the IRS?”

No context. No details. No specifics about the client, the issue, or what the person has already tried.

The responses come in fast. Most of them are variations of “need more info” or “what kind of notice?” A few people take a guess and give an answer that turns out to be wrong because they are solving a different problem than the one the asker had. The thread sprawls. Twenty replies later, somebody finally pulls enough information out of the original poster to give a real answer. By that point, half the responders have moved on, and the asker has waited a full day for help that could have arrived in ten minutes.

I have watched this pattern play out in tax practitioner groups, subreddits, X/Twitter posts, and LinkedIn discussions. The platform changes. The dynamic does not. Somebody asks a question that nobody can answer without a follow-up interview, and a small disaster of wasted time unfolds.

It also makes me forgiving of the people who post questions that make the rest of us want to throw our phones across the room. Nobody is born knowing how to ask a good question in a professional forum. It is a skill, and like most skills, you get better by paying attention to what works and what does not. What follows is what I have learned by watching what actually works.

The Problem

Every active group has a version of the same patterns. Someone posts a question that has already been answered dozens of times in the group. Someone else posts the same question in twelve different groups simultaneously. Someone asks a question so vague that answering it requires guessing what they actually want to know. Someone posts a screenshot of an error message with no context and expects a diagnosis.

This is not a character flaw. Most people who post these questions are stressed and stuck, trying to get unstuck as quickly as possible. They are not trying to waste anyone’s time. They just have not been taught that how you ask shapes what you get back.

Here is the thing that took me too long to figure out: asking a better question is not about being polite or following etiquette. It is about getting the answer you actually need. The people who ask well get help faster, get more useful help, and build relationships with the experts in the room. The people who ask poorly get ignored, get wrong answers, or get told to search the archives.

There is also a downstream cost that nobody talks about. The experts in any group have a finite amount of patience and time. Every time they answer the same poorly-framed question for the hundredth time, that patience erodes. Eventually, they stop answering at all, or they leave the group, and the quality of the whole place degrades. The people who ask well are not just helping themselves. They are helping the community survive.

Before You Post

The best question is the one you do not have to ask because you found the answer yourself in two minutes.

Search first. Every major platform has a search function. Facebook groups have one. Reddit has one. LinkedIn has one. Use it. Search for two or three keywords related to your question. If the question has been asked before, you will often find the answer and the thread where people discussed the edge cases. That thread is usually more useful than posting fresh, because you get to see how the answer holds up under follow-up questions.

If the search fails, check the pinned posts, the group rules, and any FAQ document the moderators have put together. A surprising number of common questions have dedicated resources that nobody reads. The moderators put those resources together because they were tired of answering the same question. Reward that effort by reading them.

Then check the source. If your question is about a specific product, platform, law, or tool, the authoritative source probably has a documentation page or a help center. Ten minutes with the actual source beats ten hours of crowdsourced guessing. The source is also usually more accurate than whatever the group remembers because the source updates while group memory does not.

There is also a category of questions that do not belong in a group at all. If you need legal advice for your specific situation, you need a lawyer. If you need medical advice, you need a doctor. Groups can give you general information, point you to resources, and share experiences.

If you have done all of that and still do not have an answer, now you can post. You will be in a much better position to ask a useful question because you will know exactly what you already ruled out.

How to Write the Question

Lead with the actual question. Not “Hi everyone, hope you are all having a great day, I have a weird situation.” Just the question. People are scanning. Give them something to scan.

Provide context in the next sentence or two. What are you trying to accomplish? What have you already tried? What does not work? Specifics matter more than you think. “My client got a notice” is not enough. “My client got a CP2000 proposing additional tax of $4,200 based on unreported 1099-NEC income. Do I need to file an amended return?” is something people can actually work with.

Include the details that would let someone answer without asking follow-up questions. If you are asking about software, mention the version. If you are asking about a process, mention what step you are on. If you are asking about a document, mention what kind and from what year. The goal is to let the first person who sees your question give you a useful answer instead of forcing them to interview you first.

Tell people what you have already tried. This is the single most underused move in question-asking. If you say “I tried X and it did not work because Y,” you save the responder from suggesting X. You also signal that you have done some thinking on your own, which makes people much more willing to invest time in helping you. A question that shows effort gets effort in return. A question that shows none gets none.

Skip the story. Nobody needs to know the entire history of your relationship with the client, your feelings about the situation, or your theory about why the other side is incompetent. That belongs in a different post, or in a different venue entirely. The question post is for the question.

Be specific about what you want. Are you looking for a citation? A recommended next step? A confirmation that your plan is reasonable? A second opinion? Say so. People want to help, but they cannot read your mind, and vague questions get vague answers.

A useful exercise: before you post, read your draft and ask yourself whether a stranger could answer it without asking you a single follow-up question. If the answer is no, you have more work to do. Add the missing context, cut the irrelevant context, and try again. Five minutes of editing on the front end saves an hour of back-and-forth on the back end.

On Being Rude

There are two flavors of rudeness in online groups, and both of them poison the well.

The first is the entitled asker. This is the person who posts a question and then gets annoyed that nobody has answered within an hour. The person who demands help without offering context. The person who responds to a clarifying question with “just tell me the answer.” The person who follows up with “bump” every two hours. The people in the group are not obligated to help you. They are volunteering their time and expertise for free. If you are rude about it, they will remember, and next time they will scroll past.

The thing about entitlement is that it is often invisible to the person displaying it. They are stressed, they need help, and the urgency feels like enough justification on its own. It is not. Your urgency is not anyone else’s problem. The people who answer questions well do it because they want to, not because they owe you anything. Treating them like staff is the fastest way to lose access to the only resource that was actually going to help you.

The second flavor is the smug answerer. “You should know this.” “This is basic.” “I have been doing this for 25 years.” That last one is my favorite, because sometimes the honest response is that you have been doing it wrong for 25 years and never noticed. Experience is not the same thing as being right. Years in the chair do not substitute for a citation.

The smug answerer is doing real damage even when their answer is technically correct. They are training newer members to stay quiet. They are teaching everyone who is watching that asking a question carries a social risk. The next person who has the same question will not ask it. They will guess, or they will get the answer wrong, or they will give up. The community gets smaller and dumber every time someone gets publicly shamed for asking.

If you have been doing this long enough that beginner questions annoy you, you have two choices. You can answer the question kindly and move on, or you can scroll past. Those are the only two options that do not actively harm the place you are participating in.

The AI Copy-Paste Problem

There is a newer version of bad answering, and it is getting worse.

Someone posts a question. Within minutes, another member pastes a response that is clearly the unedited output of an AI tool. Confident. Comprehensive. Authoritative-sounding. Often completely wrong, or right in a way that does not match the actual facts of the question, or right in general but missing the specific exception that makes it wrong here.

The person who posted the AI answer did not read it carefully. They did not verify it. They did not check whether the citations the AI included were real, because half the time they are not. They wanted to be the person who answered first. They wanted the social credit for knowing the thing. The accuracy of the answer was secondary to the appearance of having one.

This is a different failure mode than ordinary smugness, and it is more dangerous. The smug answerer who has been doing it wrong for 25 years at least believes their own answer. The AI-paste answerer is not even an actor in their own response. They are a delivery mechanism for output they did not check. The asker, who came to the group looking for human expertise, gets back a hallucinated regulation citation and a confident summary of a rule that no longer exists.

I am not anti-AI. I use AI tools every day. AI is genuinely useful when you treat it as a research partner that needs supervision. It is corrosive when you treat it as a vending machine that produces correct answers, because most of the time, it does not.

If you are going to use AI to help you answer a question in a group, the rules are simple. Read the output carefully. Verify any citation it produces by pulling up the actual source. Test the answer against the specific facts the asker provided. If the AI hedged, keep the hedges. If the AI cited a rule, confirm the rule exists and says what the AI claims. Then, if you are confident the answer is right, post it in your own words and disclose that you cross-checked it.

What you do not do is paste the raw output, slap your name on it, and walk away. That is not answering. That is laundering AI output through your professional reputation, and it damages both you and the group. The next time you post a real answer, the people who watched you paste a wrong AI response last week will discount it. You spent your credibility, and you got nothing in return except the brief satisfaction of being first.

Citations Over Feelings

When a question turns into a disagreement, the only thing that matters is the source.

If you are answering a question and you have a definitive answer, point to it. The statute. The regulation. The documentation. The reported decision. Whatever the authoritative source is in your field. “I have always done it this way” is not an answer. It is a personal habit dressed up as expertise.

If you are asking the question and someone gives you an answer with a source, read the source before you argue with them. Pull it up. Read the relevant section. Then decide whether it actually applies to your situation. If it does, you have your answer. If it does not, you can now explain specifically why your facts are different, which is a completely different conversation than “I do not think you are right.”

If you are answering and someone challenges you, produce the source or revise your position. Those are the only two options. Doubling down with more conviction does not make you more correct. It just makes the next person less likely to take your answers seriously.

There is a particular kind of failure mode that shows up in every professional group. Someone posts a confident answer. Someone else points out that the confident answer is wrong and provides a citation. The first person, instead of acknowledging the error, pivots to attacking the second person’s tone, credentials, or motivation. This is how a group loses its credibility. Every time it happens and goes unchallenged, the signal-to-noise ratio gets worse. The people who actually know what they are talking about start to leave, because they do not want to spend their time fighting people who are wrong but loud.

The fix is simple but unglamorous. When you are wrong, say so. “Good catch, I had that backwards.” “You are right, the rule changed.” “Let me reread the statute.” Those sentences cost nothing, and they buy you credibility. The people who are willing to be corrected publicly are the people whose answers other people start to trust.

This is how professional groups are supposed to work. The goal is to find the correct answer, not to win the thread. Everyone in the room benefits when the conversation stays anchored to what the source actually says. Everyone loses when it devolves into who feels more strongly about their position.

What Not to Do

Do not cross-post the same question in multiple groups at the same time. It annoys the people who are in all of those groups, it fragments the answers across multiple threads, and it signals that you are prioritizing speed over quality. If you have been waiting a day and the question is genuinely urgent, it is fine to try a different venue. But do not carpet-bomb. The people who do this almost always get worse answers than the people who pick one venue and ask carefully.

Do not post the question and then disappear. If someone asks you a follow-up, answer it. If someone gives you an answer that does not fit your situation, say why. The thread is a conversation, not a vending machine. The people who answer questions remember who engages and who ghosts. Engagement is currency in any group, and you spend it down every time you take an answer and run.

Do not argue with people who are trying to help you. You can push back on an answer if you think it is wrong. That is fine. But “that is not what I asked” when the person is answering what you actually asked is a good way to make sure nobody helps you next time. If the answers do not address your question, the most likely explanation is that your question was not clear, not that everyone misread it.

Do not post a screenshot of a long document and ask people to read it for you. If you want someone to review something, be specific about what part you have a question about and what the question is. Pointing at a wall of text and saying “thoughts?” is not a question. It is a request for unpaid labor.

Do not ask questions that would require someone to do your job for you. “How do I handle this entire case?” is not a question. It is a request for free consulting. Narrow it down. Pick the specific decision point you are stuck on, and ask about that.

Do not delete your post after you get the answer. The next person who has the same question will find your thread through search, and the answer will be valuable to them. Deleting it because you got what you needed is selfish in a way that is hard to articulate but easy to feel. The group helped you. Leave the answer behind for the next person.

After You Get an Answer

Thank the people who helped you. Not with a gif. Just a sentence. People remember who is gracious and who is not, and it matters more than you think the next time you need help.

If the answer solved your problem, say so. This helps the next person who finds your thread through a search. There is nothing more frustrating than reading a thread that ends with “got it, thanks!” and never finding out which of the four answers actually worked.

If you figured it out yourself before anyone responded, post the answer in your own thread. This is one of the most valuable things you can do for a group, and almost nobody does it. Your future self will be grateful when you search for the same problem two years from now and find your own answer waiting.

If you got an answer that was wrong and you eventually figured out the right one, come back and post the correction. This is harder than it sounds, because it requires admitting that the original answer did not work. Do it anyway. The next person who finds the thread needs the correction more than you needed your ego protected.

The Part That Is Hard to Say Nicely

Some of the people who ask bad questions are not going to read this article, and if they did, they would not see themselves in it. That is fine. This article is not really for them.

It is for the person who has been in a group for a while, notices the patterns, and wants to do better. It is for the person who has asked a question recently that did not get the response they hoped for, and is wondering why. It is for anyone who has ever felt the low-grade frustration of watching a thread devolve because the original poster did not give anyone enough to work with.

Asking good questions is a professional skill. It is worth developing. The people who do it well get better answers, build stronger networks, and spend less time stuck. That is a real competitive advantage in any field.

It is also a skill that quietly signals everything else about how you work. People who ask precise, well-scoped questions in public are usually the same people who write good emails, run good meetings, and produce good work. The reverse is also true.

The way you ask a question in a Facebook group is a tiny window into how you operate everywhere else. People notice. They form opinions about who they would refer work to, who they would hire, and who they would partner with. None of this is fair, but all of it is real.

And if you are on the answering side, remember that you were a beginner once, too. A short reply pointing someone to the search function is more useful than a long reply about how they should have searched. We are all trying to get better at this.

The groups that thrive are the ones where the people asking questions take the time to ask them well, and the people answering take the time to answer kindly. That is not complicated. It is just rare. Be the kind of participant that makes the place better for everyone else, and the place will be better for you when you need it.

Examples

Let’s talk about a few examples. I am changing names to protect the guilty

“OMG! My client got a CP53E notice. They owed and paid, and this is asking about their refund! Has anyone else seen this? What is going on? Clients are calling me!

Yes, in fact, we have seen this. Had you utilized a search, you would have seen that 7 other people had similar fact patterns this week. This one is popping up daily and is admittedly annoying me.

“You really need some education. Are you new? Everyone knows this, and you are wrong!”

I won’t mention the lady who does this routinely in certain Facebook groups. But it isn’t helpful, and some of us may talk about you.

Then there is “Mr. I’m confidently wrong and have been wrong the last 32 years, but I have some other credentials that are unrelated to this, and I will throw them in because I need validation. Then I will argue with you, throw in a bunch of facts and personal stories just because.”

No, just no.

If you recognized yourself in any of those examples, you are not alone. Everyone has been at least one of those people at some point. I have probably been all three on different days. The point is not to feel bad about it. The point is to notice the pattern and choose differently next time.

Asking well is a small discipline. So is answering well. Neither is hard, but both require a moment's pause before you hit post. That pause is the whole game.

The next time you are about to ask a question, take a beat. Search first. Write the question. Read it back. Ask whether a stranger could answer it without interviewing you. Then post.

The next time you are about to answer one, take a beat. Read the question carefully. Check the source. Resist the pull to be first. Ask whether the answer you are about to post would help the asker, or just make you feel useful.