How to ask a good question in the forum and get useful answers

A good forum question gives the reader four things: the situation, what you did or said, what happened, and the specific thing you want help with. Put it in the community that matches the topic, give it a title that says what it's about, and keep names out. Vague posts like "how do I get better?" tend to get vague replies, and a post someone can answer in one reply tends to get one.

Why context matters

Strangers can't see your situation, so every detail you leave out is a guess they have to make. One guide on asking questions online, by Alex Piechowski of the software consultancy Rietta, recommends describing what you did and what you expected, saying what you've already tried, staying around for replies, telling people when you've solved it, and thanking the people who helped. It was written for software questions, so applying it to dating is an extension. It's advice from one source, not research.

Pick the community first

Where you post is part of the question. The forum has communities for field reports, openers, texting, dates, mindset, style, where to go and wins, plus city boards. The composer shows a line that says "Posting in" with the community name. Tap it to change it. The forum guide lists what each one is for.

Several of them have a hint in the writing box that works as a checklist:

• f/texting: "Paste the conversation (no names) and say where you're stuck."
• f/openers: "What did you say, where, and how did it land?"
• f/dates: "Where you went, how it went, what you'd change."
• f/wheretogo: "Where is it, when is it good, and why?"

Search before you post

Tap the search icon on the Forum tab, or inside a community to search just that one. Type at least two letters and results appear as you type. If someone asked the same thing last month, reading that thread is faster than waiting for new replies, and you can add your own details to it.

Write the title

The title can be up to 120 characters. Make it say the situation and the ask. Compare:

• Weak: "Help"
• Better: "She replied once, then nothing for 3 days. Do I text again?"
• Weak: "Opener question"
• Better: "Asking about someone's book at a cafe: how do I follow up?"

Write the body

Cover four points, in this order. The box allows 5,000 characters, but a few short paragraphs are plenty.

1. The situation. Where, when, how long you'd known each other, anything that changes the answer.
2. What you did or said. The actual words if you remember them. Copy a text thread in, without names.
3. What happened. How the other person reacted, in facts, not guesses about what they thought.
4. What you want. One question. "Should I send a second text, and if so what?" is easier to answer than "what did I do wrong?"

Example of a short post:

Title: First text after getting a number at a climbing gym. Too slow? Got her number Saturday after we talked about the route we'd both just tried. I texted Tuesday: "Hey, it's Dan from the gym. How's the finger after that overhang?" She replied with a laugh emoji and nothing else. Do I suggest a plan now, or wait for her to say more?

That gives a reader the timing, the exact message, her reply and a single decision to weigh in on.

Use the field report template for a night out

If your question comes from something you just logged, the app can start the post for you. After you log a Success or Rejected, a line reads "Logged:" with the outcome and a Share button that stays for a few seconds. If the log was saved offline, Share appears once it has synced. Tapping Share opens the composer in f/fieldreports with a title like "It went well" or "Got turned down" plus a rough time, and any note you wrote in the body. Your notes can be edited before you post.

The template has four headings:

• Where:
• What happened:
• What worked:
• What I'd do differently:

Post doesn't turn on until you've written a title and some detail beyond the empty template. How to write a field report has a longer example. To turn a field report into a question, finish "What I'd do differently" with the part you're unsure about and ask people about it.

Other tools in the composer

• Poll. Add two to four options when your question is a choice between them, like two different texts.
• Photos. Up to four. Think about who's in them before you post.
• @ mention. Your friends show up as suggestions, so you can ask someone directly.

Before you hit Post

Posts can't be edited or deleted after they go up. Check four things first: no real names or handles for the other person, no phone numbers, a clear ask, and nothing you'd mind a mutual friend reading. A quick reread catches most of it.

After you post

Read the replies as options, not orders. People will disagree, and that's useful. Reply to the ones that help, and say what you ended up doing. A follow-up like "I tried the second option and here's what happened" gives readers a reason to help the next person, and it makes your own thread worth coming back to. Replies are a place for facts and kindness. If something crosses a line, the report option on a post or person is there.

What to do next

1. Search the forum for your question before you write it.
2. Open + Post and check the "Posting in" line shows the right community.
3. Write a title that names the situation and the ask, under 120 characters.
4. Use the four-point body: situation, what you did, what happened, one question.
5. Strip names and numbers, then reread once.
6. Come back within a day to answer follow-up questions, and report what you did.

A night you logged can become a field report from the Share button described above. When it's your turn to answer someone else, how to give useful replies has a simple format.

Sources

• Rietta, "How to ask great questions online" (Alex Piechowski, first published July 10, 2018). A practical guide about technical questions. Limits: one author's advice, not a study, and not about dating.