Working with an editor is one of the most practically important relationships in a writing life, and one of the least discussed in terms of how it actually works. The discussion that does exist tends to focus on the writer’s experience of being edited — on how to receive feedback without defensiveness, on how to manage the emotional difficulty of having your work changed by someone else. This is real and worth discussing, but it starts from the wrong place. The writer who understands editing only as something done to them is in a passive position relative to a relationship that works best when both parties are active.
The more useful frame is that an editor is a collaborator — someone whose attention to the work produces something that the writer alone could not have produced. Getting the most from that collaboration requires understanding what an editor can see that the writer cannot, what the writer can see that the editor cannot, and how to use both perspectives to make the piece better.
What an Editor Can See That the Writer Cannot
An editor brings something to a piece that the writer fundamentally cannot bring: genuine ignorance of the writer’s intentions. The writer who reads their own work reads it partly through what they meant to say. The editor reads only what is actually there. This is the most valuable thing an editor does, and it is available only because the editor is not the writer.
The editor who says “I don’t understand this section” is not reporting a failure of their intelligence. They are reporting that the section, as written, does not communicate what it is trying to communicate. The writer who knows what the section is trying to say tends to read past this gap — to fill it in from their knowledge of the intention. The editor cannot fill it in, because they do not have the intention. Their confusion is data.
Similarly, the editor who says “this piece loses me at the third section” is telling the writer where the reader’s attention fails — which is where the piece is failing the reader. The writer may know exactly what the third section is doing and why it is essential. The editor is telling them that what the section is doing is not visible from the outside.
This is what makes editorial feedback most useful: it is not the editor’s opinion of the work but the editor’s report of their experience as a reader. The reader who was confused, or lost, or unconvinced — that is the data. What to do with it is the writer’s decision.
What the Writer Can See That the Editor Cannot
The editor’s ignorance of the writer’s intentions is a resource — but it is also a limitation. An editor who does not understand what a piece is trying to do can give feedback that is technically accurate as a report of their reading experience and wrong as a guide to revision.
The editor who says “this section is too long” may be right that something is wrong — the editor’s attention wandered — and wrong about the cause. The section may be doing something that requires its length, and the problem may be elsewhere: in the framing, in the preceding section, in an unexplained assumption that made the section harder to follow than it should be. The writer who revises by cutting the section has addressed the editor’s experience without addressing the actual problem.
This is why the writer’s job in working with an editor is not to implement the editorial feedback but to understand what experience the feedback is reporting — and then to decide, from their deeper knowledge of the piece’s intentions, what revision would address that experience without damaging what the piece is trying to do.
The writer who treats editorial feedback as instructions tends to produce revised pieces that are less coherent, because they have been changed in response to a reader’s experience without regard for the piece’s internal logic. The writer who treats editorial feedback as data — as reports of a reading experience that the revision needs to address — tends to produce better revisions.
How to Make the Collaboration Work
Working with an editor well requires a specific kind of conversation — one in which both parties understand their respective roles and what each can and cannot see.
When I receive editorial feedback, I read it twice. The first time, I read it for the experience it is reporting — where the editor was confused, where they lost the thread, where they were unconvinced. This is the data. The second time, I read it for the diagnosis — what the editor thinks caused the experience, and whether I agree. The diagnosis is often wrong even when the experience it reports is accurate, and the revision that addresses the experience accurately is often different from the revision the editor has suggested.
I also flag edits I disagree with before implementing anything. Not to reject them, but to understand them. An edit I disagree with is either an edit that is wrong — that would damage the piece — or an edit that is revealing something I cannot see because I am too close to the piece. The disagreement is worth investigating before it is either accepted or rejected.
Working with an editor is not a process of having your work corrected by someone who can see it more clearly than you can. It is a collaboration between two kinds of knowledge: the editor’s knowledge of what the piece communicates to a reader, and the writer’s knowledge of what the piece is trying to do. Neither is sufficient alone. Together, they produce the piece that neither could have made without the other.
The best editorial relationships are the ones where both parties understand this — where the editor does not try to write the piece and the writer does not try to ignore the reader.
