Hearing What Did and Didn't Land

Someone reads your story and tells you the ending felt rushed. Your first reaction, if you're honest, is probably to defend it — to explain what you meant, or why it makes sense if they'd just read it the right way. That reaction is normal, and it's also the exact moment worth pausing at, because defending a piece of writing to the person reading it doesn't fix anything for the next reader, who won't be there to hear the explanation.

What a reaction is actually telling you

Here's the useful reframe: a reader telling you something didn't land isn't wrong about their own experience, even if their diagnosis of why is off. If someone says the ending felt rushed, they might be technically mistaken about which paragraph caused it — but the feeling of rushedness is real information, and it's yours to figure out where it actually came from, which might be three pages earlier than where they pointed.

This is also why one piece of feedback rarely needs to become one specific fix. If a reader says a character feels flat, the answer isn't necessarily to add more description of them — it might be giving them a want the reader can actually see them pursuing, or a contradiction that makes them harder to predict. The feedback names a problem; figuring out the fix that solves it is still the writer's job, not the reader's.

Not every piece of feedback deserves a change, and part of getting better at this is trusting your own read on which ones do. But feedback you dismiss without genuinely sitting with it first is feedback you're not actually learning from — you're just protecting the draft you already have.