The Narrative Gardener

Category: Writing Topics

  • Grammar Rules vs. Authentic Voice

    Why Fiction Isn’t an Essay

    Pruned rose cane
    Pruned raspberry cane

    Sharing one’s work with a critique partner takes guts, and the wait for it to come back can be excruciating, not to mention the sinking feeling that blossoms when the file opens and it’s covered with colored text and lines. Sentence fragments marked wrong. Verb forms in dialogue flagged. Split infinitives highlighted. Every sentence that starts with “And” or “But” has a note in the margin.

    During the subsequent self-edit, the changes are made, perhaps reluctantly so, but in the name of improving the writing according to feedback. The fragments become full sentences. The initial conjunctions get folded into the sentence before.

    Now the characters sound like they’re reading from a grammar textbook instead of talking like people.

    Fiction isn’t an essay, and the grammar rules that serve clarity in academic (or journalistic) writing can kill authenticity in creative work quicker than a flame.

    Same Rule, Different Plants

    Pruning guides say to cut stems at a 45° angle above an outward-facing bud. That’s sound advice for a rosebush. Apply it to a summer-bearing raspberry cane, which fruits on second-year wood and needs the oldest canes removed near the ground instead, and the next year’s harvest is cut off while following the instructions perfectly.

    The rule wasn’t wrong. It was just meant for a different plant.

    Most grammar rules were created for a different kind of writing. Prescriptive grammar tells you how language should be used. Descriptive grammar describes how people actually use it. Academic writing sits in prescriptive territory, and for good reason: quality and precision are the whole point.

    But fiction lives on another plane. The fiction author’s job isn’t to uphold a rule; it’s to capture how a person actually thinks, speaks, and moves through a world, and all of us real people break grammar rules constantly, without noticing and without apology.

    A fair number of the rules writers were taught in school were never really rules to begin with. Some are the arbitrary preferences of eighteenth-century grammarians, who decided English should behave more like Latin, which is where the prohibition on splitting infinitives comes from. Latin infinitives are a single word (example: scribere = to write); they can’t be split. English infinitives are two words, so the rule against separating them imported a constraint from a language where it was never even a thought.

    Others are class markers dressed up as correctness, ways of signaling education and status that have less to do with clarity and more with determining where someone belongs. Language is constantly shifting. What was correct in 1950 sounds stiff now, and holding a manuscript to that older standard erases the regional and cultural speech patterns that make a character sound like someone specific and someone interesting.

    Many times it’s not a matter of whether a sentence is grammatical or not. It’s whether the sentence serves the story, the scene, and the character speaking it.

    Subscribe

    Where This Shows Up First: Dialogue

    Dialogue is where the gap between grammar and authenticity stands out the most. Real people don’t speak in complete sentences all of the time.

    Grammatically correct: “I do not know where he went. Did you see him leave?” “I did not see him leave.”

    Authentic: “No idea. Did you see him leave?” “See him? No.”

    Real speech is fragmented and interrupted, full of trailing thoughts that never get finished because the other person already knows what was meant. Dialogue polished to grammatical perfection reads like a script being performed, not two people talking.

    The same gap shows up in constructions writers overcorrect out of habit.

    Overcorrected: “It is I,” she said. “To whom should I give this?”

    Authentic: “It’s me,” she said. “Who should I give this to?”

    “It is I” is technically correct and also how no one talks unless they are a butler in a period drama or somebody totally taking the piss. Ending a sentence with a preposition is ordinary English. Restructuring a sentence to avoid it produces a stiffness that serves the rule instead of the reader.

    Different characters break different rules, and the differences are what characterization actually is. A highly educated character might speak in longer sentences and precise vocabulary and still break rules constantly in casual speech because of written diction. A working-class character might use regional grammar flaws, word contractions, double negatives, or sentence fragments that carry more weight than a complete sentence ever could. A teenage character might use “like” as a verbal tic, trail off mid-thought, let text speak slip into dialogue or internal narration. Correct these fragments into standard grammar, and it’s not cleaning up the prose. It’s erasing the character.

    One specific example is the fading of the subjunctive mood in wished-for or imagined states. Formal grammar calls for a plural verb form even when the subject is singular.

    Formal: “I wish I were taller.”

    Informal/Authentic: “I wish I was taller.”

    Most English speakers couldn’t name the subjunctive mood if asked. That’s the point, though. Nobody needs to know the rule to feel the difference in the formal version as opposed to informal. And the informal subjunctive isn’t a mistake creeping into dialogue. It’s what real people do with tenses when they speak, yet many of us know when it’s better to use the formal.

    This is a language shift in progress and is common enough in print that a critique partner marking it “wrong” is expressing a preference, not a rule. Both have their place. The choice is about the tone you want the line to have. (This is one I consider carefully with every case. Sometimes the informal just “sounds” better with the surrounding text, even in narrative prose.)

    It’s Not Only Dialogue

    Fragments in narration are also a tool, not an error. “She opened the door and saw the room was empty, which was surprising.” and “She opened the door. Empty.” are not conveying the same thing, even though they describe the same event. The fragment creates a pause that mimics the actual shape of noticing. Cut every fragment from a manuscript and the prose ceases to feel alive.

    The old rule against starting a sentence with “And” or “But” doesn’t hold up against how often published fiction does exactly that, because the full stop–new sentence construction does work a comma can’t. “She didn’t want to go. But she went anyway.” carries a hesitation the comma-joined version smooths over. Split infinitives fall into the same category. “She wants to double her subscriber count by spring” states a goal. “She wants to more than double her subscriber count by spring” is the actual goal, and there’s no other way to say it. Move “more than” anywhere else in the sentence and the math changes or it stops making sense.

    Language keeps evolving, and a manuscript either reflects that or doesn’t. Singular “they” has moved from workaround to standard; “someone left their coat” has mostly replaced the clunkier “someone left his or her coat,” and prose still defaulting to “he” as the generic pronoun reads as dated immediately. Dialogue conventions are shifting too, toward em dashes for interruption, toward dropping “said” tags when the action already tells who is speaking. The same loosening shows up in punctuation more broadly—the comma after a short introductory word or before a sentence-ending “too” is increasingly treated as optional rather than required.

    Where the Rule Still Holds

    None of this means grammar has stopped mattering. It means the question is always what a rule is advocating for.

    Follow it when clarity is genuinely at risk, such as when a misplaced modifier changes what a sentence means rather than just how it sounds.

    Follow it when the formality is the point, in historical fiction with an elevated narrative voice, or literary prose crafted around precision.

    Follow it when the rule is doing characterization—when a grammar-obsessed professor would catch and correct themselves mid-thought, or a formal character would genuinely speak more correctly than the people around them.

    Break it when authenticity requires it; when the dialogue needs to sound like an actual person and not a stand-in for one.

    Break it when the rule itself is a leftover, a Latin-shaped prohibition, or an eighteenth-century preference with no functional reason for existing in English fiction written now.

    The difference between authentic rule-breaking and sloppy writing isn’t whether the rule was followed. It’s whether the choice was made on purpose.

    Authentic rule-breaking (the best kind, hands down) is consistent with a voice already established, serves the rhythm or the clarity of the moment, and shows up constantly in published books in the genre. Sloppy writing just drifts. The voice shifts without reason from one page to the next, and if you ask the writer why they made a particular choice, they don’t have an answer, because there wasn’t one.

    Read any suspect part, whether dialogue or narrative, out loud. If it sounds like a script being performed instead of a person talking, the grammar has gotten in the way of the story it’s supposed to help tell.

    An Editor’s Role

    The critique partner from the opening didn’t do anything unusual; they just did more than what they needed to. Highlighting every fragment and flagging initial prepositions is proofing for correctness, and correctness was never the question or ultimate goal. It’s always whether the sentence is doing what the story needs it to.

    A professional (human) editor starts with this question and doesn’t stop at asking it. When a manuscript comes across my desk, I have to decide, sentence by sentence in a line or copyedit, whether something is a slip the author didn’t notice or a choice they made on purpose—a working-class character’s double negative, a sentence that leaves out a comma because the moment is fast and tense, a fragment doing important work a full sentence couldn’t. If it’s intentional or serves the scene and story, my job isn’t to correct it. It’s my task to understand the context and see the author’s vision.

    But leaving it silently unflagged creates a different problem several steps down the line. A manuscript typically passes through more than one set of hands: a developmental edit, a copyedit, a proofread, sometimes more than one proofreader if it’s with a publisher. Someone reading that manuscript without the context I had when I made the call sees a comma splice or a sentence starting with “And” and has no way of knowing whether it’s intentional or a miss that made it through the last pass. Proofreaders, in particular, are trained to catch exactly these things, because many times, they are misses.

    That’s what a style sheet is for. Every intentional pattern or nuance gets documented as it’s decided, not left for the next person (or me again in a few months) to guess at.

    This character’s sections run in fragments during moments of panic, not to be changed.

    This dialect includes consistent double negatives, STET.

    Dialogue and narrative situations where it feels more natural can use the informal subjunctive (I wish I was taller versus I wish I were taller).

    It’s where every deliberate break from style guide convention gets its reasoning explained, so the next editor down the line doesn’t have to relitigate the decision, or worse, undo it.

    That’s one of the big differences between what happened at the top of this piece and what a professional edit does. Not the red text versus no red text. Instead, it’s the willingness to ask why a sentence looks the way it does, decide on purpose, and leave a record for whoever reads next.

    Grammar is another tool in the writer’s toolkit. It was never the main focus. The focus is a character or a narrator who sounds like someone specific, with a voice consistent enough to trust and alive enough to feel like it belongs to a person and not a one-room schoolhouse primer.

    Aime Sund is The Narrative Gardener—a fiction editor and horticulturist at Red Leaf Word Services, where she helps genre fiction authors cultivate stronger stories through her Narrative Ecology™ framework. www.redleafwords.com

  • Root-Bound Stories

    A matter of ratio, not prose.

    close-up photo of a root-bound plant resting on a pink pot.
    Root-bound and ready to plant!

    Fictional worlds take time and energy to build, and for some (like me) creating in this manner fuels the fire within. In no time at all, ten thousand years of history exists on the screen, and the protag’s genealogy is mapped eight generations back. The magic system has internal logic that would survive peer review. Individual cultures have their own cuisine, their own lunar rites, their own slang. A new calendar system is in place, certain regions produce certain crops, and specific families have specific abilities, but there are always wildcards (true story).

    Readers all say the worldbuilding is impressive.

    They also say they’re having trouble getting into the world. Or worse, they get into the world just fine and still don’t care what happens to the people in it. This is an often-encountered situation, one I can draw a direct parallel with in horticulture: the condition of a plant being root-bound.

    What “Root-Bound” Means

    When a plant stays too long in a container, or when it’s never transplanted at all, the roots run out of room to expand outward. So they circle. They layer. They grow back into and over themselves, filling every available inch of the pot with root mass so dense there’s barely any soil left.

    From the outside, the plant may look fine. It leafs out, takes up water, it survives. But it doesn’t thrive. Growth is stunted and yellowish. Flowering is sparse or doesn’t happen at all. In an effort to find more nutrients, the plant pours energy into its root system, which becomes an increasingly elaborate underground architecture, while the visible structure above the soil stays thin.

    The roots aren’t the problem, though. Roots are necessary. A plant with no root system dies immediately. The problem is ratio: when roots fill every inch of the container, there’s no growing medium left to hold water and nutrients. At a glance, the plant can still look fine, the way a great blurb, a phenomenal cover, intriguing About copy can look fine. Underneath, it’s suffocating on its own overgrowth.

    A root-bound story works the same way. The worldbuilding is extraordinary—years of work, sometimes, building the history, geography, culture, magic, economics, and religion the story will root in. The architecture is vast, detailed, internally consistent. And then the story itself struggles to grow.

    This is root-bound.

    Subscribe

    How to Recognize It

    The signals show up in feedback first, usually. Impressive is the word that should give you pause—impressive worldbuilding, impressive detail, impressive scope. Impressive, by nature of the word, is admiring something from a slight distance, though. It’s not the same as immersed, or invested, or I couldn’t put it down.

    Readers may say the worldbuilding is overwhelming. Not that it’s too much worldbuilding in an abstract sense, but too much arriving before they have a reason to care about it. The information is present; the hook for why it matters and why the reader should care isn’t.

    Characters can feel thin despite their elaborate setting. This one feels counterintuitive because the writer has often done significant character work, detailed their backstory, and provided clear motivation. But the characters are competing for page space with the world itself, and in a root-bound manuscript, the world is winning. Readers spend so much cognitive energy processing setting, history, and systems that character has to work harder than it should to register.

    Plot is episodic. The story moves from location to location, culture to culture, set piece to set piece—each one an opportunity to reveal more of the world. But the throughline is the world itself, not the character’s want or need or transformation. Readers follow the tour. They don’t feel the pull.

    The first fifty pages are heavy. This is where root-bound manuscripts are most tangible. The writer knows that readers need context to understand what’s happening, so they provide it— upfront, thoroughly, before the story has generated enough momentum to carry the weight. By the time the actual story begins, some readers have already let go.

    And there’s a subtler signal, one the writer might recognize in themselves before any reader names it: the scenes that feel most alive to write are the ones that reveal the world. The magic system clicking into place. The cultural detail unfolding. The history surfacing through dialogue in an old library. Writing the character moments feels harder, less satisfying, more like obligation. That preference is useful information for diagnosis.

    Not the Same as World-as-Character

    There is an important distinction to make about certain world-centered stories, however.

    Some stories have the world functioning as a character in its own right. Gothic fiction, cozy fantasy, and plenty of science fiction novels, to name but a few, are built that way on purpose—an academy house with its own rules, a village whose seasons shape the plot as much as any person does, a ship or station whose systems create real stakes—those aren’t root-bound. Those worlds are doing narrative work the story assigned to them, and the human characters are written to share the stage rather than dominate.

    Root-bound is different. It’s not the world claiming a character’s role. It’s the world crowding out the space where a character role needs to exist and yet doesn’t.

    Why This Happens

    Often the story idea itself is the size of a shelf of books, and the writer tries to grow it in the space allotted for a few volumes.

    This isn’t a failure of discipline or that the writer refuses to hold anything back. Many root-bound writers have already cut, trimmed, and simplified considerably from what originally lived in their heads. The world may genuinely have enough material to sustain something much longer than this: enough history, enough incident, enough scope for a trilogy or more. But the story living on top of that world—this cast, this plot—doesn’t have equivalent depth. The plot and character development runs thin at half the length, so the page count fills with world instead. The writer isn’t hiding the story; there isn’t enough story yet to hide. The world was conceived as an ecosystem. The story was conceived as a single season within it, and the season isn’t long enough to need everything the ecosystem contains.

    **Sidenote: I’ll admit this one hits close to home. I’m sitting on a fantasy world I can see completely, clearly big enough to outlast the story I’ve actually got, so I’m stalled. See, it even happens to editors when they can name the problem. Advice, anyone?…

    What Root-Bound Is Not

    It is not a story where the writer needs to reveal less, though that is an actual issue and a different one, with its own conversation. Root-bound is not about a writer who built the right-sized world and mishandled the reveal.

    Root-bound is a writer who built a world sized for something larger than the story currently in front of them and hasn’t yet decided which direction to resolve that mismatch: grow the container or right-size the contents.

    Growing the container might mean the standalone becomes a duology. It might mean the novel was always a series pretending to be one book. Right-sizing the contents might mean the eight-generation genealogy is real and rich and simply doesn’t belong to this story. It belongs to the next one, or the one after that, or a page in the world bible the reader never needs to see.

    Neither direction is a failure. Both are decisions the writer must consider. What doesn’t work is refusing to make either one, trying to keep the full-scale world and the single book container at the same time. The mismatch lives in the fundamental agreement between what the world requires and what the story promised to deliver, not in any sentence-level revisions.

    What Root-Bound Feels Like From the Inside

    If you’re writing a root-bound story, you probably already know something is off. The feedback has been consistent enough to stop feeling like reader error. Revisions to-date haven’t fixed it. You’ve tightened the prose, trimmed the exposition, added a faster opening… and the fundamental problem persists.

    That persistence is the tell.

    Here’s what makes root-bound manuscripts hard to diagnose from the inside: the world is real; it’s unique and excellent, and admitting it might be the problem feels like admitting years of work were wrong. They weren’t. But that fear is exactly why so much root-bound revision stays at the sentence-level—tightening prose is safe. Questioning whether the world itself needs to shrink, or the story needs to grow to meet it, means being willing to treat your own favorite thing as a variable instead of a fixed point. That’s a harder kind of objectivity than craft skill alone provides.

    The roots are still there. The canopy is still in place. Only real objectivity about the current ratio, not more polish, can show what actually needs to shift.

    Root-bound manuscripts need a different kind of revision than most writers expect—not line-level, and not structural in the conventional sense, but ecological. A Story Ecosystem Assessment™ maps the current balance of elements in your manuscript to identify where energy is stalling and what the visible story needs to grow. If your worldbuilding is impressive and your story still isn’t connecting, that’s worth looking at closely.

    Aime Sund is The Narrative Gardener—a fiction editor and horticulturist at Red Leaf Word Services, where she helps genre fiction authors grow stronger stories through her Narrative Ecology™ framework.

  • The Microclimate Problem: Why Cozy Fiction Is Harder Than It Looks

    The stakes are real. The author just has to build them from the inside out.

    picture of a terrarium shaped like a house.
    One of my Wardian cases. It holds my longest living Venus flytrap.

    The word cozy does something to people’s assumptions before they’ve read a single page.

    Low stakes. Easy read. Simple pleasures. These aren’t wrong, exactly, but they describe the reading experience, not the writing challenge. The two are not the same. A cottage garden looks charmingly haphazard. Achieving that apparent spontaneity—the right plants, the right succession, the right controlled chaos—is another thing entirely.

    A microclimate isn’t a lesser climate. It operates at a different scale, under its own pressures, with its own specific points of failure. The alpine meadow above the tree line isn’t a diminished forest. It’s a specialized system; more intricate, more fragile, and in many ways more demanding to sustain than the sprawling ecosystem below it. Remove one element and the whole thing destabilizes. There’s no redundancy. That’s not weakness. That’s the nature of a system built with precision and intent.

    Cozy fiction is a microclimate. And building one that holds is among the more demanding stakes work in genre fiction.

    Scope and Stakes Are Not the Same Thing

    This is where the assumptions go awry, for readers who become writers and carry the wrong premise with them.

    Stakes are what the character cannot afford to lose. Scope is the scale of the world in which she might lose it. Cozy compresses scope. It does not compress stakes.

    A protagonist who wants nothing more than to run her tea shop in peace, stay out of other people’s business, and keep the life she’s built intact—she’s operating under stakes as real and urgent as any thriller hero. The difference is that cozy offers less external scaffolding that affects the protagonist. No ticking bomb, no global threat, no mechanism borrowed from outside the character to manufacture urgency. The stakes have to live entirely inside the character and the reader’s belief in them.

    When writers internalize “low stakes” as a genre description and accidentally apply it to character desire, the result is a specific kind of drift. The tea shop matters a little less. The friendships become decorative. The disruption is inconvenient rather than genuinely threatening. The reader drifts too, and they usually can’t name why. The plot is functional. The mystery resolves. Yet something is still missing.

    What’s missing is the tangible weight of what’s at risk. And that weight doesn’t come from the size of the threat. It comes from the depth of the want.

    The Calibration Problem

    Before stakes can land, the reader has to be calibrated to the character’s world. This is the work that precedes everything else, and it’s where most cozy manuscripts have the most to do—not in plot structure, not in mystery mechanics, but in the quieter accumulation of evidence that this particular life, to this particular person, is worth protecting completely.

    Calibration isn’t intellectual. Readers can understand intellectually that the protagonist values her independence, her shop, her small routines. That understanding doesn’t make them feel the cost when those things are threatened. Calibration is felt. The reader absorbs, through repeated contact, why this specific thing matters this much, until the character’s priorities become inescapable rather than observed.

    It requires specificity of desire. Not “she wants peace” but the precise texture of what peace means to her—what it cost her to build, what it looked like the morning she first had it, what she does to protect it that she’d never admit to. Vague desire produces vague stakes. The more precisely the author knows what the character wants, the more exactly the reader can feel what losing it would mean.

    This requires consistency across the whole manuscript, not just the crisis beats. Every scene is an opportunity to reinforce what matters. How she answers a question she’d rather avoid, what she notices first when she walks into a room, what she gives up quietly when protecting something she won’t name out loud, why she prefers to stay in on Friday night. The calibration isn’t a passage or a chapter. It’s the texture of the entire story.

    Reinforcement Is Not Repetition

    Most cozy manuscripts that need work don’t need the author to tell the reader more clearly what the stakes are. They need the author to stop telling and start accumulating.

    Reinforcement is not repetition. It’s not restating the protagonist’s desire at intervals, or returning to it in moments of explicit reflection. It’s the steady, quiet presence of what matters in every choice, every reaction, every scene so consistently that the reader absorbs it without registering it as information delivery.

    When reinforcement is working, readers don’t consciously think she wants her quiet life back. They feel the cost of every scene that threatens it. The stakes operate below the surface. The reader is inside the character’s priorities rather than observing them.

    In a functioning ecosystem, no single element announces its importance. The mycorrhizal network running beneath a meadow doesn’t declare itself. It’s simply there, doing invisible work that holds everything else up—moving nutrients, signaling stress, connecting root systems that appear separate above ground. Reinforcement is the mycorrhizal network of cozy stakes. You don’t see it. You feel the difference when it’s missing.

    Why This Is Precise Work

    High-concept genres have external pressure to lean on. The thriller reader feels urgency because the threat is visible and ticking. The author still has to do the character work, but the scaffolding exists; the mechanism provides some of the tension on its own.

    Cozy doesn’t have that. The urgency has to be built from the inside out, through the character, through the reader’s belief, through the accumulation of small moments that together make the quiet want feel inescapable. There is no borrowed machinery.

    This is not easier than writing toward external stakes. It is a different and more precise skill—one that requires the author to trust specificity over escalation, depth over drama, the small true thing over the large obvious one.

    The authors who do it well don’t reach for bigger threats when the stakes feel flat. They go back to the character and find the more exact want. Then they put it everywhere.

    A Note on the Reader’s Side of This

    Some readers choose cozy precisely because they want lower emotional investment—the pleasure of a contained world, a resolvable problem, a gentler demand on their attention. That’s a legitimate reading experience and not what this post is arguing against.

    The craft question is separate from the reader’s preference. A reader who wants to feel at ease inside a cozy world is still best served by a microclimate built with precision; one where the stakes are proportional and fully realized, where the character’s world has weight and texture, where the resolution satisfies because something real was at risk. The reading experience of ease and warmth is the outcome of craft, not the absence of it.

    The cozy reader who says a book felt thin isn’t asking for higher stakes in the conventional sense. They’re asking for better calibration. More of the invisible work.

    The Microclimate Has to Hold

    The alpine meadow doesn’t need to be a forest. It needs to be itself—fully, specifically, with no element left inert.

    Cozy fiction at its best is sustained persuasion: convincing the reader that this world, this person, this particular quiet want is worth caring about completely. Not because the stakes are large. Because the author never let them look away.

    That’s the work. It isn’t less than other genres demand. It’s a different demand—interior, cumulative, precise. A microclimate that thrives because every element in it is doing its job.

    If your cozy manuscript has the right structure but the stakes aren’t landing the way you expect, it’s often a calibration issue—the kind that shows up in the texture of individual scenes rather than in the plot. Story Ecosystem Assessments™ look at how a manuscript’s elements are working together, including where reinforcement is thin and where the reader is being kept at arm’s length from what matters.

    Aime Sund is The Narrative Gardener—a fiction editor and horticulturist at Red Leaf Word Services, where she helps genre fiction authors grow stronger stories through her Narrative Ecology™ framework.

    Subscribe

  • When Stories Blossom: Recognizing Your Manuscript’s Growth Stages

    Your manuscript is growing. It just might not be blooming yet.

    My fringetree, Chionanthus virginicus, about to bloom. I saved it from the compost pile last fall.

    There’s an ornamental bed I’ve been slowly adding to for years that I worked on last October. I know exactly what’s in there—the plants, the shrubs, the colors, the transplants I made. I’ve been watching that bed since February, and until a few weeks ago (given our fickle New England weather), there was nothing to see but wood-chipped ground and my own impatience.

    Then the shoots finally appeared.

    I didn’t make that happen by checking more often. The plants emerged when the conditions were right: enough cold, enough warmth, enough time in the ground. My job was to plant correctly and stay out of the way.

    Stories work in much the same way. They have growth stages, each with its own requirements, and the most common mistake writers make isn’t revising too much or too little. It’s applying the wrong intervention at the wrong stage. Pruning a seedling. Watering a plant that needs sun. Harvesting before the fruit is ripe.

    Knowing where a manuscript is changes what it actually needs from the author.

    The Seedling Draft

    A first draft is fragile in the specific way seedlings are fragile: it has just broken ground, its root system is minimal, and the wrong kind of attention will kill it faster than neglect will.

    What this stage needs is completion. Not polish, not perfection, just reaching the end. The structure is visible but may be weaker than necessary. Some sections thrive; others wilt when the sun comes out. That’s expected. The author is still discovering what this story wants to be, and the only way to find out is to keep writing.

    A potential danger here is editing while drafting—going back over yesterday’s pages, trimming, second-guessing. That’s like leaf pruning a seedling. You’re cutting growth before it has a chance to flourish, and the plant doesn’t have the reserves to recover. Many writers who do this may find themselves at chapter four, forever. The seedling never gets its larger true leaves.

    However, for some writers, this approach is helpful and can re-root them in the story, especially at the start of a writing session. I’m one of those. The trick here, then, is to know when to step out of the sticky clay and move on with the next ideas and let the words flow.

    Both approaches lead to the same place: Write forward. Leave the mess. The mess is where the roots grow from.

    Established Growth

    By the second or third draft, the manuscript has roots. Its shape is there. You know what the story is, even if you can’t fully articulate it yet, and the structure is strong enough to handle bright, sunlit attention.

    This is the stage where strategic revision earns its place. Cut what isn’t serving the plant. Strengthen what is. Deepen the character arcs, clarify the stakes, look honestly at the structure and ask what’s holding weight in scenes and what’s decorative. This is also the right moment to bring in outside perspective—beta readers, a manuscript assessment—because the manuscript is established enough to survive scrutiny without collapsing.

    The signs of this stage are: the story can be explained clearly, the major beats are in place, the characters have arcs even if those arcs need refinement. It feels close but not there yet. That feeling is accurate. It’s not there yet. Let it keep growing.

    Budding

    Late revision is its own distinct stage, and writers often miss the transition. The work now shifts from structural to granular. Sentence-level changes, prose polish, the difference between a scene that does what it needs to and a scene that sings. The story knows what it is. Small refinements make large differences in this stage.

    The danger at this stage is the opposite of the seedling problem: instead of pruning too early, writers may over-revise. They keep restructuring when the structure is sound. They rewrite scenes that were working because they can’t quite believe they’re done. Prolonged stress on a plant that’s ready to flower doesn’t improve the bloom. It depletes the plant.

    If beta readers are saying “this works really well, just needs polish” but scenes are still being moved around, pay attention to that. The reactions signal the stage and the shifting work is likely too much.

    Flowering

    A manuscript that’s ready is ready. Not perfect—what garden is ever perfect?—but complete in the sense that it’s doing what it was always meant to do. The story is vibrant and whole, and it’s time to let it be seen.

    This stage has its own particular difficulty. After months or years of growth, the habit of tending can be hard to break. There’s always one more thing on the list to examine. One more pass. One more scene to reconsider. But a flower held in a vase too long fades there.

    When you’ve done multiple revision passes, incorporated substantive feedback, and can’t identify what to fix without breaking something that works, that’s the signal. It’s done. Let it bloom and be admired.

    When the Manuscript Won’t Move

    Some manuscripts stall. They stay in vegetative growth for a long time, not quite budding, and no amount of additional revision seems to move them forward.

    This usually indicates a root problem rather than a surface one. The foundation isn’t strong enough to support flowering—something in the core conflict, the stakes, or the character’s central need isn’t fully developed yet. Or there’s a condition mismatch: the story is being forced to grow in the wrong environment, and it’s not as robust as it could be. A quiet character study being pushed toward thriller pacing. A cozy mystery being revised for tension it was never designed to hold.

    None of this means the manuscript is lost. It means the conditions need to change before growth can continue. Sometimes that means setting it aside and coming back when the creative well is refilled or the writer’s craft has grown. Sometimes it means a more honest look at the foundation. The plant isn’t the problem. The soil is.

    Right now, in my garden, things are at different stages all at once. The lilacs are just finishing flowering. The peonies are budding out. The Asiatic ginger groundcover in the back is already spreading, ahead of everything else. None of them are in the wrong. They’re just on their own timelines, doing the work appropriate to the environmental conditions.

    A manuscript has a timeline too. The best thing to do is figure out which stage it’s actually in—not the stage you wish it were in—and give it what that stage requires.

    The bloom will come. It just needs the right conditions and enough time.~

    Subscribe

  • The Drought-Stressed Manuscript

    A resource problem mistaken for a craft problem

    a dry spider plant in a pot
    I know… I should do better

    The beta reader feedback comes in with the ambiguous “good” in the comments. “Good” doesn’t convey much and isn’t the hoped-for emotional response (positive or negative). Maybe one or two say “it feels like something’s missing” but they can’t quite explain what. So, you delve into revisions—a snappier opening, a more detailed scene, a beefed-up subplot thread—and the next round of feedback says the same thing. “Good.” Maybe even “great.” But the reactions still aren’t there, and nothing is specific enough to pinpoint what’s keeping the readers from having the experience you want them to have in your world. Something’s just not quite right.

    This is one of the more disorienting phases of a manuscript, because there’s no obvious dangling thread or pacing problem to tackle. The prose is competent. Individual scenes work. The characters have clear motivations. And yet the story feels exacting to read, like moving through humid air in the summer.

    What’s usually happening isn’t a craft failure. It’s a resource problem.

    When the water doesn’t go far enough

    In horticulture, this has a name: drought stress. In its later stages, it can look very much like death: desiccated leaves, collapsed stems, brown and spent. But looking like death and being dead aren’t the same thing. A drought-stressed plant is fighting to hold on, drawing down whatever reserves it has, suspending growth entirely, waiting for water that may or may not arrive in time. If it does, the plant recovers. If it doesn’t, it perishes, maybe for the season, maybe permanently. Either way, nothing is growing. Everything is directed toward survival. And the problem may not be an absence of water. It may be that the available water is spread too thin, across too many plants and plant systems competing for the same limited supply.

    Story energy works the same way. It’s finite. Every element of a story—every POV, subplot, secondary character, worldbuilding system, thematic thread—draws on the same source. When a manuscript tries to run all of them at full capacity simultaneously, nothing gets enough. Everything survives, but nothing flourishes.

    This is what I think of as a drought-stressed manuscript.

    What it looks like from the inside

    Drought stress has a recognizable set of symptoms, though they’re easy to misread.

    Revision rounds that feel like rearranging furniture. You move things around, tighten this scene, cut that chapter, shift a subplot, open the story in a different place, and the story feels neither better nor worse. Each change is absorbed without visibly improving the whole.

    The instinct to add. When a story feels thin, the natural response is to put more in: another character to generate interest, a new subplot to create momentum, more worldbuilding detail to make the world feel real, oh, a love interest! But in a drought-stressed story, adding more doesn’t help. It dilutes what’s struggling further.

    Beta readers who shrug or say “It’s good.” Not because the story is bad, but because there’s nothing specific to point to. “I couldn’t connect with it” or “it didn’t quite grab me” are also responses that feel frustratingly vague, because the problem genuinely is diffuse. It’s systemic, not localized.

    Craft competence without emotional connection. The sentences are clean. The story structure is sound. And yet something that should feel high-stakes reads as flat. This is often the signal that the story is spending energy maintaining its own complexity instead of directing the energy toward connecting with the reader.

    What it isn’t

    Drought stress is not a failure of craft. This is worth saying clearly, because writers who find themselves here often assume they simply aren’t skilled enough, that better prose, sharper dialogue, more careful plotting would solve it.

    Sometimes that’s true. But often the individual elements are genuinely well-executed. The problem isn’t quality. It’s distribution.

    A subplot can be beautifully written and still be consuming narrative energy the story can’t spare. A magic system can be internally consistent and still be drawing attention away from the character arc it’s supposed to serve. A secondary character can be vivid and still be competing with the protagonist for the reader’s investment (even though we love them and they will have their own book!). None of these is a craft failure in isolation. Together, they create a story where the water doesn’t go far enough to sustain.

    The harder question

    The instinct when a manuscript isn’t thriving is to work harder on individual elements. Write the scene again. Deepen the character. Tighten the pacing. This is understandable; it’s where craft lives, and craft is what writers know how to improve.

    But consider what actually works in a drought-stressed garden. Watering individual plants more attentively can save that one plant, but it doesn’t solve the underlying system shortfall—the same number of plants are still competing for the same baseline supply. The more sustainable solution is reduction: fewer plants drawing on the same water, so those remaining can be adequately supplied rather than merely maintained. And the most elegant solution of all is to stop fighting the climate—to plant species that are built for those conditions, that root deeply and direct energy precisely, that don’t require individual intervention to thrive.

    A story can be held to the same test. Drought stress doesn’t respond to more effort applied to individual elements. It responds to a different kind of question: not what needs to be better, but what is consuming resources it hasn’t earned, and what is being starved as a result. Sometimes the answer is reduction: doing twelve things at full capacity rather than twenty things at seventy percent. Sometimes it’s structural, needing to be built into the story from the beginning. Everything done with intentional economy, every element load-bearing, nothing purely decorative.

    That second approach—learning to write drought-tolerant stories, shall we say—is its own conversation, and one worth having separately.

    For now, the first step is recognizing that “fine but not thriving” is a symptom with a cause. Not a reason to add more. A reason to look carefully at what’s already there and ask what the story actually needs to flourish.

    Subscribe

  • Filter Words, Unfiltered

    What These Common Words Are Really Doing to Your Story

    a variegated hosta right after rain
    Hosta ‘Striptease’ post-rain; the garden unfiltered.

    Part 1 of 3

    Imagine you’re standing in a garden just after it’s rained. The air is heavy with petrichor, the soil dark and alive, water still beading on the leaves of the hostas. You can almost feel the cool dampness against your skin.

    Now imagine standing at the edge of that same garden, but this time, behind a pane of glass.

    You can see everything. But you can’t smell a thing.

    That’s what filter words do to your readers.

    So What Are Filter Words, Exactly?

    Filter words are verbs, usually sensory, perception, or cognitive verbs, that place a layer between the reader and the character’s sensory experience. They’re the literary equivalent of that glass pane.

    They typically appear in constructions like this:

    She felt the cold seep into her bones. He noticed the door was ajar. Maya realized she was alone.

    The character perceives something, and the reader receives that perception secondhand. It’s a subtle layering; so subtle that many writers don’t notice they’re doing it. But readers feel it, even when they can’t name it. That slight remove, that almost-there quality, that sense of watching the story rather than living inside it.

    That’s the filter at work.

    The Usual Suspects

    Filter words most commonly show up as sensory and cognitive verbs:

    Sensory: feel/felt, see/saw, hear/heard, notice, watch, smell, taste, listen

    Cognitive: think, know, realize, remember, wonder, decide, experience, find (as in she found herself)

    They’re familiar words. Useful words in everyday language. Which is why they slip through so easily during drafting; they feel like good, solid anchors for the point-of-view character. And that instinct isn’t entirely wrong, which we’ll come back to.

    Why We Write Them (And Why That Makes Sense)

    Here’s something I want to be clear about: filter words aren’t a sign of weak writing. They’re a sign of a writer who is genuinely trying to stay inside their POV character’s head.

    The instinct to write she noticed the letter on the table comes from a good place. The author is thinking about the character, grounding the observation in her perception, being careful not to slip into an omniscient perspective. That’s solid craft instinct.

    The problem is that deep point of view—the kind that makes readers forget they’re reading—doesn’t actually need that anchor. When we’re truly inside a character’s perspective, the filter verb becomes redundant. Of course she noticed the letter. She’s the one telling us about it.

    Removing the filter doesn’t lose the POV. It deepens it.

    What’s Actually Happening in the Reader’s Brain

    Every time a reader encounters a filter word, there’s a micro-interruption. It’s tiny, almost imperceptible on its own. But fiction works cumulatively. One filter word is a hand on the reader’s shoulder, holding them just outside the garden gate. A manuscript full of them and they never get in at all.

    What readers are experiencing, without being able to articulate it, is narrative distance. They’re aware—just slightly, just enough—that they’re being told about someone else’s experience rather than having one of their own. The immersion isn’t broken or distorted, exactly. It’s just never quite complete.

    Think of it this way: in a healthy story ecosystem, the reader is the character for the duration of the book. Filter words remind them they’re not. They’re observers. Visitors to the garden, not gardeners themselves.

    The goal of deep POV is to hand them the trowel.

    See the Difference

    Let’s put this into practice. Here are three filter-heavy sentences, followed by their unfiltered versions:

    With filter: She felt her heart rate spike as she heard footsteps on the stairs.

    Unfiltered: Her heart rate spiked. Footsteps on the stairs.

    With filter: He noticed the room smelled of cigarettes and something chemical, something wrong.

    Unfiltered: The room smelled of cigarettes and something chemical, something wrong.

    With filter: Maya realized she’d been holding her breath.

    Unfiltered: She’d been holding her breath.

    Notice what happens in each revision. The sentences get shorter, yes, but more importantly, they get faster. More immediate. The reader lands directly in the sensation rather than reaching for it through the filter first. The glass comes down. The garden opens up to all the senses.

    A Word of Caution (Because Rules Exist to Be Broken)

    Filter words aren’t inherently wrong. Sometimes they earn their place.

    When a character is meant to feel distanced from their own experience, as in situations of dissociation, shock, emotional numbness, a filter word can actually do precise, intentional work. She watched herself sign the papers lands differently than She signed the papers, and sometimes that distance is exactly what the scene needs.

    The difference between a crutch and a tool is awareness. We’ll dig into that distinction, and how to develop the judgment to know when to cut and when to keep, in Part 2.

    Your Assignment Before Part 2

    Open your current manuscript or any chapter you’ve been working on recently and use the Find function to search for just one word: felt.

    Note how many times it appears. Don’t change anything yet. Just look.

    See how often it’s doing necessary work, and how often it’s simply standing between your reader and your character’s experience. Sit with that for a few days.

    Part 2 will give you the tools to do something about it.

    Part 2: How to Find and Fix Filter Words—coming soon.

    Subscribe

  • Three Signs You’re Ready for a Developmental Edit

    Reading the Signs Before You Bring in Outside Eyes

    There’s a particular kind of stuck that happens after the draft is done.

    The manuscript exists. It has a beginning, a middle, an end. Characters who breathe, scenes that move, a story that, mostly, holds together. And yet… Something isn’t sitting right, and the revision passes that were supposed to fix it have produced a document that looks different but feels the same. The writer knows something is off. They just can’t locate it.

    This is not a failure of craft. It’s a failure of proximity. And it’s one of the more useful things a developmental editor is actually for.

    The harder question is whether that’s where a manuscript is. Developmental editing is a specific intervention for a specific condition. Bringing a developmental editor in before the draft has been through the writer’s own revision process is like training laterals on a vine that hasn’t set its trunk yet—you’re redirecting energy the structure still needs, and the intervention doesn’t just fail to hold. It sets things back.

    So how do you know when the right time is?

    emerging hellebore in frozen soil

    Sign one: Your beta readers contradicted each other

    Beta feedback that converges is useful. Beta feedback that diverges is even more useful… and harder to sit with.

    When some readers find the pacing tight and others find it slow, when some connect with the main character and others don’t, when the ending lands for half the room and falls flat for the other half—these are not signs that the manuscript is broken. They are signs that something structural is creating inconsistent experiences. A pacing problem that only some readers notice is often a scene-function problem: certain scenes are doing more than one job, or the wrong job, and different readers weight those jobs differently.

    Beta readers tell you where they felt something. They are rarely positioned to tell you why. That diagnostic step of identifying the pattern beneath the contradictory responses is what a developmental edit is built to do. Contradictory feedback isn’t chaos. It’s signal waiting to be read.

    Sign two: You’ve revised the same scenes multiple times and they still aren’t working

    There is a particular revision loop that writers recognize immediately when it’s pointed out: the scene gets rewritten, and the new version is different, but the problem is still there. So it gets rewritten again. The prose gets tighter, or looser, or the dialogue sharpens, but the scene still doesn’t land. More passes. Same result.

    This loop is almost never a prose problem. It’s a structural problem wearing a prose costume.

    When a scene isn’t working no matter how many times it gets revised, it usually means the scene is being asked to do something the surrounding architecture isn’t supporting. The setup isn’t there. The payoff is in the wrong place. The character motivation that would make this moment land hasn’t been established, or was established too early and has since been buried. The writer cannot see this from inside the manuscript because they know what the scene is supposed to do. The scene knows too. It just can’t do it from where it’s standing.

    This is the forest-for-the-trees problem, and it’s almost definitionally invisible from inside.

    Sign three: You know something’s wrong but can’t say what

    This one gets dismissed more than it should.

    Writers are often told to trust their instincts, and then, when their instincts fire—when they read through a draft and feel a persistent unease they can’t articulate—they talk themselves out of it. The manuscript is finished. The beta readers liked it. Maybe the feeling is just anxiety.

    Sometimes it is. But more often, the feeling is accurate. Authors spend months or years inside a manuscript, and that proximity creates a kind of peripheral vision for the story’s problems. The conscious mind can’t isolate the issue, but something in the writer’s reading brain is registering it. That registration shows up as unease.

    It is worth trusting. Not because instinct is infallible, but because an experienced editor can often identify in a single read what the writer has been circling for months. The instinct points at the neighborhood. The edit locates the address.

    When you don’t need a developmental edit

    This is worth saying plainly, because not every stuck manuscript needs the same intervention.

    If the draft isn’t finished, a developmental edit isn’t the next step. Self-revision is. A developmental editor works with a complete manuscript—one that has been through at least one round of the writer’s own critical eye. Bringing in outside perspective before that work is done means paying for feedback on problems the writer could have found and solved independently.

    If the draft is complete and has been revised, but what feels off is at the sentence level—rhythm, word choice, consistency of voice—that’s line editing territory, not developmental. The two are distinct services addressing distinct layers of the manuscript. A developmental edit will not fix comma splices, and line editing will not fix a second act that loses momentum.

    And if the manuscript genuinely feels finished—if the beta feedback was largely consistent, if the revisions landed, if the unease is absent—then it may simply be finished. Not every completed draft needs a developmental edit. Some manuscripts find their shape through the writer’s own revision process, and the right next step is querying or copyediting, not another layer of deep editorial intervention.

    What developmental editing actually does

    It’s not rescue work. It’s diagnostic work.

    A developmental editor reads the manuscript as a complete system, tracking how the structural elements interact, where the load-bearing moments are, what the reader is being set up to expect and whether those expectations are being met. The questions are systemic: what is this scene doing relative to what the story needs it to do? Where is the reader’s attention being directed, and is that the right place? What is the emotional logic of this character’s arc, and is it landing?

    The edit doesn’t fix the book. It gives the writer a map of what’s actually happening versus what they intended to happen, precise enough to revise strategically rather than in circles.

    That map is most useful to a writer who is ready to use it—which means a draft that is complete, a revision process that has already run its course, and a writer who has arrived at the limits of what they can see on their own.

    If those three signs are present, a writer’s limits have probably been reached.

    Aime Sund is The Narrative Gardener—a fiction editor and horticulturist at Red Leaf Word Services, where she helps genre fiction authors grow stronger stories through her Narrative Ecology™ framework.

    Subscribe

  • The Questions I Ask Every Manuscript

    “Is this good?” is a verdict. “Is this working?” is a direction. Seven questions that tell the difference.

    Somewhere around page thirty of a cozy mystery, or deep in the second act of a historical romance, or tangled in the magic system of a fantasy novel, questions start surfacing. Different genre, different voice, wildly different worlds, yet there are the same questions, every time. Not because I’m running a checklist. Because the nature of story and the reader–author covenant require they be asked.

    These certain questions reveal patterns that craft advice alone doesn’t catch. They cut through the surface-level stuff—the prose, the pacing, the dialogue—and get at the structure underneath.

    Think of it this way: properly pruning a struggling rose all season long won’t reveal why it won’t bloom. The problem isn’t the flowers. It’s the root system. These questions are how I check the roots.

    Most writers approach revision asking: Is this good? It’s the wrong question, not because quality doesn’t matter, but because “good” has no address. It’s impossible to revise toward. It’s a verdict, not a direction.

    The question that actually opens a manuscript up is: Is this working as a system?

    That shift changes everything. A system can be examined. It has parts that interact, support each other, create pressure, or quietly fail. A story that isn’t working usually isn’t broken everywhere; instead, there’s a weak link somewhere in the chain. Find the link, and the revision becomes visible.

    Here are the seven questions I ask every manuscript—and that every manuscript, in some way, asks of itself.

    What does the protagonist want, and what’s stopping them from getting it?

    This seems obvious. It isn’t.

    “Want” has to be specific enough to create stakes, but broad enough to sustain a novel. “To be happy” is not a want. “To win back the estate before her brother sells it” is a want. The obstacle has to be meaningful resistance—not inconvenience, not bad luck, but something that creates genuine difficulty and demands difficult choices.

    If this question can’t be answered clearly by page 50, readers can’t answer it either. And without a clear want + obstacle, there’s no story engine. Everything else, the gorgeous setting, the witty banter, the carefully plotted twists, is decoration on a house with no foundation.

    Not enough:

    • The protagonist wants “to find themselves” or “to heal” without something specific at stake

    Enough:

    • The protagonist wants something specific that requires choices they’d rather not make

    If this subplot / character / scene were removed, would the story collapse or adapt?

    This is one of my favorite diagnostic questions, because writers are often surprised by the answer.

    If the story adapts easily—if the climax still works, if the character arcs still resolve—that element isn’t load-bearing. It’s decorative. Decorative elements aren’t inherently bad, but they are expendable.

    This isn’t about “kill your darlings.” It’s about understanding what’s actually holding the story up versus what’s just hanging on. Effective revision requires knowing the difference.

    Try it:

    • Mentally remove the element in question

    • Does the climax still work? Do the character arcs still resolve?

    • If yes, it’s probably not essential

    Where is the reader’s attention being directed? Is that intentional?

    Every scene directs reader attention somewhere: to character emotion, to plot mechanics, to worldbuilding, to theme. The question isn’t where it goes; it’s whether that’s intentional.

    Readers will focus on whatever the prose gives them the most of. Three pages of intricate worldbuilding details and two sentences on a character’s emotional breaking point signals a story about the world, not the character. If that’s not the intent, the ratio needs adjusting.

    This is why so many “pacing problems” aren’t actually pacing problems. They’re attention distribution problems. The story is moving at the right speed, it’s just pointing at the wrong things.

    What has to be true for this ending to feel earned?

    Working backward from the climax or resolution is one of the most revealing things an editor can do. What emotional journey does it require? What stakes? What setup? Then the check: is all of that actually present in the manuscript, or is the author assuming readers will infer it?

    Endings fail when the setup isn’t there, not because the ending itself is bad. If the climax requires the protagonist to make a huge sacrifice, the manuscript needs to have spent real time establishing why they value what they’re sacrificing. That groundwork can’t be assumed. It has to be planted.

    Is this scene doing one job or trying to do three?

    Strong scenes have a primary job and maybe one secondary function. Everything else is a bonus, not a requirement. Scenes that try to introduce a character, advance the plot, deliver worldbuilding, and explore theme all at once tend to do none of those things well.

    It’s like trying to grow tomatoes, peppers, squash, and corn in the same small container. Each plant has what it needs to survive, technically. But none of them has what it needs to thrive.

    Quick test:

    • Can the scene’s primary purpose be named in one sentence?

    • If not, it’s probably doing too much

    Does the story’s structure match what the story is actually about?

    A story about internal transformation built on all external plot beats has a mismatch. A thriller whose structure lingers in introspection has a mismatch. Structure should support what the story values, not fight it.

    “Pacing problems” are very often structure/content mismatches in disguise. The fix isn’t to write faster. It’s to align the how with the what.

    What is this story’s biggest vulnerability?

    Every story has a weak point—the thing most likely to break under pressure. Thin worldbuilding. Unclear stakes. A passive protagonist. A meandering middle that can’t figure out what it’s building toward.

    Knowing a story’s vulnerability makes revision strategic rather than random. Everything can’t be fixed at once, and trying that path risks overworking the parts that are already working well while the actual problem goes unaddressed.

    How to find it:

    • It’s usually the thing beta readers mention most

    • Or the thing the writer is most defensive about

    • Or the section that’s been rewritten multiple times without improvement

    The last one is a particularly reliable indicator. Returning to the same section repeatedly without resolution usually means treating a symptom rather than the cause.

    The Meta-Question

    Every question above is really a version of a two-part underlying question:

    Does the story understand what it’s trying to be and is the execution aligned with that intent?

    Most revision struggles aren’t craft problems. They’re clarity problems. Once the story’s actual needs come into focus, the path forward becomes visible.

    What to Do with These Questions

    These questions don’t require an editor to be useful. Any writer can ask them:

    • Open the manuscript fresh, in a new document or printed out

    • Go through it scene by scene

    • Answer honestly—not the answers that feel good, but the ones that are true

    A manuscript that can answer them clearly is a manuscript the writer knows. And where they can’t be answered? That’s where the real work begins.

    When these questions surface but the answers don’t point to a clear path forward, that’s when outside perspective helps. A Story Ecosystem Assessment™ asks exactly these questions about a specific manuscript, showing what needs to change and why.

    Subscribe

  • How to Know If Beta Reader Feedback Is Right for Your Story

    Beta feedback is data, not directives. Here’s how to read it that way.

    The beta feedback is back. Some readers loved the protagonist; others found her annoying. Some said the pacing dragged; others wanted more worldbuilding. One person suggested cutting the entire second act.

    The confusion is now worse than before you sent it out.

    This is normal. It’s also not the crisis it feels like. Conflicting feedback doesn’t mean the manuscript is broken; it often means some of it is reader preference dressed up as craft advice. The task now isn’t to implement everything the beta readers said. It’s to figure out which feedback is actually about this story.

    Not All Feedback Is Created Equal

    Beta readers are generous, well-meaning, and almost always wrong about at least one thing. That’s not a flaw in the process—it’s the nature of subjective reading. The problem comes when authors treat all feedback as equally valid, equally urgent, and equally theirs to act on.

    It isn’t. Here’s how to sort it.

    Does it align with your story’s intent?

    This is the first filter, and it eliminates a surprising amount of noise. If the story contains a slow-burn character study and a beta reader says “needs more action,” that’s preference, not a problem. They wanted a different book. If a story is a thriller and multiple readers say “I wasn’t tense,” that is a problem because tension is the whole point.

    Feedback only matters if it’s relevant to what the author and story are actually trying to accomplish.

    Is it pattern-based or preference-based?

    Trust patterns. Question preferences.

    Four out of five readers struggling to connect with your protagonist in Act 2 is a pattern. One reader wishing the protagonist were male instead of female is a preference. These are not the same thing, and they don’t deserve the same weight.

    When processing feedback, look for convergence. Where do multiple readers, independently, flag the same experience? That’s a signal. One person’s strong reaction, especially when no one else shares it, is data about that reader, not necessarily data about the manuscript.

    Does it address a symptom or a root cause?

    “The pacing drags in Chapter 7” is a symptom. “I didn’t understand what your character wanted in this section, so I didn’t feel any urgency” is a root cause, and it’s infinitely more useful.

    Surface symptoms can have deep causes. A reader who says a chapter is slow may actually be saying they’ve lost track of what’s at stake. A reader who says a character feels flat may actually mean the character’s desire isn’t clear. Symptom-level feedback requires ferreting out what’s underneath it.

    Would implementing it make your story more itself, or more like something else?

    Good feedback helps a story become a better version of what it’s trying to be. It clarifies, sharpens, deepens. It pushes the story further in its own direction.

    Feedback that tries to turn a story into a different story is not helpful, nor valuable feedback to take. “I would have written it differently” is not a note. Prescriptive solutions without explanation—“cut this character,” full stop—aren’t notes either. A real note says what isn’t working and why. The solution is the author’s to find.

    Red Flags and Green Flags

    Some feedback patterns are worth flagging immediately.

    Watch out for: vague praise or criticism without specifics (“I didn’t connect” tells nothing useful without a where or why); contradictory taste masquerading as craft (“some readers want more romance, some want less”—that’s audience preference, not a fixable problem); and prescriptive rewrites that reveal what the reader would have written, not what this story needs.

    Look for: multiple readers noticing the same pattern independently; feedback that identifies what isn’t working even when the reader can’t articulate why; confusion that reveals unintentional ambiguity (you meant X, they read Y. That gap is real and worth closing); and questions that show genuine engagement (“Why did she do this? I felt like I missed something”).

    That last one is gold. A reader asking questions is a reader who was invested enough to want answers.

    When Feedback Contradicts Itself

    Don’t implement contradictory suggestions. Instead, diagnose what’s causing readers to split.

    If some readers say “too slow” and others say “too fast,” the real issue is probably uneven pacing: some sections drag while others rush. If some readers love a character and others actively dislike her, the real issue might be inconsistent characterization—she’s compelling in some scenes and opaque in others. Look for the pattern beneath the contradiction. It’s almost always there.

    Beta Reader Mismatch Is a Real Thing

    Sometimes “bad” feedback just means that individual was the wrong audience. Romance readers beta-reading literary fiction will want different things. Adult readers beta-reading YA may not connect with a teen voice on its own terms. Cozy mystery readers beta-reading dark fantasy may find the tone too heavy.

    Before discounting feedback entirely, ask whether the beta readers were actually your target readers. If they weren’t, their responses indicate how the book lands with the wrong audience, which is useful to know, but not useful to fix.

    What to Do When You’re Drowning

    Beta feedback is data, not directives. The author’s job is to look for patterns, identify root causes, and make strategic decisions about what serves the story—not to implement a committee’s vision of what it should be.

    Trust your instincts. If a note feels wrong, it might be. But if multiple readers flag the same experience, independently and without prompting, pay attention. That’s the process working.

    If you’re deep in conflicting feedback and can’t find the pattern beneath the noise, that’s exactly what a Story Ecosystem Assessment is designed to help with. An outside eye can filter signal from noise, identify root causes beneath surface symptoms, and help you understand what’s actually not working versus what’s simply reader preference.

    Your manuscript isn’t broken. You just need the right diagnostic lens.

    Story Ecosystem Assessment™

    Subscribe

  • Your Theme Is a Noun. That’s the Problem.

    The answer to this question unlocks your entire revision.

    A ginkgo tree sprout in sand
    Photo by Jeremy Bishop on Unsplash

    There’s a question that comes early in almost every developmental edit, and the answer tells me more about what the revision needs than almost anything else in the manuscript.

    What is this story about?

    Not plot. Not premise. Theme.

    The answers fall into two categories, and they predict very different revision conversations.

    The first kind: “It’s about grief.” Or loneliness. Redemption. Identity. Belonging. A single word, sometimes two. A topic.

    The second kind: “It’s about how grief isolates you before it can connect you to anyone.” A sentence. A claim. A point of view the story is willing to defend.

    Both writers know what their story is about. Only one knows what their story believes.

    Why the sentence changes everything

    A noun theme is a container. It marks the emotional territory the story is exploring, but it doesn’t plant a flag anywhere inside that territory. Two novels can both be “about grief” and arrive at completely opposite conclusions about human nature. The noun doesn’t distinguish them. The sentence does.

    Consider a hypothetical manuscript—a quiet literary novel about a woman returning to her childhood home after her mother’s death to sort through the estate. The theme: “grief and memory.”

    Workable. But revision with that theme is like weeding without knowing what was planted. Something feels off, but there’s no way to articulate why, and no reliable basis for deciding what to cut, what to expand, what the ending needs to earn.

    Now the theme gets rephrased: “The things we inherit from the dead are never what we expected to want.”

    Suddenly the manuscript has a thesis. Revision has questions. Does the protagonist’s arc support that claim? Does she move from expecting one kind of inheritance to recognizing another? Are the objects she sorts through doing thematic work, or are they just set dressing? What does the ending need to deliver in order to feel like the story kept its promise?

    Nothing in the manuscript changed. The lens did.

    The revision test

    A thematic sentence makes a simple scene-level filter possible: is this scene evidence for the claim, a complication of it, or neither? Evidence and complication both belong—they’re the system working. “Neither” is where the hard questions start.

    This doesn’t mean every scene needs a theme stamp on it. Feeder roots don’t announce themselves. But they should be there, quietly pulling the story toward what it believes, even in scenes that look like they’re just advancing plot.

    A thematic noun can’t generate that test. A sentence can.

    The one-sentence exercise

    When theme is currently a noun, try finishing this sentence: “This story believes that ____.”

    Not “this story is about.” Not “this story explores.” Believes. The word forces a claim. It forces a verb. It forces the story to have a position rather than just a subject.

    The claim can be softened later. The nuance, the complication, the place where the story resists its own thesis—that’s where the most interesting thematic work usually lives anyway.

    But a claim that hasn’t been made yet can’t be complicated.

    Start with the sentence.

    If you try the exercise and the sentence won’t come, or keeps shifting, that’s worth paying attention to. It’s usually what a developmental edit unearths early on.

    Subscribe