A critique of the article is not a critique of you.
It is feedback on your work that is not fully formed yet.
That distinction matters because writers get attached to drafts. Time creates attachment. Attachment makes edits feel personal.
Editors are trying to solve a publishing problem because the angle is weak, the pacing drags, the point is unclear, or the evidence is thin.
What Editors Usually Mean
Editors leave useful notes across dozens of drafts, and most writers misread them because they hear judgment where the editor meant direction.
A few common ones:
-
"Missing stake?"
This means the paragraph explained a concept but not say why the reader should care. Usually the fix is one sentence connecting the point to a real consequence, problem, or decision.
-
"Needs data"
The claim sounds plausible but unsupported. The editor is not accusing you of making things up. They are flagging the point where a skeptical reader will stop trusting the article unless they see evidence. That evidence could be a number, a source, a direct example, a comparison, or a concrete outcome
-
"Cliche"
The concept has been used so often that readers stop processing it. The editor wants the actual idea underneath the stock wording.
-
"Unclear"
This usually does not mean the sentence is poorly written. It means the sentence assumes knowledge the reader does not have. One additional clause or a concrete example usually fixes it.
-
"Cut"
Cut is rarely about the quality of the writing in that section. It is usually about pacing, redundancy, or editorial scope. A cut section in one article is sometimes a different article entirely.
Most cuts happen because:
- The section repeats something earlier
- The pacing slows down
- The point belongs in another article
- The publication has length constraints
When to Push Back
Disagreeing with an editor is legitimate. What’s important is knowing what is worth pushing back on.
The rule is simple: push back on meaning, not preference.
If an edit removes a nuance you think is important, explain what the reader loses without it. Not why you liked the original phrasing, but what the edit costs the reader. That framing is easier for an editor to act on.
If you disagree with a stylistic choice, let it go unless it changes the meaning. Style is the editor's domain. Accuracy is yours.
One pushback per round of edits is a reasonable ceiling. Two is tolerable. More than that, the relationship shifts from collaboration to negotiation, which benefits neither the piece nor your next pitch.
Confusing the two makes collaboration harder.
Keep a Feedback Log
Most writers treat each round of feedback as a standalone event. They fix what the editor flagged, file the piece, and move on.
The problem is that the same mistakes come back in the next draft, and the one after that.
A post-mortem log fixes this. After each round of edits, add three things to a running document: the type of comment received, the section it appeared in, and the underlying cause.
Over four or five pieces, patterns become visible. Maybe the structural notes cluster in conclusions. Maybe the "so what" comments appear most often in the middle sections, which suggests the argument loses purpose halfway through.
Once you can see the pattern, you can check for it before submitting.
Editors remember writers who fix things. They also remember writers who send back the same problems in different clothes.
What Feedback Actually Means
Writers who treat feedback as data improve much faster than writers who treat it as judgment.
A marked-up draft shows the gap between what you intended to communicate and what the reader actually received. That gap is the work.
Close it. Submit the revision. Learn the pattern. Then carry that lesson into the next draft.
Smart writers use feedback to improve faster!
Want to take this further? (HackerNoon’s Blogging Course)
HackerNoon’s Blogging Course is designed for beginners and writers who’ve published a bit and want to level up. It’s organized into 8 modules created by experienced writers and editors, and it includes topics like:
How to Find Your “Voice” and Ideal Writing Workflow SEO + Storytelling: Write Content That Ranks and Resonates How to Write Great Articles That People Will Read
Sign up for the
That’s it for today.
Until next time, Hackers!