Last week we did draft feedback. Students brought pages they’d written, paired up, read each other’s work, reported what they received. The standard ritual of writing workshops everywhere.
Except we tried to do something different. We asked readers not to interpret what the writer meant, but to report what they actually received. Not “I think you’re trying to say X” but “Here’s what I understood.” Not “this is good” or “this needs work” but “here’s where I saw instability” and “here’s where I didn’t see costs.”
It usually works. Students learn something about the gap between what they thought they were communicating and what readers receive. They see where their instabilities aren’t visible, where their costs aren’t explicit, where their implied readers aren’t clear.
But I keep thinking: What if the most useful thing readers could tell you is precisely what they can’t tell you?
When we talk about feedback, we assume readers can help you fix your writing. And in certain limited ways, they can. They can tell you where they got confused. Where they lost the thread. Where they stopped caring. Where a sentence didn’t make sense. Where they couldn’t see the instability you thought you’d constructed.
This is valuable information. It’s data about reception. It tells you: what you thought you communicated didn’t land.
But here’s what readers can’t tell you: what you should write instead.
They can tell you where the instability isn’t visible. They can’t tell you how to make it visible—because they don’t know what you’re trying to make visible. They only know it didn’t work.
They can tell you where costs aren’t clear. They can’t tell you what the costs should be—because they don’t know what your project is trying to accomplish. They only know they don’t see stakes yet.
They can tell you where they couldn’t identify the readers. They can’t tell you who your readers should be—because they don’t know what community you’re trying to serve. They only know they don’t recognize themselves.
We call this “feedback” as if readers are feeding something back to you. But what they’re actually doing is reporting a negative: something is missing. Something didn’t work. Something wasn’t there.
The positive—what should be there instead—that’s still your work. That’s the work readers can’t do for you.
Here’s the paradox: you need readers to see what’s not working. But once you know what’s not working, readers can’t tell you how to fix it.
This is why feedback often feels simultaneously essential and useless. Essential because you can’t see the gaps yourself—you’re too close, you know what you meant, you can’t read your own work as a stranger would. Useless because once readers point out the gaps, you still have to figure out what to put there.
And the real problem—the one we rarely talk about—is that often the gap readers identify isn’t actually a gap. It’s a sign that your whole frame is wrong.
Let me give an example. A student wrote about noticing Syrian shops in Neukölln. Their reader said: “I don’t see the instability. You’re describing things but I don’t see what doesn’t fit.”
The easy interpretation: the writer needs to make the instability more explicit. Just state it clearly in paragraph one. Problem solved.
But what if the problem isn’t that the instability is unclear? What if the problem is that there isn’t an instability—not yet, not in the way the writer is framing it? What if the writer is trying to create a problem out of something that isn’t actually a problem for anyone except the writer?
The reader can’t tell you this. The reader can only report: “I don’t see it.” But they can’t tell you whether you need to make it clearer or whether you need to find a different tension entirely.
That’s still your work. And it’s the hardest work.
We’ve built an entire culture around feedback in academia. Peer review. Writing groups. Draft exchanges. Advisor comments. Workshop sessions. Feedback is everywhere.
And much of it is genuinely helpful. I’m not arguing against feedback. I’m arguing that we’ve overclaimed what feedback can do.
We talk about feedback as if it solves (writing) problems. As if the right feedback will tell you what to do. As if readers who understand the gaps can tell you how to fill them.
But most feedback doesn’t solve problems. It surfaces them. And surfacing problems is not the same as solving them.
The solving part—figuring out what instability you’re actually tracking, what costs actually matter, who your real readers are—that’s a different process. That’s not feedback. That’s writing.
And here’s what makes this hard: the better the feedback, the more it reveals how much work you still have to do. Bad feedback tells you you’re almost there, just fix these small things. Good feedback tells you the problem is deeper than you thought.
Good feedback is the reader who says “I don’t see why anyone would care about this” and means it. Not as an insult. As information. As the honest report that whatever you thought you were establishing—instability, costs, reader investment—didn’t land.
And then you’re back at the beginning. Not revising. Rethinking.
There’s another problem with feedback culture: it assumes the text you brought is close to the text you should write.
The whole feedback apparatus is designed for refinement, not transformation. We mark up drafts. We suggest changes. We point to specific sentences that need work. This all assumes the basic frame is right and just needs tweaking.
But what if the frame is wrong?
What if you’re writing for the wrong readers? What if your instability isn’t actually the interesting instability? What if you’re trying to solve a problem no one has rather than identifying the problem people are actually struggling with?
Readers can’t tell you this. Or rather, they can—they can say “I don’t find this interesting” or “I don’t see who this is for”—but they can’t tell you what you should do instead. Because they don’t know what you’re trying to do. They only know this isn’t it.
The feedback that would actually help—”your whole project needs to be different”—is both true and useless. True because the frame is wrong. Useless because knowing the frame is wrong doesn’t tell you what the right frame is.
You have to find that yourself.
Here’s what I think happens: We use feedback to outsource the anxiety of not knowing if our writing works.
We bring drafts to readers hoping they’ll tell us: yes, this works, keep going. Or: here’s what’s wrong, fix these three things, then it’ll work.
We want feedback to settle the question of whether we’re on the right track. We want readers to give us permission to continue, or clear instructions for how to improve.
But readers can’t give you this. They can only report their experience. And their experience might be “I don’t know what this is” or “I don’t see why this matters” or “I’m not your reader.”
None of which tells you what to do. All of which leaves you back where you started: uncertain.
The anxiety doesn’t go away with feedback. It just gets more specific. Before feedback: “I don’t know if this works.” After feedback: “I know this doesn’t work but I don’t know why or how to fix it.”
Is that better? Sometimes. Sometimes it’s worse.
So what do we do?
I don’t think we stop doing feedback. Readers are essential. You can’t see your own work clearly. You need to know what’s landing and what isn’t.
But maybe we need to be more honest about what feedback is and isn’t.
Feedback is data about reception. It tells you what readers received. It doesn’t tell you what to write.
Feedback surfaces gaps. It doesn’t fill them.
Feedback tells you where you’re not yet communicating what you think you’re communicating. It doesn’t tell you whether what you’re trying to communicate is worth communicating.
Feedback is about the text as it is. It can’t tell you about the text you haven’t written yet, the text that emerges when you realise your whole frame is wrong and you start over.
And maybe most importantly: feedback can’t tell you whether to keep going. Only you can decide that. Readers can tell you “this doesn’t work yet.” They can’t tell you whether it’s worth the work to make it work.
Last week, students hopefully learned that what they thought they were communicating and what readers received were different. Good. That’s the value of feedback.
But the next part—figuring out how to close that gap, or whether to close it, or whether to abandon this approach entirely and try something else—that’s not feedback work. That’s writing work.
And writing work is lonely. It’s you and the draft and the question that won’t go away: is this worth doing? Am I tracking something real? Does this matter to anyone?
Feedback can’t answer these questions. It can only make them more precise.
Which might be the most honest thing feedback can do: not solve your writing problems, but clarify what the problems actually are.
And then you’re back to writing. Alone. Figuring it out.
Which is, maybe, exactly where you need to be.