The Narrative Gardener

Category: writing craft

  • 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

  • What’s Actually Keeping Your Story Alive

    What readers feel but can’t name is usually theme doing its job.

    Closeup of a root mass

    Every spring, there’s a week in the garden when nothing looks like it’s happening.

    The beds are bare, or close to it. Whatever was planted in autumn is still underground, doing work that won’t be visible for weeks. A gardener who’s new to the season might look at that soil and see nothing—no evidence of effort, no proof anything survived the winter. An experienced one knows better. The quiet surface is usually the sign of a root system earning its keep.

    Theme in a story works the same way.

    The part that gets all the attention

    When writers talk about their stories, they talk about plot. Readers talk about plot. Query letters lead with plot. Editors examine plot. There’s good reason for this; plot is visible. It moves. It creates pressure and release, problem and consequence, scene and sequel. It’s the stem, the leaves, the bloom. It’s the part you can point to and say “here is where the story is.”

    But plot is not what keeps a story alive.

    What keeps a story alive is the hidden network underneath it. The fine, almost invisible strands running just below the surface. Not the taproot of premise, not the thick roots of character arc, but the feeder roots. The small, threadlike filaments that don’t announce themselves. They just quietly pull everything the story needs to stay nourished.

    That’s theme.

    What feeder roots actually do

    In horticulture, feeder roots are the fine, hair-like roots responsible for the actual uptake of water and nutrients. They’re not structural. They don’t anchor the plant. They’re not the part anyone sees when they dig up a shrub or pot a perennial. But remove them, damage them, ignore their health, and the plant shows it—not immediately, not dramatically, but in a slow, creeping way that’s hard to diagnose until you look below the surface.

    A story with weak theme does the same thing. It might have a perfectly competent plot. The characters might be well-drawn. The dialogue might crackle. But something feels thin. A reader closes it and can’t quite say why it didn’t land. There’s no single scene to point to, no obvious structural failure. Just a vague sense that the story didn’t feed them the way they expected it to.

    The feeder roots weren’t doing their work.

    The excavation problem

    Here’s what makes theme genuinely difficult to work with in revision: writers are often taught to add it. To go back through a draft and insert thematic resonance, find the symbols, make sure the character’s journey “means something.”

    That’s not how theme works. You can’t transplant feeder roots. They either grow from the story’s own root system, or they don’t take.

    The work of finding theme in revision isn’t addition. It’s excavation. Tracing back what’s already alive in the story to the hidden system sustaining it. What does this story keep returning to without being told to? What question can’t it stop asking? What does it seem to believe, underneath all the plot, about the way the world works?

    Those answers are almost always already there. The feeder roots exist. The revision work is learning to read them and then making sure the rest of the story is actually drawing from them.

    When the roots are working

    When theme is working well in a manuscript, it rarely announces itself. It shows up instead in the weight a particular scene carries. In why a throwaway moment between minor characters lands harder than expected. In the reason a reader closes the book feeling something they can’t quite name, moved by something they couldn’t track while it was happening.

    The feeder roots did their job. The reader felt fed.

    The parts readers see aren’t always the parts doing the work. That’s not a flaw in how stories function. It’s exactly how they’re supposed to.

    If you’re in revision right now and something feels thin without a clear cause, it might be worth going underground for a bit. Not to add anything, just to see what’s already growing there.

    Subscribe

  • Stakes Are What Characters Believe They Can't Afford to Lose

    Readers don’t feel stakes. They feel what a character can’t imagine living without.

    Cypripedium acaule in the wild. Photo: me!

    A gardener doesn’t save a plant because the garden might look worse without it. She saves it because this clematis belonged to her grandmother, or because that struggling tomato represents the first thing she’s managed to keep alive in years.

    Stakes work the same way.

    When a character’s motivations feel abstract, when readers can’t quite feel the urgency even though the plot consequences are enormous, it’s rarely because the stakes aren’t high enough. It’s because the character hasn’t convinced us what they believe they stand to lose. Not in some theoretical future. Right now, in the reality they’re currently living.

    Plot Machinery vs. Belief at Stake

    A prophecy says the kingdom will fall? That’s plot machinery. It tells us something bad will happen to a lot of people in a future we haven’t lived yet.

    A prophecy says this character will become the very thing they’ve spent their whole life proving they’re not? Now there’s a belief at stake.

    The difference is that the second prophecy threatens something the character has already invested in. It puts at risk a story they’ve been telling themselves, possibly for decades, about who they are. And that kind of threat lands differently, because the reader can feel the weight of everything that’s already been spent defending it.

    This is why stakes that exist only in the future tend to fall flat, even when they’re technically catastrophic. Readers can’t feel a kingdom falling. They can feel a person discovering that the thing they were most certain about themselves might not be true.

    The Real Question Underneath the Stakes

    When I’m working with a manuscript where the tension isn’t landing, I often stop asking “what are the consequences?” and start asking something else entirely: What does this character think failure would mean?

    Not what would happen. What would it mean.

    Would it confirm the thing they’ve been dreading was true about themselves all along? Would it prove that they were right to never trust anyone or devastatingly wrong to start? Would it mean that every sacrifice they made was worthless, that the story they told themselves to survive was a lie?

    That’s the real architecture of stakes. Not the external consequence, but the internal verdict failure would deliver.

    A character fighting to save their village is fighting a plot. A character fighting to save their village because if they fail it will prove that their father was right—that they were never enough, that they’d ruin everything they touched—that character is fighting something that readers feel in their chest.

    The external stakes give the story shape. The internal ones give it weight.

    Why Abstract Stakes Create Abstract Tension

    What tends to happen when stakes stay at the level of plot consequence is readers understand intellectually that something bad will happen, but they don’t feel urgency. They’re watching the story rather than living it.

    Abstract stakes create abstract tension, the kind that produces mild concern rather than breath-holding. You can raise them as high as you want. End of the world. Death of everyone the character loves. Destruction of everything they’ve built. If the character hasn’t shown us what they believe they stand to lose—the specific, personal, identity-level thing—the reader remains at a safe observational distance.

    Specific beliefs are what collapse that distance. When we understand that this character has staked their entire sense of self-worth on a particular outcome, we can’t watch from outside anymore. We’re in it with them, because we know what failure would cost in a way that no amount of plot consequence can manufacture.

    What This Looks Like in Revision

    When I’m doing a developmental edit and the stakes feel flat, I’ll look for a few things.

    First: has the character articulated, to themselves or to us, what failure would say about them? Not what it would do to them. What verdict it would deliver. That distinction matters enormously.

    Second: is there a belief already established in the manuscript that the stakes are threatening? Stakes feel earned when they connect to something the story has already built. If the character has never shown us what they most need to believe about themselves, we won’t feel the threat when that belief is put in danger.

    Third: is the character aware of what’s really at stake, or only aware of the surface consequence? Sometimes the most powerful dramatic tension comes from a character who thinks they’re fighting for one thing while the reader can see they’re actually fighting to preserve a belief they can’t even name yet. That gap between what the character thinks they’re protecting and what they’re actually protecting is one of the richest places a story can live.

    The Clematis and the Tomato

    The gardener saves the clematis because it was her grandmother’s. She saves the tomato because it’s evidence that she can sustain something, that she’s capable of keeping things alive.

    Neither of those plants matters objectively. A garden assessment would tell her they’re both struggling and probably not worth the effort. But stakes aren’t objective. They’re personal, specific, already emotionally loaded before the crisis arrives.

    The best stakes in fiction work the same way. By the time the moment of reckoning comes, the reader should already know, because the story has shown them, exactly what this character believes they cannot afford to lose. Not the kingdom. Not even their life.

    The thing that would crumble if they failed. The piece of their understanding of themselves they’ve been tending, sometimes without even knowing it, for the entire length of the book.

    That’s what’s really at stake. And when readers feel it, they don’t just follow the plot.

    They hold their breath.

    Stakes are one of the most nuanced elements to diagnose in a manuscript and one of the most rewarding to untangle. If your story’s tension isn’t landing the way you want it to, a Story Ecosystem Assessment™ looks at exactly this kind of systemic question. Learn more here.

    Subscribe

  • A Story’s Point of View Sets the Rules for Curiosity

    What your narrator can’t—or won’t—see shapes everything your reader feels.

    a hornet's nest up in a tree in a forest
    Not everything that catches the eye is meant to be understood. Credit: me!

    What the narrator is allowed to wonder about shapes everything a reader experiences.

    A limited third-person narrator can’t casually speculate about what’s happening in the next town over. An omniscient voice can, but if it chooses not to, that silence becomes its own kind of information. A first-person narrator might fixate on a detail that seems irrelevant, and that fixation tells us as much about the narrator as the detail itself.

    Point of view isn’t just a technical choice. It’s the boundary around what gets to be interesting on the page.

    The Microclimate of POV

    Think of it like a garden’s microclimate. A shaded bed under oak trees can’t grow sun-loving tomatoes, no matter how much the gardener wishes otherwise. But it can grow hostas, ferns, hellebores (if they aren’t buried in snow!)—things that thrive in exactly those conditions. The limitation isn’t a flaw. It’s the environment that determines what flourishes.

    A close third-person POV creates a microclimate of immediacy and interiority. The narrator wonders what that look meant, whether the silence is angry or sad, why the room suddenly feels smaller. The reader is pressed up close against the character’s perception, living inside the gap between what’s observed and what’s understood.

    An omniscient narrator operates in full sun. It can see everything, move anywhere, tell us outright what a character feels or choose to withhold that information for effect. That withholding, when an omniscient narrator goes quiet, carries a different kind of weight than a limited narrator’s uncertainty because the reader knows the narrator could tell them. The silence is chosen.

    First person is its own microclimate entirely: the most intimate and the most unreliable. What the narrator notices, what they obsess over, what they skip past without comment, all of it is characterization. The reader is always reading two texts simultaneously: what the narrator says and what the narrator reveals without meaning to.

    Each POV creates conditions. The writer’s job is to know what grows there.

    When the Microclimate Gets Confused

    Here’s what tends to go wrong, and it’s more common than you’d think: the narrative voice starts wondering about things its POV can’t actually sustain.

    A close third-person narrator who suddenly speculates about another character’s childhood. A first-person narrator who describes their own facial expressions as though watching from outside. An omniscient narrator who dips into one character’s interiority so deeply and so consistently that readers forget it’s supposed to have a wider view, and then they feel jarred when it suddenly pulls back to tell them what’s happening across the kingdom.

    These aren’t always catastrophic errors. Sometimes they’re barely noticeable. But they erode something important: the reader’s trust in the container.

    When the rules of curiosity feel inconsistent, readers lose their footing. They’re not sure anymore what the narrator knows, what it’s allowed to know, or whether the boundaries will hold. That uncertainty doesn’t create productive tension; it creates a low-level unease, a sense that the story isn’t quite in control of itself.

    The fix usually isn’t to change the POV. It’s to understand what the chosen POV permits, and then be rigorous about staying inside those conditions.

    What This Looks Like in Editorial Practice

    When I’m working through a manuscript and scenes feel flat or slightly off, technically competent but missing something, POV confusion is often what I find underneath.

    Not the wrong POV choice. The right POV choice being inconsistently applied.

    I’ll ask: what is this narrator allowed to wonder about? Then I’ll look at what they’re actually wondering about. When those two things diverge, that’s usually where the flatness lives.

    Sometimes the narrator is failing to use the full range of curiosity their POV permits. A close third-person voice that reports events without ever speculating, questioning, misreading—that’s a narrator not taking advantage of the microclimate. The conditions are there for interiority and immediacy, and the story is growing lettuce in the shade instead of intricate, mysterious hellebores.

    Sometimes the narrator is reaching past what the POV can sustain, grabbing for information or certainty it hasn’t earned, or shouldn’t have. That’s the sun-loving tomato problem. The gardener keeps trying to force it, and the plant keeps struggling, and the problem isn’t the tomato. It’s that this bed doesn’t get enough light.

    Curiosity Has a Container

    The magic isn’t in choosing the “right” POV. Every POV is right for something. The question is always: what kind of curiosity does this container permit, and is the story growing things that thrive in those conditions?

    When a scene feels flat, it’s worth asking not just who the narrator is, but what this narrator is allowed to wonder about and whether the story is actually using that permission, or ignoring it, or accidentally exceeding it.

    Curiosity has a container. The story grows best when the writer knows its shape.

    And the editor’s job, sometimes, is simply to help the writer see the microclimate they’ve already created and understand what it was always capable of growing.

    POV is one of those elements that tends to reveal itself slowly across a full manuscript, which is exactly why it shows up in Story Ecosystem Assessments™. If something feels consistently off in your narrative voice and you can’t quite name what it is, that might be worth exploring. Learn more here.

    Subscribe