Workflow Wednesday · AI Pro Writers Studio

🔥

Workflow Wednesday

The Weekly Author Operating System: How to Run Your Writing Business in Ten Hours a Week

Workflow Wednesday | DragonWorks Publishing

*****Author's Note

For most of us the last part of this article is the most important. Time blocking, schedules, and boxes do not always work. I've owned several businesses in my life. Custom Computer Sales, Onsite Computer Support, Sound Recording Studio, Poster & Tee Shirt Printing and now a pair of SAAS apps as writing tools. In all cases I had the same issue but for me it was a triangle. I could Run the office, Do the Work,or Bring in New Business. I was very good at all of them, but only two at a time.

As you will see below I've added an extra pieces of the puzzle for authors and I'm doing it again. Create, Publish, Market, Admin, and for me with WCP & BW it's Support, and of course my day job until things really take off. And I'm doing it again. I can do all 5 but only 2 at a time really well. I need to fix that.

*****

Most indie authors are running four different jobs at once and treating them like one job.

You're a writer. You're a publisher. You're a marketer. You're an admin department. Every one of those roles has its own rhythm, its own kind of attention, and its own definition of "done." And most of us handle all four the same way: whatever's loudest today wins.

An email from a reader needs a reply, so admin wins. A cover reveal is coming up, so marketing wins. A deadline is close, so writing wins for a few frantic days and then collapses because nothing else got done and now there's a backlog. Nothing is scheduled. Everything is reactive. And the role that actually makes the books, the writing, is the one that loses most often, because it's the only one without a ping, a deadline, or someone waiting on you.

The fix isn't working more hours. It's giving each job its own room instead of letting them fight in the same open floor plan.

The Four Buckets

Every task an author does falls into one of four buckets:

Create. Drafting, revising, outlining, anything that adds new words or new structure to a story that doesn't exist yet.

Publish. Formatting, uploading, proofreading passes, cover coordination, metadata, anything that turns a finished manuscript into a live product.

Market. Social posts, email newsletters, ads, launch planning, anything aimed at getting the book in front of readers.

Admin. Email, bookkeeping, tool maintenance, replying to reviews, the unglamorous plumbing that keeps the business running.

Almost every author already does all four. The problem is doing them in the same undifferentiated block of time, where whichever one has the loudest fire wins the moment. Separating them into scheduled buckets doesn't add hours to your week. It just stops one bucket from silently eating the others.

Why Create Has to Go First

If you build your week by scheduling admin and marketing first and hoping writing fits in the leftover space, writing loses. Every time. It has no external deadline pressure, so it's the easiest thing to bump.

The fix is mechanical, not motivational: block your Create time on the calendar before anything else goes on it. Treat it the way you'd treat a dentist appointment someone else made for you. Everything else gets scheduled around it, not the other way around.

This is the one non-negotiable rule of the whole system. Every other bucket can flex. Create goes first or the system doesn't work.

A Ten-Hour Week, Divided

Ten hours a week is a deliberately modest target. It's meant to be achievable around a day job, kids, or whatever else is eating your real hours, not an aspirational number for someone with a completely open schedule. Scale it up or down to whatever you actually have.

Here's one way to split it:

Create: 5 hours. The largest bucket, always. Two or three sessions, protected and scheduled first.

Publish: 1 hour. Most weeks this sits idle, then spikes hard the week you're actually formatting and uploading a release. Treat it as a reserve, not a weekly constant.

Market: 2.5 hours. Enough for a consistent content rhythm without turning into a second full-time job. This is where batching earns its keep, more on that below.

Admin: 1.5 hours. One sitting, ideally the same time every week, so email and bookkeeping don't leak into the other three buckets throughout the day.

The exact split isn't sacred. What matters is that each bucket has a number attached to it instead of an open-ended "whenever I get to it." A number is a boundary. An open-ended intention is just a hope.

Batch, Don't Drip

Marketing and admin both suffer from the same failure mode: they feel like five-minute tasks, so they get done in five-minute interruptions scattered across the whole week, and each interruption costs you the re-entry time to get back into whatever you were actually doing.

Batching fixes this. Write a week's worth of social posts in one sitting instead of one post a day. Answer the whole email inbox once, not every time a notification pops up. Schedule everything you can with a tool that posts on your behalf, so the actual publishing moment doesn't need your attention at all.

One batched hour of marketing produces more usable output than five scattered fifteen-minute sessions, because you're not paying the re-entry tax five separate times.

What a Week Actually Looks Like

This isn't a schedule to copy exactly. It's a shape to adapt.

Monday, Wednesday, Friday mornings: Create. Same time, same protected block, before anything else has a chance to claim it.

Tuesday afternoon: Market. Batch the week's content in one sitting.

Thursday morning: Admin. Clear the inbox, handle bookkeeping, do the plumbing.

Publish sits in reserve until release week, when it temporarily borrows hours from Market, since a launch week is not a normal week and shouldn't pretend to be one.

When Ten Hours Isn't Real

Some weeks the ten hours doesn't happen. Life eats it. That's not a failure of the system, it's just a week where the system didn't get to run.

The recovery move is small: protect Create first when you come back, even if it's the only bucket that gets time that week. A week where you wrote and nothing else happened is still a week that moved the book forward. A week where you did admin and marketing and no writing is a week where the actual product stood still.

When the System Itself Is the Problem

Everything above assumes a brain that can look at a calendar block and just show up to it. For a lot of writers, especially those with ADHD or other neurodivergent wiring, that assumption is where the whole system quietly breaks down. Fixed time blocks don't fail because of laziness or bad planning. They fail because some brains don't run on clock time, they run on interest and energy, and a block scheduled for Tuesday at 9am means nothing if Tuesday at 9am is not when the brain shows up.

If the ten-hour version above doesn't stick, the buckets themselves are still useful. It's the clock-block delivery mechanism that needs swapping out.

Order instead of hours. Instead of assigning Create a fixed slot, assign it first place. Whenever you sit down with any capacity to work this week, Create gets first refusal on that window. Publish, Market, and Admin fill whatever's left, in whatever order the day allows.

Body doubling. Writing alongside someone else, in person, on a video call, or in a virtual co-working room, lowers the activation energy of starting. The presence of another person doing focused work is often enough to get unstuck, even with zero interaction between you.

Short sprints instead of long blocks. A 15 or 20 minute timer with a hard stop is easier to start than an open-ended hour. Many writers find they keep going once the timer ends, but the timer is what got them past the doorway.

External, visible tracking. A calendar entry that's out of sight is out of mind. A sticky note on the monitor, a whiteboard with the week's four buckets on it, or a kanban board where Create physically moves across columns gives the system a presence in the room instead of a buried notification.

No shame tax on missed days. The recovery rule from earlier, protect Create first when you come back, matters even more here. A missed day that turns into guilt often turns into a missed week. A missed day that gets shrugged off turns into tomorrow.

None of this is a diagnosis or a prescription, just a set of commonly used adjustments. The four buckets are the map. How you actually move through them is allowed to look nothing like a calendar grid.

The four buckets were always there, doing their four different jobs inside your head at the same time. Giving them separate rooms doesn't create more hours. It just stops the loudest one from running the whole week.

What's the next Workflow Wednesday? Two candidates are on deck: the continuity workflow for series authors, and a research workflow that doesn't eat your writing time. Let me know which one to run next.

6 comments

Workflow Wednesday