Why Can't I Finish My Stories?
Quick answer: Why you can't finish your stories: the five real causes, from perfectionism to missing endings, and the specific fix for each one. A practical diagnosis.
You cannot finish your stories for one of five findable reasons: you revise while drafting, so momentum dies; you start without any ending in mind, so the middle has no direction to fall; the idea is a situation rather than a story, so there is nothing to finish; new ideas outglow the hard middle, so you defect; or finishing itself feels dangerous, because a finished story can be judged and an unfinished one cannot. Identify which of these is yours and the cure is usually direct.
The diagnosis matters because 'I never finish' feels like a character flaw and is almost always a process fault. Serial non-finishers routinely become reliable finishers within months once they stop treating the problem as shameful and start treating it as mechanical.
The longer answer: five causes, five signatures
Cause one, mid-draft revision, leaves an unmistakable signature: gorgeous, heavily reworked openings and no middles. You reread yesterday's pages, repair them, exhaust the session's energy on old ground, and the frontier never advances. Cause two, no destination: you write brilliant setups and stall at the exact point where setup must convert to consequence, usually a third of the way in. Discovery writing is legitimate, but even discovery writers need a direction of travel, an image, a final line, a fate, if not a route.
Cause three, situation mistaken for story: 'a lighthouse keeper who collects messages in bottles' is a situation; until someone wants something and something resists, there is no engine, and drafts without engines coast to a stop regardless of how vivid the premise felt. Cause four, novelty defection: the new idea is perfect because it is unwritten, the current draft is flawed because it exists, and the comparison is rigged; writers with folders of openings are living inside this loop. Cause five, fear wearing a disguise: finishing converts potential into evidence. While the story is unfinished you might be brilliant; once it is done, someone, including you, can find out. That fear dresses itself as perfectionism, as busyness, as 'this one was not working anyway'. Most chronic non-finishers are running cause five underneath one of the others.
The fixes, matched to the causes
For mid-draft revision: forward-only rules, no rereading past the last paragraph, brackets for every problem, and revision formally scheduled for after the end. For no destination: before drafting, write the ending as one sentence, even provisionally, 'she sells the boat and does not tell him'; you may betray it later, but the middle now has gravity. Raymond Chandler plotted loosely but always knew the shape of the reckoning.
For situation-not-story: run the engine test on every idea before drafting. Who wants what? What resists? What changes? Thirty seconds of interrogation saves three weeks of coasting. For novelty defection: keep an ideas file with a strict ritual, two sentences per new idea, then back to the draft, and finish-before-start as a standing rule; the new idea will still be there, and the ones that stay bright through a whole draft are the ones worth writing next.
For fear: shrink the judgement. Finish small things first, flash pieces, 500-word stories, so 'finished' stops being a cliff and becomes a habit. Then let real, survivable verdicts arrive: share with one reader, or enter a contest where feedback is structured rather than social. Writory's monthly story contest returns a five-part score out of 100 to every entrant, which quietly retrains the nervous system: judgement happened, numbers arrived, nobody died, next story.
A finishing protocol you can run this month
Week one: pick your smallest live idea, run the engine test, write the provisional last line on an index card, and draft to 60 percent under forward-only rules with a 300-word daily floor. Week two: cross the middle by whatever means required, bracketed holes, summarised scenes, '[the argument, she loses]', and reach the ending on the card or the better one that shows up en route. The middle is not where drafts should be good; it is where they should be continuous.
Week three: cool for three days, then revise in two passes, structure first, sentences second. Week four: send it somewhere real, one magazine, one contest, one trusted reader, and log it as finished in a list you keep visible. That list is the actual therapy. Non-finishers own no evidence of being finishers; every logged completion rewrites the identity a little, and identity, not talent, is what was broken. Repeat monthly, and let the pieces stay small until finishing feels boring. Boring is the goal. Finishing should eventually feel like closing a door: unremarkable, done, next room.
Misconceptions that keep the loop running
Misconception one: 'real writers finish because they love their stories throughout'. False; mid-draft disenchantment is close to universal, and professionals finish through it, not without it. Steinbeck's journals during The Grapes of Wrath alternate between quota-keeping and despair. Misconception two: 'I have too many ideas', framed as a curse of abundance. Idea count is not the problem; the missing finish-before-start rule is.
Misconception three: 'if it were the right story, it would finish itself'. No story finishes itself; endings are built during the least glamorous hours of the process. Misconception four: 'I need a big block of free time'. Chronic non-finishers with free weeks produce longer unfinished drafts; the fix is cadence, not volume. And the last one, quietly the most damaging: 'abandoning is failing'. Strategic abandonment of a genuinely broken premise, named in one sentence, is a professional act. The pathology is not stopping one story; it is the pattern where stopping is the only ending you ever write.
What poets can take from this
- Diagnose first: reviser, no-destination, no-engine, defector or afraid; the fixes differ.
- Write a provisional final line before drafting; betray it later if the story insists.
- Run the engine test on ideas: who wants what, what resists, what changes.
- Log every new mid-draft idea in two sentences, then return; finish before starting.
- Make finishing small and frequent until it bores you.
- Keep a visible finished list; identity repair happens one logged completion at a time.
Try it yourself
Open your abandoned-drafts folder and choose the one you abandoned closest to its end. Write only its final scene today, out of sequence, then build the shortest bridge from the abandonment point to that scene. Log it as finished.
Questions
Is it okay to abandon a story?
Sometimes, yes: if you can state in one sentence why the premise cannot work, abandonment is editing at the project level. The warning sign is pattern, not incident. If every story dies at the same percentage mark, the cause is process, and the next story deserves the diagnosis, not the drawer.
Why do I lose interest in my story halfway through?
Because the middle is where a story stops running on the premise's novelty and starts requiring consequences and decisions. Interest loss at the midpoint is structural, not romantic; a provisional ending, a raised-stakes scene or a new complication usually restarts the engine.
Does finishing get easier?
Dramatically. Finishing is partly skill, endings improve with practice, and partly identity: after five or six logged completions, the mid-draft crisis loses its authority because you have survived it before. The first three finishes are the expensive ones.
By the Writory editorial team, reviewed by working poets. Updated July 2026.
Enter a Writory poetry contest
Enter the August contest and have your own poem read and scored.