How to ask for feedback people will actually give

To get feedback worth having, ask one named person about one specific decision, say how finished the work is, and give them a date. "Any thoughts?" is not a question. It is a door left open in the hope that somebody walks through it.

I ask badly by default. My instinct is to send the whole thing and wait, which is how you collect three replies saying "looks good" and one silence you then think about for a week.

Why "any thoughts?" comes back empty

An open ask hands the reader the hardest part of the job, which is working out what you need. Most people will not do that work, and the ones who try will guess wrong.

Sit on their side of it. A document lands with no question attached. They cannot tell whether you are proud of it, whether it ships tomorrow, or whether the part they dislike is the part you already fought someone else to keep.

In every one of those cases the safe reply is "looks good". It costs nothing and it starts no arguments. You built a situation where flattery is the sensible move, then felt let down when you got flattery.

Here is the test I use before sending any request. If I cannot name what I would change depending on the answer, I am not asking for feedback. I am asking for company.

Name the decision, not the document

Ask about the choice you are stuck on rather than the file it lives in. A decision has an answer. A document has a comment thread.

"Feedback on the pricing page?" gets you a note about the font. "I moved the questions above the quotes, does that read as hiding something?" gets you a real opinion, because there is exactly one thing to have an opinion about.

Narrow asks also signal that you did the work. Sending an open document says you have decided nothing and would like company while you decide. Naming the decision says you made a call and want to know if it holds.

Some shapes that work:

• "What was the first thing that confused you?" beats "was it clear?", because it assumes something confused them.
• "Where did you stop reading?" gets an honest answer, since it is a question about them and not about your work.
• "If this goes wrong, which part broke?" invites the objection they were being polite about.
• "Which of these two would you defend in a meeting?" forces a choice instead of a compliment.

Send it to a name

Send the request to one person. Posting "would love any feedback" to a channel of forty people reliably produces feedback from zero of them.

Everyone in a group assumes someone better qualified will answer. Everyone is right. Nobody moves. A direct message takes away the escape route without applying any pressure at all.

This is the one place I go against my own advice about asking for help, where the channel wins because anybody free can answer and the answer stays where the next person can find it. Feedback does not work that way. Nobody is free to read your draft, the answer is worth nothing to a stranger later, and a public request costs the reader something a private one does not, which is being seen to criticise you.

Who you pick matters more than how you word it. Choose for the gap you have: someone who will actually use the thing, or someone who got burned by this exact decision before, or someone who disagrees with you on principle and enjoys it.

I would rather have one grumpy reply than nine thumbs up.

Say what stage the work is at

Tell them how finished it is, because that one line decides what kind of note comes back.

Line edits on a rough outline waste an evening. Structural doubts about something that ships in an hour are worse, because now you both know and neither of you can do anything about it.

• "Rough shape, ignore the wording" invites arguments about the plan.
• "The structure is locked, I need the wording to land" keeps them out of the plan.
• "This goes out unless something is actually wrong" asks for objections only.
• "Nothing is decided yet" is useful when true and expensive when it is not.

Give a date as well. "By Thursday" tells them how much time to spend and hands them a clean way to decline, which is worth more to you than a reluctant yes that arrives two weeks later attached to an apology.

"Be brutally honest" does not work

Telling someone to be brutal does not make them brutal. It tells them you have thought about wanting honesty, which is a different thing from being safe to give it to.

I have said it plenty of times. I have also watched what came next, which was a warm note with one small suggestion in it.

What works is asking for the criticism in a form the person can hand over without being the one who decided your work is bad. Ask what the most skeptical reader would say. Ask which sentence a competitor would screenshot. You have given them a costume, and people will say things in costume that they will never say as themselves.

The other trick is asking what to cut. Cutting is concrete, and nobody has to insult you to point at a paragraph and say that one is doing nothing.

When I want to know whether a rewrite is any good, I stopped asking people what they thought of it. I ask them to type their angriest message into Unvent and tell me whether the Direct version is one they would actually send. That question gets answered. The other one got me "looks clean" for months.

What you do with the answer decides the next one

Your reply to feedback is the price list for future feedback. Argue once and the next request gets a "looks good" like everyone else's.

Do not explain in the same message. The urge is enormous, especially when they missed context that you have and they do not. Say thanks, say what you understood, then go away and think.

Three ways to make sure nobody bothers next time:

• Explaining why they misread it teaches them to stop reading.
• Going silent after a long reply reads as rejection, whatever you meant by it.
• Saying "great point, will do" and then changing nothing burns a good reader for good.

Come back later with what actually changed. "I cut the second section, you were right that it was doing nothing" costs you one line and buys you a reader for years. People give feedback to be useful. Show them that they were.

Write the ask like it matters

The request itself is a piece of writing, and a mumbled one gets a mumbled answer.

Mine come out of my hands wrapped in padding: no rush, only if you have time, whenever suits. All of that tells the reader the thing does not matter much, and then the reply matches the question. Keep the manners. Put the actual question in a sentence of its own, and name the day.

Then ask earlier than is comfortable, while the work is still ugly enough that changing it is cheap. Most people do the opposite and only ask once a thing is finished, which is the exact point at which the answer can no longer cost them anything. That is not a request for feedback. It is a request for permission to stop.