Overextended stories and overplanted gardens have the same symptom: everything looks more or less okay. Nothing is actually growing.

The diagnosis of what needs to be reduced is harder than it looks.

When beta readers all say a manuscript is 'fine,' does that read as a green light or a warning sign?

For me it's the latter. 'Fine' means the story is surviving. Not the same thing as thriving.

A craft-competent manuscript that still feels flat usually isn't missing anything. It's overextended. Too many elements drawing on the same limited pool of reader attention.

The fix is focus, not addition.

What’s a book you finished that felt true even if the ending wasn’t what you wanted?

Thinking about the difference between satisfying and accurate.

What makes an ending feel true to you as a reader — resolution, or recognition?

I find the answer varies more by reader than by genre.

Twist and earned ending aren't synonyms. One surprises. The other settles something the reader didn't know was open.

photo of The Narrative Gardener the person with the title of the article about her, The Gate.

Three years of hiding behind a drawing of myself. Not because she wasn’t true—she was. But there’s a difference between accurate and present.

New photos. Finally closing that distance.

Spring cleanup rule: cut back before you plant anything. You need to see what actually survived before you decide what's missing.

Manuscript drafts work the same way.

Spent 5 hours outside on Saturday. Highly recommend the garden as a place to stop solving problems and let your brain go quiet for a bit.

The problem will still be there when you come back. But you'll be better at it.

The writers who get the most from a dev edit aren't the ones with the cleanest drafts. They're the ones who come in knowing the process will ask something of them.

Openness to that is its own kind of preparation.

Contradictory beta feedback isn't a sign the draft is a mess. It often means there are real strengths and real ambiguities. That's actually a good place to bring in a dev editor.

Chaos from readers is workable data.

"Said" isn't weak. "Said" becomes invisible, which is the point.

If your dialogue tag is drawing attention to itself, something's off—either the tag or the line it's attached to.

The goal is a reader who hears the voice, not one who notices the label.

Iteration doesn't always mean more. Sometimes the second pass reveals what to remove. Knowing which is the whole skill.

Subtraction is still revision.

Iteration isn't a sign the first version failed. It's evidence the thing is still alive.

Finished things don't iterate. Growing things do.

Dormancy isn't stagnation. Sometimes the ice has to form before you can see the branch clearly. Iteration starts with the thaw.

The rested eye isn't a reset.

Romantasy isn't dying. It's differentiating. The ones standing out now feel specific in a way the wave didn't require before.

The romantasy conversation has shifted from "is this good?" to "is this distinct?" That's not a smaller bar. It's a different one.

A plot hole and a logic gap aren't the same problem. A plot hole breaks causality. A logic gap just needs a bridge the writer hasn't built yet.

When you realized your manuscript was using a recognizable trope, did you lean into it or try to write around it? Curious whether that instinct helped or made things harder.

Subverting a trope and executing one well are different skills. Subversion requires the reader to know the original. Executing a trope well requires the story to earn it regardless.

Knowing which one you did changes where you look for the fix.

A trope isn't a cliché.

A cliché is a trope that forgot to earn its moment.

I’m skeptical of the idea that themes should be invisible. Readers don’t need subtlety so much as coherence.

But at what point does reinforcing a theme become overstatement?

Introducing a framework I've been building: Narrative Ecology. Reading manuscripts the way a horticulturist reads a garden. Not 'what's broken?' but 'what's out of balance?'

When writers say they want a theme to feel “organic,” I often find they mean it’s embedded in character choice rather than explained in narration.

Where do you see theme surfacing most effectively in your own work?

A story's theme isn’t the topic. “Grief” is a topic; “Grief isolates before it connects” is a thematic claim.

What changes in revision when you phrase your theme as a sentence rather than a noun?

When I feel blocked, I usually ask: what decision am I avoiding on the page? Plot, voice, scope, or stakes?

Naming the decision often loosens the work.

I’m not convinced ‘writer’s block’ is a single problem. Sometimes it’s a drafting problem, sometimes a decision problem, sometimes a permission problem.

Which of those shows up most often for you?”

Craft advice: "Raise the stakes! Add conflict! Make dialogue snappier!"
Me, a horticulturist: "Cool but have you considered your story might be root-bound?"

New post on why treating your manuscript like a living system beats treating it like a craft checklist: redleafwords.com/what-is-narr...

Omniscient POV isn’t just “multiple heads at once.” It’s a distinct narrative intelligence with its own distance, judgments, and permissions. How much is that narrator is allowed to know and comment on?

I'm interested in where authors or readers draw the line between knowledge and interpretation.

POV isn’t just “whose head we’re in;” it’s which information the story is allowed to notice and explain. Ask yourself, when a scene feels slippery, is it a character problem—or an information problem?

I see many POV issues as boundary drift rather than inconsistency.