The assumption a calendar makes
A content calendar assumes you can generate creative output on a fixed schedule, on demand, regardless of your internal state. For a neurotypical brain that assumption mostly holds. For an ADHD brain it's exactly wrong, because ADHD creativity is state-dependent, not schedule-dependent. When the dopamine isn't flowing, output doesn't degrade gracefully, it stops. "Post a thread every Tuesday" asks for something the brain can't produce to order, even though it can produce an extraordinary volume once conditions actually align.
Worse, a missed day isn't a neutral setback the way it is for other creators. It becomes evidence, evidence you're inconsistent, undisciplined, the same story you've been told your whole life. The missed Tuesday becomes a missed Wednesday because the calendar itself gets harder to open. It stops being a tool and becomes a monument to the failure.
The anti-calendar, in two parts
A production system that fills the reservoir, and a release schedule that draws from it. You run them at completely separate times, and they never touch.
The reservoir: production in batches
Instead of one piece a day, produce a month's worth in a single window. The mechanics of that window are their own thing, the 2-Hour Content Sprint covers the step-by-step, but the principle stands even without that exact structure: create only when the energy is there, and draw from the reservoir the rest of the time. Store finished posts, drafted posts needing one pass, a hooks file, rough video outlines. Aim for a two-week buffer minimum. When it drops under a week, the same novelty drive that scatters attention elsewhere will want to refill it, mild urgency plus novelty is a genuinely productive state for this brain.
The release schedule: publishing without creating
This is the only place a schedule enters the system, and it's not a calendar you fill in, it's a cadence you set once. Pick your days and times per platform, put it in a scheduler or a calendar block, and the only decision left each week is which piece from the reservoir goes out. No "what do I write today," no blank page, no decision about format or timing. You're choosing from a menu, not cooking from scratch.
The weekly check: ten minutes
Every Monday, one question: how many days of buffer are left. Fourteen or more, nothing to do, keep publishing. Seven to thirteen, put a sprint on the calendar this week, not urgent yet. Under seven, sprint this week, let the mild urgency fuel it. Zero, skip the schedule and create today, the empty reservoir is the dopamine trigger, use it. There's no shame anywhere in this loop. You're not failing a calendar, you're managing a reservoir, and that frame is what decides whether you open the document or avoid it.
Making the switch
If you're running an empty calendar or no system at all, build the reservoir before you set any release schedule. Week one: use the next window to create twenty or thirty pieces, don't publish any yet, just fill it. Week two: set the cadence and start publishing from what you built. After that, the system maintains itself, refill when the buffer drops, publish on the cadence, nothing else required.
The calendar didn't fail because you're inconsistent. It failed because it was never built for a brain that runs in windows. The reservoir is.