A topic in the Open Knowledge Graph — a free, open map of 15,290 topics and the order to learn them in.
Peer review is a structured process in which writers read and respond to each other's drafts, serving two purposes: providing the writer with an outside perspective that identifies issues invisible to the author, and training the reviewer to read critically — a skill that transfers directly to revising their own work. Effective feedback is specific (pointing to particular passages rather than offering vague impressions), descriptive (explaining what the reader experienced rather than prescribing fixes), and prioritized (focusing on the most consequential issues rather than cataloging every flaw). Learning to receive criticism without defensiveness is equally important, because the instinct to explain or justify rather than listen undermines the review's value.
Use structured peer review prompts — "What is the thesis? Where does the argument feel weakest? What evidence is most convincing?" — rather than open-ended "give me feedback" requests, which produce vague responses. Practice writing a feedback letter that identifies two strengths and two areas for development, each with specific textual evidence. After receiving feedback, practice writing a revision plan that translates peer comments into concrete changes before returning to the draft.
You already know from revision strategies that good revision requires distance — the ability to read your own draft as a stranger would. The problem is that writers accumulate intentional blindness as they draft: you know what you meant to say so thoroughly that you cannot see what the text actually says. Peer review solves this problem by introducing a reader who genuinely does not have your intentions in their head. Their confusion, their slowing down, their re-reading — these are data. The peer reviewer's job is not to fix your draft but to report their reading experience honestly.
This means that the most valuable feedback is often not prescriptive but descriptive. "Your argument gets confusing around paragraph four" is more useful than "you should restructure paragraph four," because the first tells you where the problem is experienced and lets you diagnose the cause, while the second might push you toward a structural change that doesn't address the real issue. Descriptive feedback keeps the decision-making with the writer, where it belongs. Prescriptive feedback often reflects the reviewer's preferences rather than the writer's actual problem. The question to ask as a reviewer is not "what would I do?" but "what is this draft doing and where does it stop working for me?"
Learning to receive feedback without defensiveness is harder than learning to give it. The natural instinct when someone identifies a flaw in your argument is to explain what you meant — but that explanation is exactly the information your draft failed to communicate. If you have to explain, the draft hasn't done its job. When you hear yourself wanting to say "well, what I was trying to say was..." stop, write it down, and ask why the draft didn't convey that. The reviewer's confusion is a feature, not a bug: it shows you what is invisible to you.
The review cycle also makes you a better writer for a structural reason: critical readers internalize the moves of good feedback. When you practice asking "where is the thesis?", "what is the warrant for this claim?", "where does the evidence feel thin?" — you are installing a checklist that runs automatically as you draft and revise. The skills transfer directly. Writers who have done serious peer review typically find that their self-revision becomes sharper because they have learned to read their own work through a reviewer's eyes. Peer review is, in this sense, a form of writing education disguised as a collaborative exchange.