Friends and Family Make Terrible Beta Readers
When you tell people you are writing a book, one of the first things they tend to say is that they would love to read it. This is encouraging, particularly during those years when the book exists mainly as an increasingly large Word document and a vague promise that you will finish it eventually.
Then you finish a draft, send it to them and discover that wanting to read a book and wanting to read an unfinished manuscript are not quite the same thing.
A book asks for a reader’s attention. A manuscript arrives with responsibilities. If you are honest with yourself, do you really think someone will stare at their screen for hours on end reading your drafted chapters? People like to hold books, not unpolished works from their cousin.
It cannot simply be enjoyed or abandoned in the way a normal book can. The person who sent it to you is going to ask what you thought, whether the characters worked and why you went strangely quiet after chapter fourteen. You are no longer reading for pleasure. You are holding several years of someone’s life in your hands, and that someone may be sitting across from you at Christmas dinner.
This is why friends and family often make terrible beta readers.
I do not mean they are terrible readers. I certainly do not mean they are terrible friends or family members. The problem is that the relationship they have with you makes it almost impossible for them to have a straightforward relationship with the book.
Reading because they love you
Most writers begin with the people closest to them because those are the people most likely to say yes. Asking strangers to read 150,000 words of unfinished fantasy feels like a considerable request. Asking your friend feels safer, particularly if you have listened sympathetically to several years of updates about kingdoms, wars and characters they can no longer pretend to remember.
The trouble is that many friends and family members agree to read your manuscript because they love you, not because they desperately want to read that particular kind of book.
Those motivations are not the same.
A person can be incredibly supportive of your writing without enjoying fantasy. They may be thrilled that you have finished a novel while having no particular desire to spend several evenings learning why the Northern Kingdom has not trusted the Southern Kingdom since the Treaty of Something-or-Other.
This creates a strange obligation for everyone involved. The writer waits for feedback while trying not to ask for feedback. The reader watches the manuscript sitting on their bedside table and feels increasingly guilty about the fact that they are reading almost anything else.
Eventually, one of you breaks.
“So, have you had a chance to start it?”
“I have. I’m really enjoying it.”
“Where are you up to?”
There is then a pause long enough to suggest that the answer may be “the first chapter.”
My wife did not read Shadows Before the Dawn while I was writing it. I spent more than eight years working on the book, and she managed not to touch it for almost the entire time. I must make a disclaimer before she murders me, that she did let me read her most of the chapters as I wrote them. She was my biggest fan, and helped push me to the finish line, but she didn't read those drafts. She eventually read it after it was published and told me she loved it, which was reassuring (and she kind of has to say that).
In truth, I never needed her to be my beta reader. I needed her to tolerate the time I spent writing, listen when I disappeared into some invented problem and occasionally remind me that most of the pressure I felt was coming from me. That support was far more useful than forcing her to provide notes on chapter seven.
The people closest to you do not have to become part of your editorial department simply because you decided to write a book.
“I liked it” is lovely but not particularly useful
The kindest beta readers are often the least helpful because they know how much the book matters to you. They have seen the work behind it, heard about the sections you rewrote and watched you become disproportionately excited when you finally solved a plot problem that meant absolutely nothing to anybody else.
When you ask what they thought, they naturally want to reassure you. They tell you they liked it. They say the characters were good. They might even use the word “gripping,” which is always nice to hear and almost impossible to turn into an edit.
The problem is that beta reading is not really about deciding whether a manuscript is good or bad. It is about identifying the experience of reading it. Where did your attention drift? Which character did you care about? What did you think was going to happen? Which explanation made sense to the author but apparently nobody else?
“I liked it” answers none of those questions.
The opposite can be equally unhelpful. Someone may point at a single line and announce that it sounds strange, but they cannot explain why. They might insist that a character should make a completely different decision because that is what they would personally do. Occasionally, they will offer a solution so dramatic that accepting it would require you to remove half the book and possibly change genre.
This does not mean the feedback has no value. A reader does not need to understand story structure to recognise that something feels wrong. If several people lose interest in the same place, the problem belongs to the manuscript even if none of them can diagnose it.
However, one person disliking a scene does not automatically mean the scene is broken. It may simply mean that person does not like that sort of scene. Part of being a writer is learning the difference between a pattern and a preference, which becomes particularly difficult when the person giving the preference is someone whose opinion matters to you well beyond the book.
A normal reader and a beta reader are not the same thing
One of the points Chris made when we discussed this on the podcast was that friends and family are often simply members of the potential audience. They are not necessarily writers, editors or experienced beta readers, and there is nothing wrong with that.
We do not ask readers to explain why every book works. Most people know when they are enjoying something without needing to examine its pacing, character arcs or narrative structure. I have loved plenty of novels without stopping halfway through to make notes on the efficiency of their second act.
Beta reading asks for something different. It asks someone to pay attention to their own reaction and then communicate it honestly. That is a skill, and like most skills, people improve through experience.
A useful beta reader does not have to be a writer. In fact, writers sometimes make difficult beta readers because we cannot resist rewriting the book we would have written instead. A good beta reader understands what your story is trying to be and responds to that story rather than quietly converting it into their preferred version.
They can tell you where they became confused without demanding another page of explanation. They can recognise when a chapter feels slow without insisting that someone be murdered before page five. Most importantly, they can separate “this did not work for me” from “this is objectively wrong,” because those are very different pieces of feedback.
Finding someone who can do this consistently is difficult. Finding several people is even harder, which is why writers occasionally begin to understand those oddly formal critique groups with application forms, waiting lists and what appears to be a small admissions department.
Chris once tried to join a writing group that had several rounds of questions before politely declining him. At first, that sounds excessive for a group of people sitting around discussing imaginary characters. Once you understand how much trust is involved, it makes considerably more sense.
A good critique group has to protect the way its members work together. People need to be honest without being cruel, confident without taking over and willing to give as much attention as they receive. One person with the wrong approach can change the entire atmosphere.
Chris eventually found a stable critique group in Korea, and their feedback helped him reshape the beginning of his manuscript. That is what useful criticism can do. It does not simply tell you that the book is good. It helps you see the version of the book that is trying to emerge from the draft.
Ask better questions and you may get better answers
Writers often make the feedback process harder by asking a question that is almost designed to produce a useless response.
“What did you think?”
That is an enormous question. It invites everything from a detailed editorial letter to “Yes, it was good,” depending on how frightened the reader is of the look on your face.
More specific questions give people somewhere to begin. Where did you feel most interested? Was there a point where you wanted the story to move faster? Which character did you understand best? Was anything confusing? Did the ending feel earned? Were there moments when you expected something to happen and it did not?
I would also ask what the reader remembers a few days later. The answer can be revealing because it shows which characters, scenes and ideas survived after the smaller details had disappeared.
This does not mean sending readers a questionnaire long enough to qualify as a second manuscript. A few good questions are enough, and you should give them permission to be honest before they answer.
You also need to mean it.
Writers often say they want honest feedback when what they really want is detailed praise. I have certainly had moments when I asked for an opinion and then immediately began explaining why the person’s opinion was wrong. This is not an especially effective way to encourage further honesty.
You do not have to accept every suggestion, but you should understand the reaction behind it. If someone proposes removing a character, the answer may not be to remove the character. The important question is why that reader felt the character was unnecessary.
Feedback is evidence, not an instruction.
When a friend becomes a critique partner
There is an obvious complication in all of this because one of the most valuable readers I have had is also one of my closest friends.
Chris is not useful because friendship secretly makes someone a perfect beta reader. He is useful because our friendship developed a separate creative relationship with its own trust, language and expectations.
We have spent years discussing each other’s work. He knows the world of Shadows Before the Dawn, and I know the world he has created for his own manuscript. We understand what the other person is trying to achieve, but we are also comfortable enough to say when it is not working.
That did not happen because one of us sent the other a finished book and asked for a quick opinion. It developed through conversations, shared chapters, disagreements and the occasional idea that changed the direction of an entire section.
The exchange matters as well. Chris has spoken about how helping me solve problems strengthened his ability to examine his own work. I have found the same thing. It is often much easier to recognise a problem in somebody else’s story, and once you have recognised it there, you become slightly less capable of ignoring it in your own.
A critique partner is not simply a friend who is willing to read. It is someone who understands that protecting the writer and protecting the manuscript are not always the same thing.
Sometimes supporting a writer means telling them a section is not working. Sometimes it means questioning the idea they have spent weeks defending. Occasionally, it means listening to an explanation of an ordinary battle and saying, “Bring the giants in.”
Find the people who can tell you the truth
Friends and family can still be early readers. Some of them will be excellent at it, particularly if they already read widely in your genre and understand the kind of feedback you need.
But they should not be your entire test audience.
You need readers who do not know what you intended. You need people who cannot hear your explanation while they read and will therefore notice when that explanation is missing from the page. You need enough opinions to recognise patterns, but not so many that the book becomes an anxious collection of compromises.
Most of all, you need people who can be honest without making honesty feel like punishment.
Your family may love the book because they love you. Your friends may tell you it is brilliant because they know how hard you worked. Accept that support for what it is, because writing is lonely and encouragement matters.
Then find someone who is willing to tell you where they stopped believing the character, which chapter dragged and why the brilliant reveal you saved until page 400 made absolutely no sense.
That person may become one of the most important people in your writing life.
Just try not to make it somebody you have to sit next to at Christmas dinner.



Comments