When your editor wants to cut your favorite scene

Just got notes back and my editor wants to axe what I consider the emotional heart of chapter seven—you know, that perfect little moment that took me three months to get right. Anyone else ever have to murder their actual darlings, not just the pretty sentences?

The sentence-level version of this is when you've crafted what you think is the perfect transition and your editor circles it with "unnecessary." But with scenes, I've learned to ask: is this moment serving the reader's experience or just my attachment to the writing process? Sometimes we fall in love with our problem-solving rather than the solution itself.

This is where reading outside the Western editorial tradition helps. In Igbo storytelling, what seems like digression is actually spiral narrative—each apparent tangent deepens the center. Your "heart of chapter seven" might be serving a different structural logic than your editor recognizes.

That's brilliant, Amara. I've started asking editors to articulate what they think a scene accomplishes before cutting it. Half the time they realize they misread its function—what looks like indulgence is actually doing structural work they didn't catch.

Sometimes the scene that feels most essential to us is doing emotional work for the writer, not narrative work for the reader. I've had to learn the difference—especially with my poetry, where every line feels like a small miracle until I realize it's just therapy masquerading as art.

The story here is always: whose version serves the book? I had an editor want to cut twelve pages about Moses' early surveying work from my second book. Felt like cutting the foundation. But she was right—it was backstory I needed to write to understand him, not story readers needed to understand the book.

But here's what fascinates me—in Caribbean oral tradition, the audience participates in deciding what stays. If a story element doesn't land, the listeners literally redirect you. Maybe we need to trust our editors as that first audience, even when it stings.

Exactly—and this is why I always tell my students to read their work to someone from a completely different literary tradition. I once shared a story with my grandmother in Lagos, and she immediately identified the scene that wasn't working. "Why are you telling me what I already know?" she asked. Brutal clarity.

The hardest part is when they're right and you know it. I've had editors cut scenes that were gorgeous on the page but stopped the story cold. (One existential crisis per draft, right?) The real question becomes: am I fighting for the scene or for my ego's attachment to having written it?

The brutal test I use: can I explain why this scene exists without using the word "because"? If I have to justify it with logic, it's probably not earning its place. The scenes that truly belong announce themselves through necessity, not argument.

Ah, this reminds me of working with my editor on my poetry collection—she kept flagging what she called "scholarly tangents" until I explained they were praise songs, a form she didn't recognize. Sometimes the fight isn't about the scene itself but about expanding what counts as necessary in storytelling.

This reminds me of Chinua Achebe's editor wanting to cut the palm wine scenes from Things Fall Apart—they seemed "tangential" to Western narrative logic. But those scenes carry the entire cosmology. Sometimes what editors read as excess is actually the text's breathing space.

The question becomes: are we defending the scene's function or just our process of discovery? I've noticed my most defensible scenes are the ones that teach me something about the character I didn't know before—but that doesn't always mean the reader needs to witness that revelation.

I've learned to save those cut scenes in a separate document called "Beautiful Corpses." Nine times out of ten, when I revisit them months later, I can see exactly why they had to go. But that tenth time? That scene finds its way into the next book where it actually belongs.

Sometimes I think the real skill isn't writing beautiful scenes—it's recognizing when a beautiful scene is in the wrong book. My "chapter seven heart" might be the opening of novel five. (Though telling my editor that felt like negotiating with a hostage taker.)

Had an archivist once tell me: "The documents that survive aren't always the ones that mattered most—they're the ones that served the story future generations needed to hear." Same logic applies. Your favorite scene might be historically accurate but narratively redundant.

The archivist analogy is perfect, James. I'm realizing my attachment to that scene wasn't about its necessity—it was about the three months I spent wrestling with it. But readers don't experience our process, they experience our choices. Maybe the real craft is learning when to let the struggle go.

The sentence-level version of this: I once spent hours perfecting a metaphor about light through venetian blinds, only to realize it was interrupting a character's moment of decision. The metaphor was beautiful—and completely wrong for that paragraph. Sometimes our best writing is our worst editing.

That venetian blinds thing hits hard, Darnell. I have a whole graveyard of perfect sentences that murdered perfectly good scenes. The cruelest part? My editor was gentler about cutting my "heart of chapter seven" than I was about cutting that metaphor. We're often our own harshest executioners.

The hardest cut I ever made was a 2,000-word section on Civil War telegram operators—pure gold from the archives, voices I'd spent months tracking down. But it was slowing the narrative to a crawl. Sometimes the most fascinating research makes the worst storytelling.

That telegram section sounds like it belonged in a different book entirely—maybe one focused on communication during wartime rather than your main narrative thread. I've started asking myself: is this scene advancing *this* story, or is it just good material that happened to surface during research?

Exactly. I've started treating my proposals like archaeological site maps—every chapter has to justify its position in the larger dig. That telegram section? Probably belonged in a book about information networks, not battlefield strategy. The archives seduce us with their abundance, but the story demands we choose.

That archaeological metaphor is perfect—I'm stealing it. The sentence-level version: every clause has to earn its place in the paragraph, not just be interesting on its own. I've started reading scenes aloud to hear where the narrative actually pauses versus where I think it should.

In poetry, we call this the "darling massacre"—when a line sings perfectly but breaks the poem's spine. En español, we say "matar a tus hijos"—kill your children. The translator in me knows: what survives isn't always what's most beautiful, but what serves the whole.

Reading aloud is the ultimate lie detector for prose—you can feel exactly where the rhythm breaks, where you're performing the writing instead of serving the story. That telegram section probably sounded gorgeous in your head, James, but I bet it felt like trudging through mud when spoken.

Rosa's "matar a tus hijos" cuts deep—but I wonder if that metaphor reveals something colonial about how we think of texts. In Igbo storytelling, nothing truly dies; it transforms. Maybe our "killed darlings" aren't corpses but seeds waiting for the right soil in future work.

Rosa's "matar a tus hijos" cuts to the bone—we create these perfect little beings and then have to sacrifice them for the larger work. I keep thinking about that telegram section living in James's files, waiting for its proper home. Maybe the real tragedy isn't the cutting, but when we don't save those beautiful corpses for resurrection.

The story here is always about serving the reader, not preserving our process. I just reread that telegram section—it was brilliant research wrapped in beautiful prose that completely derailed chapter momentum. The voices were authentic, the details vivid, but it belonged in a footnote, not the narrative spine.

That metaphor of serving the reader versus preserving process hits differently when you consider whose reading practices we're centering. Wole Soyinka's editors initially resisted his time-shifting techniques because they violated linear Western narrative expectations—but Yoruba storytelling had been doing this for centuries.

The reader-serving question gets thorny when we consider that editors often represent a very specific reading tradition. I've watched MFA students gut gorgeous, culturally-specific narrative rhythms because workshop consensus favored familiar pacing. Sometimes "serving the reader" becomes code for serving the most conservative reader in the room.

James's telegram research reminds me of my own attachment to praise song structures—my editor kept asking "but what does this do for the plot?" until I realized she couldn't see how the circular repetitions were building emotional architecture. Sometimes what looks like narrative wandering is actually a different kind of storytelling logic.

The sentence-level version: I've started distinguishing between scenes that *feel* necessary to me versus scenes that *function* for the reader. That telegram section probably felt essential because of your research investment, but function-wise it was beautiful static interrupting the signal.