

One of the most common problems I encounter as a developmental editor is something I call author blind spots. These happen when writers know their characters, worlds, and stories so intimately that they forget how much of that knowledge never actually makes it onto the page.
Sometimes, the author simply knows too much.
They know their characters' childhood traumas, their complicated family histories, and the exact moment a friendship turned into a rivalry. They know the political structure of their fantasy kingdom, why two neighboring countries have been at war for centuries, and what really happened to the protagonist's missing mother.
They know things that never even make it into the manuscript. And that's where the trouble begins.
Because while the author has spent months, sometimes years, living inside this world, the reader is arriving for the first time. They don't have access to the character biographies, the elaborate timelines, or the dozens of conversations the author has imagined but never written.
They only have what's on the page. And sometimes, what's on the page isn't quite enough.
One of the most common issues I encounter during developmental edits is a character whose behavior makes perfect sense to the author but leaves the reader scratching their head.
Perhaps a protagonist refuses to trust someone who has repeatedly demonstrated loyalty. Or a character reacts with disproportionate anger to an otherwise innocent comment. Maybe a romantic relationship shifts from antagonism to affection without the emotional groundwork necessary to make that transition believable.
When I flag these moments, the author often has an immediate explanation.
"Well, she's afraid of abandonment because her father left when she was seven."
Or, "He doesn't trust her because she reminds him of someone who betrayed him years ago."
Those are perfectly reasonable explanations. There's just one problem. None of that information is in the book.
The author has been writing with the benefit of knowledge the reader doesn't possess. What feels like a natural progression to the person creating the story can feel abrupt, confusing, or even contradictory to the person reading it.
And readers can't connect the dots they haven't been given.
This is where things get tricky, particularly for writers working in fantasy, mystery, and other genres where withholding information is part of the storytelling.
You absolutely do not need to explain everything. In fact, you shouldn't.
Readers enjoy uncertainty. They want to speculate about motives, question loyalties, and discover secrets alongside the characters. A little confusion can create wonderful tension.
But there's a difference between making readers wonder why something happened and leaving them unable to understand what is happening.
In the first, a character refuses to enter a particular room. Their hands tremble whenever they pass the doorway, and they become visibly uncomfortable when someone mentions the room's former occupant.
The reader doesn't know why, but they recognize that something important is happening. The mystery is intentional, and the author has given them enough context to become curious.
In the second scenario, a character refuses to enter the same room, but there's no hesitation, no emotional reaction, and no indication that the refusal matters. Three chapters later, their unwillingness becomes central to a major confrontation.
The author knows exactly why the character avoided the room. The reader, however, may feel as though an important piece of the story has been left out. They are pulled out of the story trying to wonder what they are missing.
The difference isn't how much information the author reveals. It's whether the reader has enough information to understand the significance of what's happening.
You can withhold answers without withholding context.
This problem isn't limited to character development. Fantasy and science fiction writers are particularly vulnerable because worldbuilding often involves creating far more information than will ever appear in the finished novel.
And that's a good thing. A well-developed world should feel larger than the story taking place inside it.
But sometimes writers become so familiar with their world's rules that they forget those rules aren't obvious to everyone else.
A character might make a dangerous bargain with a supernatural creature, for example. The author understands that breaking such a bargain carries terrible consequences because they've established an entire magical system around these agreements.
But if the reader hasn't been shown or told enough about those consequences, the character's fear may feel exaggerated.
The opposite can happen, too. A character uses magic to solve a seemingly impossible problem, and the author knows the ability has existed all along. Unfortunately, the reader has never encountered it before.
Instead of feeling impressed by a clever solution, they may feel cheated.
The solution isn't to dump three pages of magical history into the opening chapter. It's to establish the information readers need before they need it. A warning from another character. A small demonstration of a magical limitation. A seemingly inconsequential consequence that becomes much more important later.
Often, a few carefully placed details can accomplish more than an entire paragraph of explanation.
The difficult part is that these gaps are often invisible to the author. You've read the manuscript countless times. You know what's coming. You remember scenes that existed in earlier drafts, even if you've since removed them. You may even remember conversations between characters that happened entirely in your imagination.
Your brain automatically fills in the missing information. Unfortunately, your reader's brain can't.
Here are a few ways to catch those author blind spots before they become problems.
When a character makes an important choice, ask yourself what the reader knows at that exact moment. Not what they'll learn five chapters later, and not what you know from your character notes.
What information is actually available to them?
If the decision depends on knowledge they don't have, consider whether you've provided enough emotional or situational context to make the choice believable.
Relationships rarely change overnight without a reason.
If two characters go from distrust to friendship, or attraction to love, look for the moments that earn that progression. Sometimes authors have imagined an entire relationship developing between scenes, only to discover that the reader has witnessed very little of it.
You don't need to document every interaction, but the important shifts need to happen where readers can experience them.
If a beta reader asks why a character did something, resist the urge to immediately explain it. Instead, ask yourself why the answer wasn't apparent from the manuscript.
That doesn't necessarily mean you need to spell everything out. Sometimes the reader has overlooked a detail. Other times, the explanation exists only in your head.
The distinction matters.
This is one I encounter frequently during developmental edits. I'll question a character's reaction or a plot development, and the author will respond with a wonderfully detailed explanation of the circumstances leading up to it.
Sometimes that explanation is more compelling than what's actually on the page.
When that happens, I encourage the author to look at how some of that missing context might be incorporated into the story itself. Not all of it. Just enough to give the reader the same opportunity to understand the character that the author already has.
The goal of developmental editing isn't to make every motivation explicit, eliminate ambiguity, or explain away every mystery. It's to make sure the story provides readers with what they need to remain invested. Sometimes that means adding a line of dialogue. Sometimes it means moving a revelation earlier. Sometimes it means strengthening a character interaction so an emotional shift feels earned.
And sometimes it means recognizing that a brilliant piece of backstory you've been carrying around for three years never actually made it into the manuscript.
Writers should know more about their stories than their readers do. That's part of what gives fictional worlds depth and characters complexity. The trick is remembering that readers can only experience the story you've written, not the one you've imagined.
So beware of your author blind spots when you're writing.
So, writers, have you ever had a critique partner or beta reader tell you about an author blind spot?
Jenn Windrow once attempted to write a “normal” book—and promptly bored herself into a coma. So now she sticks to what she does best: writing snarky, kick-butt heroines, broody supernatural men, and more sexual tension than a vampire in a blood bank.
She’s the award-winning author of the Alexis Black novels and the Redeeming Cupid series, where the undead never sparkle and the drama is always delicious. Jenn moonlights as a developmental editor, helping other writers wrangle their wild plots and tangle-free prose.
When not arguing with her characters or muttering about Oxford commas, she can be found binge-watching trash TV, wrangling the slew of animals that live in her house (husband and teenagers included), or telling herself she’ll only have one more cookie.
You can find her at jennwindrow.com or lurking on social media where she pretends to be an extrovert.
Photo by Serge Taeymans on Unsplash
Copyright © 2026 Writers In The Storm - All Rights Reserved
When I beta read or do dev editing for other authors, I run across this a lot. I also see pages of backstory early in the book, slowing down the pace and making the readers wonder why they are being told a bunch of unnecessary info about someone they just met.
I have to remind them to weave small pieces of info into the action. It keeps the plot/pace moving AND it helps the reader get to know someone (or know about a place) like you would in the normal world- little bits at a time as things happen that may reveal the info naturally.
This is a great article and I plan to share the link for reference to my authors as needed. Thanks!
I find the same when I edit. It’s amazing how much someone else can see about your work that your blind to.
Jenn, for me, my best friends are the ones who can identify my blind spots. LOL!! Yes, all too often, I am so engrossed in my amazing (at least to me!) story that I think the reader knows everything that I do about a character. I even had that happen last week as I am digging out an older story I want to polish. My friend caught a hole the size of a semi-trailer truck that I hadn't even thought about. Score!
Thanks for the post. It's a good one for us to consider.
Sarah, of course your story is amazing! I find it true, no matter how rough the draft, that each author's story stems from an amazing seed, a concept I never would have dreamed of. I'm always fascinated to see how the author cultivates and nurtures that seed into full bloom.
When I send off my chapters to my critique partners, I always have an idea where my issues but, but they are so wonderful at helping me figure out how to fix them. I tell all my clients to find a close group of writing friends and share their work.
On #3: "a reader asks why a character did something ... sometimes the reader has overlooked a detail"
One of the members of the critique group I belong to has this problem. It is obvious that she rushes through the submissions (probably in the penultimate hour(s) before the critique meeting), instead of reading them carefully and thoroughly as they deserve. This is frustrating to a degree. But the rest of us accept her, because when she does slow down to read carefully, her points are often spot-on and useful to improve the work. Besides that, the concepts of her own stories are fascinating - we always want to know more! (Give a little, take a little ...)
I have two dev editing clients right now that have this same issue. It’s to the extreme end and I have to wonder if they didn’t read it all the way through before sending it to me. Or if they just know the world so well in their own head that they are unaware that they didn’t inform the reader.
I have been living with my characters for thirty years. So I know everything. But not everything belongs in this story, so I have this happen a lot. And the opposite happens too: I put in ideas the reader doesn't need for this book. The hard part is figuring out exactly how much of each thing is necessary and where it belongs in the story. It's like spooling out the different threads of a tapestry, so they all get woven together in correct amounts to make the whole. And it is not easy.
It’s a balancing act for sure. Especially if you write a continuing series. Too much backstory and you bore old readers. Too little and you confuse new ones.
True.
I am writing book 1. But I have been telling myself stories about these characters for a very long time. This is why I know so much, but a lot of what I told myself doesn't work in book form. For one thing, I didn't need to be fully consistent in my own head.
The advantage of never sending my beta reader anything I don't consider finished is that it is the first time she sees what I've written, and those questions will come naturally as she reads, if there are any.
Her confusion - as a reader - is my gold. It happens rarely, but it has a couple of times, and when I explain the confusion, I find exactly what you said: some forewarning piece isn't actually on a page somewhere. Since she hasn't seen it present and then removed and no longer there, she is fresh to the problem, and notices it on her first pass through a new chapter.
Fortunately, the hole is often very easy to fix.
Those fresh eyes are so important. Getting first hand knowledge is what is working and what isn’t. Where readers are confused. Bored. All of that is gold before you hit publish.
For the first draft of my first novel, my wife–who doesn't normally Beta my work–commented that in Part Three of my story my characters seemed to have suddenly known how to professionally operate some of the more serious alien technology they were bringing back to Earth.
Although I had in Part two shown them discussing the importance of learning the technology, I had never written any scenes really showing them trying. My wife's a prolific reader (and capable editor) so I value her opinion. So, upon review, I realized she was quite right. It resulted in the addition of two chapters, where they learned how to use two of the technologies which would become important throughout the series. As a plus, these chapters could show their early mistakes and their kidding of one another. These added to their personal characterizations and solidified the warmth and cooperation they shared with each other.
The good thing is that if you left needed details out, it is always easy to go back to earlier scenes and add foreshadowing.
That’s the joy of writing, most things can be fixed with adding more context.
Your self-editing posts make me SO HAPPY. Seriously. We aaaall struggle with things like this and, if we're lucky, we find those great critique partners and beta readers. Bonus if they're honest, but kind.
Thanks, Jenn!
I adore my critique partners. Honestly, I might have quit years ago if it wasn’t for them. They encourage me, even when they tell me my stuff is crap sometimes.
Letting stories rest has become a vital part of my process. After finishing a story, I put it aside and work on something else, and only take it up again once I’ve forgotten enough of the details, sometimes days, but more often months or even years later. It’s as close to an uninitiated reader as I can get. I can catch a lot of author blind spots that way.
That’s a great way to do it as well. It’s amazing how each writer has their own process that makes finishing a book easier for them.