Writing sprints for people with day jobs — what works and what is theater

Anthony Trollope had a day job at the post office for most of his writing life. He wrote before work, from half past five to half past eight, with a watch on the desk, and he expected 250 words from every quarter hour. He finished forty-seven novels this way. I am not telling you this so you will get up at half past five. I am telling you because of the watch.

Trollope did not sit down to "work on the book." He sat down to fill a container. Fifteen minutes, one small demand, then the next fifteen. That is a writing sprint, a hundred and fifty years before anyone called it that, and it is still the single best tool I know for writers whose writing time comes in scraps between a job, a commute, and a family.

But sprints have picked up a lot of theater over the years — apps, leaderboards, elaborate rituals — and the theater hides what the tool actually does. So let me strip it down.

A sprint is a short, closed block of time in which you do nothing but draft. You set a timer, usually somewhere between fifteen and thirty minutes. While it runs, you write forward. You do not fix the previous sentence, look up whether trains had corridors in 1911, check your phone, or reread the chapter. When the timer ends, the sprint ends, whether the scene is done or not.

That is all. The magic, such as it is, comes from three things the container does to your brain.

First, it makes starting cheap. The real cost of writing with a day job is not the writing; it is the starting. After a full workday, "work on the novel" is a demand your tired mind refuses, because it has no edges — it could mean anything and take all evening. "One twenty-minute sprint" has edges. It will be over before the tea is cold. You can talk yourself into it on your worst day, and your worst days are exactly the ones that decide whether the book gets finished.

Second, it evicts the editor. Most drafting time is not lost to distraction. It is lost to revising the sentence you just wrote, which feels like writing but moves nothing forward. A sprint's one rule — forward only, fix nothing — is really a trick for silencing the inner editor without arguing with it. You are not refusing to fix the sentence. You are just not fixing it for twenty minutes. The editor can accept a postponement. It cannot accept exile.

Third, it makes small time count. This is the part that matters most if your job takes your best hours. A novel does not need large blocks of time. It needs frequent contact. Two twenty-minute sprints on a Tuesday, at 250 to 400 words each, are not a consolation prize — across a working week that pace finishes a first draft in under a year, which is faster than most drafts written in occasional heroic weekends. The heroic weekend has a hidden cost: the ten days away that usually follow it, during which the story goes cold and the price of returning goes up.

Now the honest part, because sprints fail for plenty of people, and they fail in predictable ways.

They fail when the sprint starts with a question. If you sit down, start the timer, and only then ask what happens next, you will spend the whole block deciding instead of drafting, and the timer will feel like a bully. A sprint is an execution tool, not a planning tool. It needs one sentence of intention waiting for it — "Marta finds the letter but cannot read it in front of him" — written at the end of the previous session, when you still knew where the story was going. Readers of this blog will recognize that sentence. The next-scene note and the sprint are two halves of the same machine: one decides, the other types.

They fail when the container is too big. Writers new to sprints often set forty-five minutes or an hour, on the theory that more is more. Then they have one bad session where the well runs dry at minute twenty, feel the remaining time as failure, and quietly stop. Start at fifteen or twenty minutes. It should feel slightly too short. Slightly too short is what makes you willing to come back tomorrow, and tomorrow is the whole game.

They fail when the word count becomes a scoreboard. Counting words after a sprint is useful the way a pedometer is useful — as information, not as judgment. Some scenes are fast and some are not; two hundred words of a hard scene can be a better session than six hundred of an easy one. The number to track, if you track anything, is sprints completed this week. That number you control completely.

And they fail when writers treat the rules as morally binding. If the timer ends mid-sentence and the scene is alive in your hands, keep writing. The container exists to serve the book. Nobody is grading your form.

Here is the weekly shape I suggest to writers with full-time jobs, and it is deliberately modest. Find your two most defensible scraps of time on weekdays — before the house wakes, a lunch break with the office door closed, the twenty minutes after the children are down. Put one or two sprints in each, and decide the night before which scene they belong to. On the weekend, take one longer sitting of three or four sprints with short breaks between them, in the spirit of the pomodoro method, which discovered independently what Trollope's watch knew: attention is renewed by endings. That is somewhere between four and ten sprints a week. At the low end it keeps the story warm. At the high end it is a chapter a week, from a person with a job.

One last thing, because someone always asks whether this produces worse prose than slow, deliberate composition. In first drafts, I have not found it to. Sprint prose is looser, and it is sometimes flatter, but it exists, and it carries more forward motion than most carefully composed drafting, because it was written facing forward. The polish it lacks was never going to survive revision anyway. A draft's job is to exist. The sprint is simply the tool that fits that job into the life you actually have — fifteen minutes at a time, with a watch on the desk.

If you want the timer, the next-scene note, and the manuscript in the same window, sprints are built into Psitta Studio — but a kitchen timer and a sticky note will do fine.