How to get and use feedback on your writing

Most writers get bad feedback because they ask a bad question. "What do you think?" invites politeness, and politeness is useless. The person then says "I liked it", and you have spent a favour and learned nothing.

Getting useful feedback is a skill you control almost entirely, and it starts before anyone reads a word.

Ask a specific question

Tell the reader what stage the draft is at and what you want. Then ask two or three questions, not ten.

• "This is a first draft — I only want to know whether the argument holds. Ignore the sentences."
• "Where did you get bored? Just mark the line."
• "Did you believe the ending? Yes or no is enough."
• "What do you think this piece is about?" — the single most revealing question you can ask, because the gap between their answer and your intention is the whole problem.

Never ask "is it good?" It is not answerable and it invites reassurance.

Choose the right reader for the stage

Early, structural: someone who reads in your genre and will engage with the shape. Not a line-editor; they will fix commas in paragraphs you are about to delete.

Middle: two or three readers, including at least one from your actual audience rather than your writing circle.

Late, line level: someone precise. This is where a good copy-editor earns their fee.

Never: someone who will only reassure you, or someone whose approval you need for other reasons. Partners and parents are usually both.

Hearing it

Your first reaction to real criticism is a physical one and it is not information. It passes in about a day. The rule is simple: do not respond to feedback for twenty-four hours beyond "thank you, this is helpful."

Do not defend the piece in the room. Explaining what you meant is satisfying and it is a waste of the session — you will not be able to explain it to a reader who buys the book. If they misread it, the misreading is the data.

Take notes on everything, including notes you are certain are wrong. Some of them will look different in a week.

Deciding what to act on

The most useful rule in workshopping: readers are reliable about what is wrong and unreliable about how to fix it.

When someone says "this scene is boring, add a fight", the diagnosis is trustworthy and the prescription probably is not. Something is wrong with that scene. It is very likely not the absence of a fight.

Then weigh:

• Two or more readers flag the same place — it is real, whatever their explanations. Fix it.
• One reader, and it names something you already suspected — it is real. You knew.
• One reader, and it contradicts your intention entirely — consider whether they are your audience. If they are not, note it and move on.
• A note that would turn it into a different piece — decline it. Deliberately, not defensively.

You are not obliged to take any single note. You are obliged to be honest with yourself about which ones you are rejecting because they are wrong and which because they are hard.

Giving it, briefly

Say what the piece is doing before you say what it is not. Be specific about location — "page four" beats "somewhere in the middle". Frame reactions as reactions: "I lost track of who was speaking here" is usable; "this is confusing" is not. Do not rewrite their sentences into your voice. Answer the question they asked.

Common mistakes

Sending a draft too early, then being derailed by structural notes on something unfinished. Sending to ten people at once and being paralysed by contradictions. Asking only people who like you. Arguing. Acting on every note, which produces a piece with no author. Acting on none, which wastes everyone's time. Never telling readers what you did with their notes — the fastest way to lose them.

Practical tips

• Keep a feedback log: the note, the reader, and what you decided. Patterns across projects are where you actually learn.
• Give it a week before revising. Distance does what argument cannot.
• Return the favour promptly and well. Good readers are rare and they are earned.