Three decisions run my entire content output. Not a tool. Not a calendar. Three small choices made on three different days. The engine has been running for fourteen months. Most weeks it produces an article on Thursday with no further negotiation.
The decisions are these: on Sunday, which captured idea moves into the draft block this week. On Tuesday, whether the draft block produced something shippable or needs another round. On Friday, what stops earning its place in the next 90 days. Three decisions, fifteen minutes total, repeated weekly. Everything else in the writing process is downstream.
This is the series closing article. It pulls together the cadence question, the three-stage building blocks, the skip-or-ship situations, and the strategy-vs-article distinction into a single operating frame. The frame is small. The constraint is what does the work.
The three decisions
Sunday – Which captured idea moves to the draft block this week.
The capture file from the previous week usually contains 10 to 20 fragments – lines I overheard, observations from client work, half-formed essays in three sentences. On Sunday morning I pick one. Not the best one. The one that’s most ready to become a draft this week. Sometimes that’s an idea I’ve been carrying for a month and have finally found the angle for. Sometimes it’s something I captured on Friday that’s still hot. The decision is to commit to one, knowing the others stay in the capture file for next week.
The decision takes five minutes. The cost of getting it wrong is small: I run a draft block that doesn’t quite produce a publishable piece, and I substitute from the queue. The cost of not deciding is real: a Tuesday morning that begins with “what should I write about” eats half the draft block.
Tuesday – Whether the draft block produced something shippable or needs another round.
Tuesday at 10 AM, after the 90-minute draft block, I read what I wrote. The question isn’t “is this perfect.” The question is “would I ship this on Thursday if I had to.” If yes, the piece goes into the ship-ready queue. If no, the piece either gets one more round on Wednesday or rotates back to capture for another week and I substitute from the queue.
The decision takes five minutes. It’s the most subtle of the three because the temptation is to keep editing the piece into something polished. Editing belongs at the ship stage. The Tuesday decision is binary: shippable, or not.
Friday – What stops earning its place in the next 90 days.
Friday afternoon, after the article ships, I spend five minutes looking at the queue and the recent archive. Two questions. Is there a draft in the queue I’ve been carrying for more than three weeks that hasn’t gotten clearer? Is there a published article from the last quarter that’s pulling the archive average down? The drafts that fail the queue test get pulled. The articles that fail the archive test get noted for the next quarterly strategy review.
The Friday decision is the strategy-edit equivalent at a weekly cadence. It’s small enough to fit in five minutes. It compounds because each pull or note moves the archive one step toward the position you actually want it to occupy.
Three decisions. Three different days. Fifteen minutes a week in total. That’s the content engine.
Why three (and why not other numbers)
Two decisions isn’t enough. Without the Friday decision, the queue and archive drift. The capture file fills with ideas that have already gone cold. The archive accumulates pieces that no longer represent the position. After a year the cadence still runs but the output stops mattering.
Four decisions is too many. Every extra decision means an extra slot to remember, an extra cognitive load to carry, an extra opportunity for the system to skip a week. The fourth decision is usually one of: “should I rewrite this older piece,” “should I promote this on a third platform,” “should I open a new editorial direction.” None of these is bad. All of them belong on quarterly review cycles, not weekly ones.
Three is the smallest number that covers the three distinct cadences the system actually needs: pulling forward from capture (Sunday), gating quality at the ship boundary (Tuesday), pruning at the strategy edge (Friday). The number isn’t aesthetic. It’s structural.
Brian Eno’s Oblique Strategies – the deck of cards he designed with Peter Schmidt in 1975 to introduce productive constraints into creative work – is the cleanest analogue I’ve found to the principle. Constraint isn’t the opposite of creativity. It’s the surface against which creativity becomes visible. The three weekly decisions function the same way: not as limits on the writing, but as the small set of decisions that protect the writing from drowning in the larger set of decisions a content practice could ask of you.
What the constraint actually does
The constraint doesn’t tell me what to write. It tells me when to decide.
The Sunday decision contains the topic question. By 10 AM Monday I know which idea is the week’s piece. I no longer think about it. The remaining six days are execution.
The Tuesday decision contains the quality question. By Tuesday at 11 AM I know whether this week ships from the new draft or from the queue. I no longer think about it. Wednesday and Thursday are mechanical.
The Friday decision contains the strategy question. By Friday at 4 PM I’ve noted what needs to drop. I no longer think about it. Saturday and Sunday are recovery time.
Three decision points. Twenty-one decision-free hours between each. The week feels lighter than it sounds because most of it isn’t negotiation. The decisions were made on the days they belong to.
This is also why the system survives a bad week. A bad week doesn’t add new decisions. The Sunday decision still happens. The Tuesday decision still happens. The Friday decision still happens. The only thing a bad week changes is the substance of the decisions, not their existence. The Sunday idea on a bad week is smaller. The Tuesday decision more often says “substitute from the queue.” The Friday decision more often pulls drafts that aren’t ready. The engine runs through the bad week because the decision points are intact.
How the content engine survives the rare weeks it shouldn’t run
There are two situations where the engine genuinely shouldn’t run, and the constraint accommodates both without breaking.
Strategic skips – the times when a piece isn’t ready and shouldn’t be forced – live inside the Tuesday decision. The Tuesday decision says “shippable or not.” A “not” that can’t be substituted from the queue is the skip case. The decision didn’t disappear. The answer was simply that this week doesn’t ship a new piece. The engine still ran. The output just changed shape.
Depletion skips – the rare quarterly rest weeks – are honoured by the Friday decision from the previous week. The Friday decision before a depletion skip looks at the load and explicitly pulls drafts from the queue. Sunday’s decision the following week is “no draft block this week.” The engine still ran. The decisions still happened. They named the absence rather than producing an article.
This is the principle most solo content systems miss: the decisions don’t stop because the publishing stopped. The decisions are the structure that survives the absence. When the decisions stop happening, the system is no longer paused. It’s dismantled.
When the three decisions are wrong
The engine is wrong in two ways, both of which the quarterly strategy review catches.
The first: the Sunday decision keeps picking ideas that don’t end up making it through the Tuesday filter. The capture file is mismatched to the strategy. The fix isn’t to discipline the Sunday decision more. It’s to edit the capture filter so different fragments get captured to begin with.
The second: the Friday decision keeps pulling the same kinds of drafts. Some topic or angle is consistently showing up in the queue and consistently failing to graduate. That’s a strategy signal, not a queue signal. The strategy review surfaces it. The fix is at the layer above the engine, not inside it.
The decisions themselves don’t change much. What changes is what they’re choosing from. The content engine stays small. The inputs to the engine evolve with the position the archive is building.
The rest of the Content Systems archive lives at the Content Systems category.
FAQ
Why decisions and not tasks?
A task is what you do. A decision is what you commit to before doing. A solo content system that runs on tasks needs constant re-planning because every change of conditions forces a re-task. A system that runs on decisions absorbs the conditions: the same three decisions produce different outputs in different weeks, but the structure is constant.
How do I know if my three are the right three?
After 90 days of running them, look at the output. If the cadence is holding and the archive is moving in the direction you want, the three are right. If the cadence is holding but the archive feels arbitrary, the Friday decision is probably misnamed or in the wrong slot. If the cadence isn’t holding, the Sunday or Tuesday decision is the one to revisit. The structure of three is robust; the choice of which three needs occasional tuning.
What if I use a calendar app or a project tool?
Tools are downstream of decisions. The engine I’ve described works the same whether the capture file is in Notes, Drafts, Obsidian, a physical notebook, or a text file on the desktop. The tool stores the inputs; the engine processes them. If you spend more than ten minutes a week thinking about your tool, the tool is the wrong layer.
Does this scale beyond solo publishing?
The decision structure does. The cadence might shift. A two-person operation might run the same three decisions with one person owning each, or run them daily instead of weekly with smaller units. The principle – small set of explicit decisions at fixed cadences, large field of execution downstream – applies. It’s the principle, not the specific number, that makes it solo-scalable.
What’s the cost of not having explicit decisions?
The cost is decisions happening anyway, just slower and worse. Without an explicit Sunday decision, you make the same decision on Tuesday morning, tired and rushed. Without an explicit Friday decision, the queue and archive accumulate without pruning until a panic-edit becomes necessary. The decisions don’t go away. They just get made in worse conditions, by a worse version of you.
The placement is the system
Three stones, set down once on a Sunday morning. Set in different places, at different cadences. The week happens between them, and most of the week is execution.
The engine isn’t a tool. It isn’t a calendar. It isn’t a discipline. It’s three decisions made on three different days, and a refusal to make more than that.
Fourteen months in, the article still ships on Thursday with no further negotiation. The placement is the system. The system is what survives the year.
The Solo Content System. A printable framework for the three-decision engine: which idea, shippable or not, what drops. Same logic as this article, sized for a single Sunday morning. Download the guide →
