In the old trades, an apprentice’s first pieces were never meant for sale. A carpenter’s first chair wobbled. A smith’s first blade went back into the fire. Nobody hung a price tag on the work a beginner made while learning how the tools behaved, and nobody thought that was cruel. It was how a craft got passed down.
A first novel is an apprentice piece. Self-publishing has hidden that fact under a tidy routine: write a draft, revise it a few times, send it to beta readers, hire an editor, hire a proofreader, publish. The routine looks professional. It gives a beginner a checklist and a feeling of progress. What it can’t do is turn a chair that wobbles into one you’d sell.
This week a traditionally published novelist laid this out in a writing group, and I agree with nearly every word of it. The writer has spent two decades teaching, editing and coaching, and calls the whole cycle dubious. I’ve been ghostwriting and publishing for a long time, and I’ve seen the same thing from the other side of the desk.
Why is a first novel almost never publishable?
You have to write a novel to learn how to write one. Nothing else teaches you how to hold a plot together across 300 pages, how to keep a character consistent from chapter two to chapter thirty, or how to pace a middle so readers don’t drift off. The first novel is where you find out what you don’t know.
That’s its job. Nobody expects a first chair to hold a dinner party.
So the first one is nearly never publishable. The exception is the author who spends an enormous amount of time on it, reworking it again and again over a period of years, sending it out, getting it back, rewriting it once more. Some of those books do come out good in the end.
It’s the slowest possible way to learn.
A faster way is to set the first novel aside and write another one. Then set that one aside and write a third. Somewhere in there, something good comes out, and you’ll know it when it does because you’ll finally have the skill to tell. Or you skip the apprenticeship entirely and hire a ghostwriter. Yes, that’s a plug, and I’ll own it.
The poster made a point about drafting that I see in client manuscripts all the time. Multiple drafts can make a weak book worse. Every pass leaves something behind: a subplot that got cut but still has a scene, a character whose motive changed in draft three and never got fixed in chapter one. The book turns into a collage of earlier versions.
Have you ever read a manuscript where the hero’s sister vanishes after chapter four? That’s a ghost from draft two. I wrote about working through drafts in revising your novel, and revision assumes the story already works. If the story doesn’t, revision just moves the furniture around.
Can beta readers tell what is wrong with a first novel?
Mostly, no. A beta reader can have read thousands of books, and every one of them was published. Somebody already cut it, fixed it and made it readable. An amateur manuscript is a different animal. Most of them are hard going, and a reader who has only ever seen finished books doesn’t have the tools to say why.
Nobody tells them the manuscript is bad, so they treat it like a real book and hunt for small fixes.
Here’s the trap. Beta readers are reading slop, and they know something feels off, but they can’t zero in on what. Nobody tells them the manuscript is bad, so they treat it like a real book and hunt for small fixes. One says the middle drags. A second reader found the villain flat, and a third loved the dialogue.
All of it misses the trouble with a first novel. The trouble is structural: no story, or a story that falls apart halfway through. Why would a reader catch that, when nobody ever showed them what a broken story looks like?
The poster described a writer whose many beta readers loved the manuscript and praised the prose. The book had no story. That’s the ceiling of beta reading on a first novel. Readers react to sentences, because sentences are what they can see. My Beta Reader Handbook covers how to get better feedback. I still say beta readers pay off on a manuscript that already works. A book that needs rebuilding needs somebody else. I made the same point in Getting Published: Proposals, Beta Readers and the Rest.
What an editor can and can’t do for a first novel
An edit was never built to fix an unworkable manuscript. In traditional publishing, a book gets edited once the publisher accepts it, when it’s already good enough to publish and needs a polish. If the author hadn’t learned to write yet, there was no deal and no edit.
Freelance editors get paid per project, so the self-publishing world flipped that order. A smart editor asks for a sample first. If the sample is amateur work, a good editor turns the job down. If the editor takes it anyway, there are two ways it goes. The editor rewrites nearly every sentence and becomes an uncredited co-author, or does a quick cosmetic pass that leaves a bad book a little less bad.
There’s a third option, and it’s the one I’d point a new novelist toward. A developmental edit is a deep dive into the whole book: structure, plot, characters and pacing. The editor sends back a long letter and notes on what works, what doesn’t, and what to change. Then you do the rewriting. Nobody polishes your sentences at this stage.
It tells you what beta readers can’t: whether the story holds up. And because you make the changes yourself, you learn the craft instead of renting it. I explained how the different editorial roles compare in book doctor vs. ghostwriter, and why a finished manuscript still needs an editor in why your manuscript needs a professional editor.
| Step | Built for | Can’t do |
|---|---|---|
| More drafts | Tightening a story that already works | Supply a story that isn’t there |
| Beta readers | Reader reactions to a nearly finished book | Diagnose a structural problem |
| Developmental edit | Diagnosing story, structure and pacing, with what to change | Do the rewrite for you |
| Line or copy edit | Polishing a book that’s already good | Fix a book without rewriting it |
| Proofreading | Catching typos and formatting slips | Anything about the story |
The second novel is where many authors stumble
I think the worst case belongs to a different author: the one who spent years on a first novel, got it right, and sold it to a traditional publisher or built a real following. Now there’s a second novel to write, and there’s a deadline, and readers waiting. So the author writes it fast to hit the date.
It’s crap. Is anybody surprised?
The second novel that sags is common enough to have a name: the sophomore slump. The first book had years of rewriting behind it. The second gets months, and the author discovers that the skill lived in the rewriting. The writer never had it on tap.
Then the third novel comes along, and it goes one of three ways. Some authors make a course correction and find their footing. Some get discouraged and never come back. And some make it even worse, because they’re writing to prove they can write instead of writing the story.
That’s the hidden cost of the long route. An author who learned on one book, rewritten for years, learned that book. An author who wrote four or five pieces of fiction learned how to write.
How should a new writer learn to write fiction?
I think the old way still works best. Learn to write before you attempt the novel, and show your work only to people who can judge it: a teacher, a working editor, a more experienced writer. The poster joined writing groups at 17 and wrote a first novel in one draft at 37. It sold as part of a multi-book deal with Macmillan. Twenty years of learning, then one draft.
Here’s the ladder I’d hand a beginner. Start with flash fiction. A complete story in under 1,000 words forces you to find the one scene that matters and land it.
Flash fiction is hard to write well. It’s also fast. You can draft one in an hour, edit it in another, and put it through dozens of revisions in a single day. A novelist finds out whether a structural choice worked months after making it. A flash writer finds out before lunch. No other form gives a beginner that many repetitions.
Write a bunch of those. Then read short stories, lots of them, and watch how a professional fits a whole arc into a few pages. Then write a few short stories of your own, then some longer ones, and then try the novel.
Five rungs from flash fiction to a first novel, with the rung most new writers start on marked in gold.
Short stories are harder than novels in one respect. You don’t have room to tie things up. A novel can wander for a chapter and recover. A short story can’t afford a wasted paragraph, so it teaches economy faster than anything else I know. I wrote more about that in short story techniques, and I post flash fiction on this site, like The Lighthouse Keeper’s Last Shift, because it’s still the best practice I know.
I’ll admit I didn’t take my own advice. My first short story, back in junior high, went to a gaming magazine and came back covered in an editor’s comments. Those comments taught me more than any class. But when it came to novels, I jumped right in and wrote one, and it turned out OK. I don’t recommend my route. I got lucky, and luck is a lousy teacher.
Your first novel is an apprentice piece. Write it, learn from it, then set it aside and write the next one. – Richard LoweShare on X
Do writing critique groups help new novelists?
They do, when the group is the right one.
The poster joined writing groups at 17, and twenty years of that made a one-draft first novel possible. A critique group does what beta readers can’t. The people around the table are writers, so they read your pages looking for where the story turns, where a character stops making sense and where a scene goes slack.
You critique their work too, every meeting. When you hunt for the problem in somebody else’s chapter, you train your eye faster than you ever will staring at your own.
A group also hands you a deadline. Pages are due on Tuesday whether you feel like writing or not. For a beginner working through flash fiction and short stories, that rhythm turns practice into a habit.
I ran a science fiction and fantasy critique group in Clearwater for about a year. The groups worth joining have at least one person in the room who knows the difference between a sentence problem and a story problem. A room full of beginners praising each other is a beta reader panel with snacks. Look for a group with published or working writers in it, or start one and recruit them. I covered what makes those groups work in writing critique groups.
My take
The poster is right. A first novel is practice, and no stack of beta readers or editors turns practice into a finished book. More fiction does. Write flash fiction and short stories first, and get a developmental edit from someone who can judge a story as well as a sentence. Then write the novel, set it aside if it isn’t there, and write the next one. And when the second novel comes due, give it the time the first one got.
When the apprentice piece is not the point
Not everybody wants to become a novelist. Some people have one story to tell and no interest in writing three practice books to earn the right to tell it well. That’s a fair choice. What they need is a collaborator who has already served the apprenticeship. A bigger editing budget won’t get them there.
If you want to keep learning, the Writing Hub collects everything on this site about the craft, from structure to revision. If you’d rather have the book written with you, my fiction ghostwriting service is built for that.
Either way, treat the first novel like the first chair. Sit in it, notice the wobble, and figure out why. Then build the next one.
The piece of advice every workshop gave me and nobody explained. Over a hundred before and after examples, so you can practice the skill on the page instead of guessing at it.
If you want the book without the years of practice novels, this is how working with a ghostwriter goes, from the first conversation to the finished manuscript.
