How I Used to “Be a Writer”

How building a tiny, repeatable system for short stories did more for my writing than three abandoned novels ever did

The email subject line said: “We loved this — can we pay you $150 to publish it?”

I stared at it for a full minute.

The “this” they were talking about was a 2,300‑word short story I’d written in a single weekend. No outline, no worldbuilding wiki, no “this is part of a trilogy” grand plan. Just a cramped Saturday at my kitchen table, an over‑steeped mug of tea, and a story about a burned‑out sysadmin who starts receiving error logs from ten minutes into the future.

Two days of work. One revision. $150.

I did a quick, slightly painful calculation.

If I divided the estimated hours I’d sunk into my “real” novel by how many pages I actually had, the short story had paid something like 50 times better per hour. Forget the money — the short story was finished. The novel was in a folder called WIP_3_FINAL_really_THIS_time.

That email landed at 2:17 p.m. on a Tuesday. By 2:25, I realized I’d been thinking about my writing life backwards.

How I Used to “Be a Writer”

For almost a decade, my creative identity ran on a single sentence:

“I’m working on a novel.”

I said it to friends, relatives, dates, coworkers. I said it enough that it felt true, even when my Scrivener file sat untouched for weeks.

My process looked impressive from the outside:

60K words across three different drafts

A Notion database full of character profiles and timelines

A folder of Google Docs labeled “Worldbuilding” with subfolders inside subfolders

But those numbers were gravity wells. The more pages I accrued, the heavier and more immovable the project felt.

Whenever I tried to return to the manuscript, I’d spend half an hour re‑reading “to get back into the voice,” then freeze at the next blank scene. I’d open Twitter, see someone celebrating their debut book deal, and think, “I just need to push through.”

Then I’d tweak a paragraph in chapter three for the seventh time.

I had a vague respect for short stories but quietly treated them as side quests. “Real” writers wrote novels. Stories were consolation prizes or warm‑ups. I’d occasionally jot down an idea, get to 800 words, and bury it in a “Fragments” folder.

So when a small speculative magazine accepted my short story, it felt like a fluke, not data.

The problem was: the data kept coming.

The Trigger: A Very Specific Kind of Burnout

The breaking point wasn’t dramatic. There was no big meltdown or “I’m quitting writing” post.

It was a Tuesday night in March.

I opened my novel file for the first time in a month. The word count still said 41,712 — the exact number I remembered from the last time I’d checked. After half an hour of reading, I tried to write a new scene, stared at the cursor, and closed the laptop.

I didn’t cry. I didn’t rage. I just felt…grey.

Walking to the kitchen, I heard myself think, “I’m tired of being the person who’s always almost writing a book.”

That specific phrasing annoyed me. It sounded like something from a productivity podcast.

So I did what I usually do when I’m annoyed: I opened a plain text file and started listing out what I was actually doing, not what I claimed to be doing.

The list was brutal:

3 abandoned novels in 7 years

0 finished long‑form manuscripts

9 short stories started, 1 finished

Average time between writing sessions on the novel: 11 days

Under that, I wrote one more line: “Finish something small on purpose. Then decide.”

I promised myself I’d suspend all novel guilt for 60 days and treat short stories as the main thing, not the side dish. If it went nowhere, I could go back to suffering nobly over chapter arcs.

The Build: A Tiny, Boring System for Writing Stories

I decided on a small, clear target: three finished short stories in 60 days.

Not “three published.” Not “three masterpieces.” Just “three stories with a beginning, middle, and end that another human can read without me hovering in the room explaining what I meant.”

The rule was: no story could take more than two weeks end‑to‑end. That forced me to build a process that fit real life.

Here’s what the first iteration looked like, roughly:

1. Constraints First

I picked a few constraints that would apply to every story, regardless of genre:

2,000–3,500 words

One main character, one central relationship

Takes place over 24 hours or less

At least one decision that can’t be undone

The point wasn’t to be artistic. It was to remove options. The fewer dials I could fiddle with, the harder it was to get lost.

2. 90‑Minute “Proof of Life” Draft

Instead of “write a first draft,” the task on my calendar said: “Proof of life.”

The rule: I had 90 minutes to write the story straight through in ugly, skeletal form, with no backspacing for anything except typos that made the sentence unreadable.

If I got stuck, I typed things like:

[something happens here that forces her to confront boss]

and kept going.

The goal wasn’t quality. It was to answer one question: Is there enough here that Future Me can fix it?

Most days, I hit 1,200–1,800 words in that window. It felt like laying down scaffolding, not building the house.

3. 3‑Pass Revision, Each with a Single Job

I’d tried “big revisions” before and always drowned in the amount of work. So I broke editing into three passes, each with exactly one job.

Pass 1: Make It Coherent.

Fill in [brackets], fix any scenes that contradict each other, clarify who wants what in each scene. No line edits allowed.

Pass 2: Make It Feel.

Ask: Where does this feel flat? Add concrete sensory details and specific thoughts. If a sentence made me shrug, I either cut it or made it sharper.

Pass 3: Make It Clean.

Only then did I mess with sentences: cutting filler words, checking dialogue tags, removing accidental repetition.

Each pass took 45–90 minutes. Each had a deadline on my calendar.

I used Google Docs and a simple naming convention:

story1_proof_of_life

story1_revision_pass1

etc.

Nothing fancy. Just boring enough to repeat.

4. Small, Real Feedback

I picked two friends who read a lot of fiction and don’t mind telling me when something’s off. No critique group, no workshop.

I gave them two questions:

Where did you get bored or confused?

What stuck with you after reading?

I learned very quickly that “I liked it” is useless, and “I got confused around page 3” is gold.

What Actually Shifted

The obvious change was output.

In those 60 days, I finished four short stories, not three. Word counts ranged from 2,100 to 4,000. Two were speculative, one was realist, one was a weird hybrid.

But the real shift happened about three weeks in.

I was walking to the grocery store, mentally outlining a possible fifth story, when I realized something that startled me: I trusted myself to finish it.

Not “if I have the discipline.” Not “if I can find the time.” Just a quiet, gut‑level: I know the steps now.

For someone who’d spent years in a drama‑filled relationship with her own projects, that feeling was new. And honestly, a little disorienting.

I stopped introducing myself as “working on a novel” and started saying, “I write short stories.” It felt almost embarrassingly modest at first, like admitting I only run 5Ks instead of marathons.

But my calendar and file system told a different story. There were finished things in there.

The email from the magazine landed at the tail end of that 60‑day experiment. Another story got shortlisted in a small contest. A third got a personalized rejection that, for once, didn’t crush me because I had other pieces in the pipeline.

The biggest payoff wasn’t the $150. It was the absence of that old, heavy guilt.

The System, in Plain Terms

If I boil down what started working, it wasn’t mystical or dramatic. It was a system with three parts:

Constraints that limit choices before I start

A fast, ugly first pass to get the story “alive”

A sequence of small, single‑purpose revisions with deadlines

The details matter less than the shape:

Constraints turn “infinite story” into “this specific kind of story.”

Proof of life moves the story from idea‑space into word‑space as fast as possible.

Layered revision reduces overwhelm. I never sit down thinking, “I have to fix everything.” I sit down thinking, “Today my only job is to make sure this makes sense.”

On paper, it’s not complicated. The value is in the repetition.

By the end of six months, I’d run that mini‑system around eight different stories. Each time, I could see where I’d gone off script — usually by “just exploring” on the first draft and ignoring the 90‑minute limit, or by trying to do all three revision jobs at once.

When I followed the system, I finished in 7–10 days. When I didn’t, stories dragged on for a month and made me resent them.

What Changed in Numbers (and What Didn’t)

I’m wary of making creative work sound like a productivity case study, but numbers helped calibrate my expectations.

From the first finished short story to the magazine acceptance:

Stories completed: 7

Stories submitted: 11 (some stories went to multiple places)

Acceptances: 2

Personalized rejections: 4

Form rejections or no response: 5

The money was not life‑changing:

$150 from the first magazine

$50 from an anthology

One contributor copy that arrived slightly bent in the mail

If I divide total dollars by total hours, the hourly rate is still below minimum wage.

But other metrics told a different story:

Average days between writing sessions dropped from 11 to 3.

0 months in a row with no finished work, for the first time in years.

My “finished pieces” folder went from 1 lonely PDF to 9 completed stories in under a year.

What didn’t change is important too:

I did not suddenly get a book deal.

My day job remained necessary.

Some stories I loved still landed with a thud in readers’ inboxes.

The system made me prolific, not famous. There’s a difference.

The Less Glamorous Lessons

There were trade‑offs, and I made a few mistakes.

1. I Over‑Corrected Into “Only Short Stories Matter.”

For a while, I treated novels like a toxic ex. If an idea felt big, I’d force it into 3,000 words, even when it clearly wanted more space.

Result: a couple of cramped, unsatisfying stories that read like drawn‑out synopses.

I had to relearn that form should fit the idea, not my current identity.

2. My Early Stories Were All Skeleton, No Flesh.

The 90‑minute draft constraint worked a little too well at first. I got good at structure and bad at texture.

My friends’ feedback was consistent: “Cool premise, emotionally thin.”

It took conscious effort in Pass 2 to slow down, let characters notice things, and let scenes breathe. Speed is a tool, not the goal.

3. The System Doesn’t Solve Taste vs. Skill.

My taste in short fiction is still ahead of what I can reliably produce. I know when something I wrote is just okay, and the system can’t magically make it brilliant.

What it does is reduce the time between “idea” and “imperfect but finished artifact.” That gap is where learning happens, but it’s still uncomfortable.

4. Submission Is Its Own Job.

I underestimated how much admin goes into actually sending stories out: tracking markets, formatting, cover letters, reading guidelines.

During one three‑month stretch, I wrote plenty but submitted almost nothing. Unsurprisingly, nothing got accepted.

I eventually made “Submission Friday” a recurring task. Still not my favorite part.

A Practical Framework If You Want to Try This

This isn’t a blueprint, but if you’re stuck in “working on my big project” purgatory, here’s a simple version you can adapt.

Step 1: Pick a 45–60 Day Window and a Number.

Decide on a specific, realistic goal like “2 finished stories in 45 days” or “3 in 60.” Put the end date on your calendar.

Step 2: Define 3–4 Constraints Per Story.

Keep them simple:

Word count range

Time span of the story

Max number of POV characters

A requirement like “one irreversible decision”

Write these at the top of each story doc so you can’t forget them.

Step 3: Schedule a “Proof of Life” Session for Each Idea.

Block 60–90 minutes. Set a timer. Your only job is to reach the end in rough form.

Type bracketed notes instead of stopping to think through details.

Step 4: Plan Three Named Revision Sessions.

Literally name them in your calendar:

Story A – Pass 1: Coherence

Story A – Pass 2: Emotion/Texture

Story A – Pass 3: Clean‑up

Having names prevents “I guess I’ll just stare at this and tweak commas” sessions.

Step 5: Choose 1–2 Feedback People and 2 Specific Questions.

Give them a deadline and questions like:

Where did you feel lost or bored?

What, if anything, stuck with you afterward?

Limit yourself to one revision cycle after feedback, or you risk endless tinkering.

Step 6: Decide on a Submission Policy (Even If It’s Modest).

For example: “Every finished story gets sent to at least three venues over six months.”

Track this somewhere dumb and visible: a sticky note on your desk, a simple spreadsheet.

Most of this is project management, not art. The art happens inside those containers.

The Identity Shift I Didn’t Expect

The biggest change wasn’t a financial one, or even a prestige one. It was social.

When people now ask what I write, I say, “Short stories, mostly speculative, and I’m slowly growing a body of work.”

It’s a boring sentence. It’s also true.

I no longer feel the need to impress people with the scale of an unwritten novel. I can point to specific pieces and say, “Here’s one about a woman who hears her neighbor’s thoughts through the plumbing,” or “Here’s one about a town where the streetlights go out when someone lies.”

Tiny, self‑contained worlds that exist, not just in my head, but in other people’s.

The irony is: working in small forms is what finally made the idea of a novel feel less impossible. It’s just a different system: more passes, bigger arcs, longer timelines.

I still have an outline for a long project. The file isn’t named FINAL_really_THIS_time anymore. It’s called novel_experiment_1. That small change is deliberate. It reminds me this is just another structure I can test, not a verdict on whether I’m “really” a writer.

Short stories didn’t rescue my career or solve my finances. They did something more mundane and, for me, more valuable: they turned writing from an identity I performed into a practice I actually do.

If your hard drive is full of almosts — almost‑finished drafts, almost‑outlined epics, almost‑submitted stories — it might be worth shrinking your ambitions for a season, not as a compromise, but as a test.

You might find, as I did, that small stories can hold more of your life than a never‑ending novel ever will.