Three long-form projects do not cost three times one project. They cost three times the writing plus the price of every switch between them, and the switching is where the time actually goes. The remedy is not a better calendar. It is fewer pieces in composition at the same time, and better notes at the seams.
- List every commitment, including the ones you have not started.
- Keep one portfolio page with a stage, deadline, and next action per row.
- Allow one project in active composition and one in light status.
- Send composition to your longest block and checking work to the fragments.
- Park or drop what you cannot support, and tell whoever is waiting.
Count what you are actually carrying
Start by listing everything with a deadline, a promise, or somebody waiting. Include the piece you agreed to in a hallway and the one you have not started. Most writers find two or three more projects than they were tracking, and the unlisted ones generate the most background worry.
Then mark which of them are in composition. Reading, interviewing, and thinking run in parallel without much cost. Producing sentences does not. The load you feel is rarely the number of projects; it is the number of arguments you are trying to hold in your head at once.
Put the whole portfolio on one page
One page, one row per project. Reviewing that page on a fixed day is what the weekly review is for. Outcome, stage, deadline, who is waiting, and a single next action. Nothing else. The page exists so that deciding what to work on takes seconds rather than an anxious tour through five folders and two inboxes.
A project with no next action is not a project yet; it is an intention, and it should be labelled as one. A project with nine next actions has not been prioritized. Both conditions are obvious on a single page and nearly invisible when every project lives in its own tool.
Two half-finished manuscripts are worth less than one finished chapter.
Limit drafting, not thinking
Hold one piece in active drafting. Give a second one light status at most, meaning revision, research, or a pass through the notes, and queue everything else behind a clear resume note. This feels restrictive until the first week you finish something instead of advancing four things slightly.
The limit works because composition consumes the scarce resource. Holding an argument, a reader, and a voice in working memory is expensive, and none of it survives an afternoon spent inside a different argument. Queued does not mean stalled, though: a queued project still collects notes and questions.
Match the work to the hours you have
Composition needs a long protected block and a reasonably clear head. Source checking, transcript review, outlining, and captioning all survive fragmented time and interruption far better than drafting does, which makes them the right work for the gaps between other obligations.
So assign kinds of session rather than projects to days. A ninety-minute morning goes to the primary draft. Thirty minutes between meetings goes to verifying claims on something else. Several projects keep moving without ever running two arguments through the same block.
Write the resume note before you stand up
The most valuable five minutes in a multi-project week arrive at the end of a session, not the beginning. Write three lines: what changed, what is unresolved, and the exact next move, whether that is a sentence to write, a source to check, or a section to cut.
Be literal about the next move. Continue section four will cost you twenty minutes of rereading. Section four needs the paragraph on why the 2019 figures are not comparable, numbers under bond-restructure, costs you nothing. Store it beside the draft; a note you must hunt for is a note you will not read.
Park projects instead of abandoning them
Some projects should stop for a month, and stopping one properly takes about ten minutes. Update the home note, write a longer resume note than usual, and set a date on which you will reconsider it rather than leaving the return open.
Then go and tell whoever is waiting on it. An unannounced pause becomes a broken commitment inside someone else's head, and the guilt that follows keeps the project consuming your attention long after it stopped consuming any actual working time.
Decide what drops, on purpose
Sometimes the honest answer is that there is more work than there are weeks. Efficiency will not fix that. Make the conflict visible instead: list the deadlines side by side, show what would have to move, and ask which piece matters most.
Dropping something deliberately is a decision. Dropping it by neglect produces the same outcome with worse timing and no chance to renegotiate. Writers who handle many projects well are not faster than everyone else. They are clearer about what they are not doing.
A portfolio page rebuilt in ten minutes
Six projects, all labelled in progress: climate feature, onboarding guide, quarterly report, book chapter three, newsletter backlog, conference talk. No dates, no next actions, no way to choose.
ACTIVE — Climate feature, 4,500 words. Draft, three of six sections. Due 18 May, editor waiting. Next: write the insurance withdrawal section from the interview notes. LIGHT — Quarterly report. Second revision pass. Due 6 May. Next: check the three growth figures against the finance file. QUEUED — Book chapter three. Resume note written 2 May. Reconsider 20 May. QUEUED — Onboarding guide. Waiting on product sign-off, not on me. PARKED — Conference talk. Paused until the feature ships; organiser told 2 May. DROPPED — Newsletter backlog. Handed back on 2 May.
The same six projects. What changed is that five of them stopped asking for attention, and the one that matters carries a next action you could begin immediately.
Common mistakes
| The mistake | Why it costs you, and what to do instead |
|---|---|
| Confusing a list with a plan | A list of projects tells you what exists. It does not tell you what to do this morning. Give every row a stage, a deadline, and one next action, or the list becomes a source of pressure rather than a source of direction. |
| Drafting two pieces in one day | It looks efficient on a calendar and rarely is. Each switch costs the rebuilt argument, the reader you had in mind, and the sentence rhythm you had found. Keep composition to one project per day and spend the fragments on checking work. |
| Leaving projects open with nobody owning the pause | A project that quietly stops still occupies attention. Nothing was decided, so it can be neither closed nor resumed cleanly. Park it explicitly, write the resume note, set a review date, and tell anyone who is waiting on you. |
| Treating overload as a personal failing | When every deadline is urgent, the instinct is to work harder and stay quiet. Capacity problems are structural, not moral. Show the conflict early, propose a sequence, and let the person who owns the schedule choose what slips. |
Your checklist
- List every project you owe, including work you have not begun.
- Mark exactly one project as this week's active draft.
- Give each row a stage, a deadline, and one concrete next action.
- Reserve your longest block for composition and the gaps for checking.
- Finish every session with a three-line resume note in the project itself.
- Park or drop what you cannot support, and say so to whoever is waiting.
Key terms
- Portfolio page
- One view listing every live writing project with its outcome, stage, deadline, waiting party, and next action, used to decide what deserves attention today.
- Work-in-progress limit
- A cap on how many pieces may be in active composition at the same time, usually one, with the rest held in research, revision, or a queue behind it.
- Resume note
- Three lines written at the end of a session recording what changed, what is unresolved, and the exact next move, stored beside the draft it describes.
Setting a project up properly?
Frequently asked questions
How many projects can one writer carry?
+
How many projects you can carry depends far more on size than on count. A workable shape is one piece in composition, one in revision or research, and three or four queued. If two pieces both demand fresh prose in the same week, one of them will end up late or thin.
What if my editor expects progress on everything?
+
Show the portfolio page. It moves the conversation from whether you are working hard to which of these should come first. Most editors sequence willingly once they can see the whole load in a single view rather than one deadline at a time.
Does the one-draft limit apply to short pieces?
+
Not strictly. Short familiar work, such as a newsletter or a summary you have written twenty versions of, does not consume the same attention. Reserve the limit for the pieces where you are still working out what you actually think about the subject.
How detailed should a resume note be?
+
Three lines, written for someone with no memory of the session. If you can read it and begin typing within a minute, it is detailed enough. If it sends you into three files just to orient yourself, add the specifics you left out.
Can Strut AI help me switch between projects?
+
Strut AI can summarize where a queued project stood and which questions were open, which shortens the reload considerably. Ask the assistant for a short brief drawn from the project notes before a session, then check that summary against the draft before acting on it.
Should I batch similar projects together?
+
Batching helps with shallow work such as fact checks, link repairs, or captions across several pieces. It does not help with composition, where the similarity of two projects makes it easier to import the wrong argument into the wrong draft without noticing.