Most writers believe revision means reading through the manuscript once, catching typos, smoothing clunky sentences, and calling it done. The truth is almost the opposite: effective revision barely touches sentences at all -- at least not in the beginning. It starts with something far more unsettling. It starts with being willing to tear apart the thing you just spent months building.
Raymond Carver's editor Gordon Lish once cut seventy percent of his manuscript. Seventy. An entire book reduced to less than a third. Carver was devastated. But those stripped-down versions became cornerstones of American short fiction. Every passage that felt essential -- the careful descriptions, the contextual explanations, the atmospheric padding -- turned out to be fat smothering the real story underneath.
Hemingway said it. Anne Lamott said it. Neil Gaiman said it. Writing is rewriting. The first draft digs the story out of your skull. Revision is what makes it legible to anyone who isn't you.
But revision is not one task. It's a layered process, and the layers have a strict order.
Think about renovating a house. Nobody picks curtain colors while debating whether to knock down a wall. Structure comes first -- which rooms exist, how they connect, whether the floor plan works. Then each room's function and furniture. Paint colors and cabinet handles come last. Revision follows the same logic. Large to small. Skeleton to skin. If you're still wondering whether an entire chapter should be cut, there's no point polishing the punctuation inside it.
Before You Begin: Build a Safety Net
One thing before anything else.
Open the Version Control panel (Cmd+Shift+G or Ctrl+Shift+G) and create a Snapshot of your first draft. Name it "Pre-Revision - Complete First Draft."
This snapshot is your safety net. Whatever happens next -- chapters deleted, timelines reorganized, an entire subplot ripped out -- you can return to this exact version with a single click.
That matters more than it sounds. So many writers revise timidly, nibbling at the edges, adjusting a word here, swapping a paragraph there -- never touching the parts that genuinely need surgery. Why? Because they're terrified of losing something that can't be recovered. With the snapshot in place, that fear evaporates. The chapter you've been afraid to cut? Cut it. See what happens. If the story falls apart without it, restore it. Cost: zero.
Bold revision requires a safety net. Build it first.
Round One: Structure -- Is Your Story's Skeleton Right?
First pass. Macro only. Ignore every sentence-level flaw. Focus entirely on the bones.
Open the draft not to revise but to answer a handful of questions:
- Does the story have a clear beginning, middle, and end?
- Does the protagonist have a goal strong enough to carry the entire narrative?
- Does the protagonist undergo genuine internal change -- not just a shift in circumstances, but a psychological transformation?
- Is the ending driven by the protagonist's own choices, or does it depend on coincidence and external forces?
Then examine pacing. Where does the story drag? Where does it sprint past something that needed room to breathe? Does the second act sag? Does the climax arrive too early, too late, or without enough force?
Using AI to Check Story Structure
Seeing structural problems in your own work is notoriously difficult. Slima's AI Assistant can serve as a second set of eyes for exactly this purpose. Press Cmd+Shift+A (Mac) or Ctrl+Shift+A (Windows), and try a prompt like this:
Please analyze my story structure. Check the following:
1. Is the beginning too slow? Where does the real story start?
2. Does the middle sag? Are there scenes that can be deleted or merged?
3. Is the climax scene powerful enough?
4. Is the ending determined by the protagonist's choices?
5. Are there overall pacing issues?
Please analyze using all chapters in the @chapters/ folder.
The AI scans your entire manuscript and flags structural concerns. The point is not to accept every suggestion. The point is to borrow a perspective you physically cannot generate yourself -- the perspective of someone encountering this story for the first time.
Three Common Structural Problems
After reading countless first drafts -- my own and others' -- three problems recur with the reliability of gravity.
Slow openings. Hemingway's advice: cut your beginning and you'll find the real beginning comes after. Most first drafts spend their opening chapters warming up. Characters wake up, eat breakfast, commute, make small talk, dump backstory. The actual story -- the event that sets everything in motion -- often doesn't arrive until chapter four. Ask yourself a brutal question: what is the latest possible point where the story can begin without losing essential information?
Saggy middles. Act Two occupies roughly half the book, and it's where most writers lose their way. The narrative softens. Tension leaks. Readers start checking how many pages are left. The fix: make sure something in the middle fundamentally changes the direction of the story. A reversal. A revelation. A decision that can't be undone. And audit every scene in this section -- if it doesn't push the story forward, cut it.
Rushed endings. By the time a writer reaches the final chapters, exhaustion has usually set in. The climax gets compressed. The protagonist's transformation is summarized instead of shown. Subplots that were carefully seeded just... disappear. The ending deserves at least as much attention as the opening. Probably more.
After completing the structural pass, return to Version Control and create a new Snapshot: "Structural Revision Complete." Use Diff View to compare before and after -- see exactly how much you moved, cut, and rebuilt.
Round Two: Scenes -- Is Every Brick in the Right Place?
Skeleton confirmed. Move down one layer: scenes.
Examine each one individually. Three questions per scene.
What is this scene's reason for existing? Is it advancing the plot? Revealing something about a character? Building the world? Generating emotional tension? If you can't name a function, seriously consider cutting it. Good scenes usually accomplish more than one thing simultaneously. A scene with only one function barely passes. A scene with no function doesn't belong.
Does this scene contain conflict? Conflict doesn't require shouting matches or fistfights. A character wanting something they can't have -- that's conflict. A character facing a choice where both options cost something -- conflict. A character wrestling with their own fear, desire, or belief -- conflict. Scenes without conflict are flat. Like lukewarm water. Drinkable but flavorless.
Is the world different when the scene ends? Relationships shifted. Information changed. Circumstances altered. The character's internal state moved. Any kind of change counts. If everything is identical before and after a scene, that scene is almost certainly excess weight.
One more principle, borrowed from screenwriting: enter late, leave early.
Many writers start scenes with characters walking into a room -- greeting each other, sitting down, ordering coffee, making small talk before arriving at the point. All of that is entering too early. Similarly, the critical event has already happened but the scene continues -- characters say goodbye, walk to the door, look back over their shoulder. That's leaving too late. Find the moment each scene truly begins and truly ends. Everything before and after those points? Delete it.
Using Split Window for Side-by-Side Revision
Press Cmd+ (Mac) or Ctrl+ (Windows) to open Slima's Split Window. Outline on the left, chapter on the right.
Cross-reference constantly: where does this scene sit in the outline? What function was it supposed to serve? Does the current version actually deliver?
When a scene has drifted from the plan -- maybe it's gone off-topic, maybe it's not achieving its intended effect -- press Cmd+Shift+A to summon the AI Assistant:
This scene's purpose is to reveal the antagonist's motivation.
Please check whether my current writing achieves this purpose.
If not, give me specific revision suggestions.
Round Three: Sentences -- Polishing Every Word
Skeleton: confirmed. Scenes: confirmed. Now -- and only now -- focus on the sentence level.
The single most powerful sentence-revision technique is embarrassingly simple. Read your work out loud.
Ears are more honest than eyes. When you read aloud, clunky rhythms expose themselves. Repeated words become grating. Overly long paragraphs make you run out of breath. Dialogue that no human would actually say -- those lines that sounded fine in your head -- suddenly sounds absurd coming out of your mouth. If it feels awkward to speak, it's awkward to read. No exceptions.
Stephen King, in On Writing: "Kill your darlings."
Those sentences you're proudest of. The metaphor you spent an hour perfecting. The description so vivid you nearly wept when you wrote it. Look at them carefully. Are they serving the story, or are they serving your ego?
A passage that's beautiful but slows the narrative? Cut it. A metaphor that's clever but confuses the reader? Cut it. A description so detailed it moved you but contributes nothing to the plot? Still cut it. This isn't a poetry collection. It's a story. Everything must earn its place.
Using Search & Replace to Find Filler Words
Slima's Search & Replace (Cmd+Shift+F or Ctrl+Shift+F) becomes a surgical instrument during this round. Search for common fillers and inspect each occurrence:
- "very" "really" "quite" -- eight times out of ten, deletable
- "a bit" "slightly" "somewhat" -- these weaken every sentence they touch
- "then" "next" "and then" -- overuse turns narration into a lullaby
- "started to" "decided to" -- almost always replaceable with the action itself
Finding them is not the same as blindly deleting them. Some belong. Ask each one: is this word necessary here? Does a sharper alternative exist?
AI-Assisted Sentence Polishing
Select a passage that reads as "okay but not great" and run it through Slima's Quick Actions:
- Polish: preserves the original meaning, improves flow
- Condense: keeps core information, reduces word count
- Rewrite: expresses the same idea in an entirely different way
These are tools, not replacements for judgment. The AI's version won't always be better than yours. But it opens a window -- showing you possibilities for the same paragraph that you wouldn't have considered. The final call is always yours.
Multi-Round Revision Workflow
Expecting one pass to fix everything is a fantasy. Professional writers run multiple rounds:
- Structure -- may require major rewrites, chapter relocations, entire plotlines removed
- Scenes -- cutting scenes that serve no function, adding scenes that are missing
- Dialogue and pacing -- making each character's voice distinct, adjusting the rhythm of fast and slow
- Sentences and word choice -- polishing every line, eliminating filler
- Final polish -- typos, punctuation, formatting
Each round addresses one layer. Don't try to fix everything simultaneously -- that path leads to fixing nothing well.
In Slima, create a Snapshot for each completed round:
Revision History/
+-- Complete First Draft
+-- Structural Revision Complete
+-- Scene Revision Complete
+-- Dialogue Revision Complete
+-- Sentence Revision Complete
+-- Final Polish Complete
These snapshots aren't just backups. They're a record of your evolution as a writer. Months later, use Diff View to revisit each round. See what you cut. What you added. What you reshaped. Those changes are the tangible proof that you're getting better.
Want to try something radical during a round -- switching from third person to first person, maybe, or fracturing the timeline? Use Branches. Create a branch, experiment freely, and if the result works, merge it back to the main line. If it doesn't, leave it as a record of what you tried. Nothing lost.
Self-revision goes far, but it has one wall it can never climb: you only have one pair of eyes. No matter how much time passes, no matter how hard you try to adopt a reader's perspective, you are still the author. You know what you intended. That knowledge warps what you see -- filling gaps that actually exist on the page, smoothing over passages that a fresh reader would stumble on.
So eventually, you need someone else's eyes.
The next article covers how to get feedback from multiple angles -- from real human readers, and from Slima's AI Beta Readers. Each source of feedback has unique strengths. Each has blind spots. Together, they give you something self-revision alone never can.
Carver lost seventy percent and became one of America's most important short story writers. Revision isn't punishment. It's the process that separates a rough draft from a finished work.
Open Slima. Create your first revision Snapshot. Then start cutting.