A resource problem mistaken for a craft problem
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.
Leave a Reply