a calendar people follow.
a calendar fails for one reason: it was built around dates instead of around what you can produce.
plan formats, not posts. a small set of repeatable formats, one owner, a two-week buffer and a monthly production day survives a busy month; a thirty-cell grid does not.
almost every business has built a content calendar and almost none are still using the one they built. the pattern is consistent: two weeks of disciplined posting, then a busy period, then a gap, then a quiet decision that the calendar was unrealistic.
it usually was. the failure is structural rather than a discipline problem — a calendar that specifies thirty individual pieces requires thirty separate creative decisions, and nobody has that in reserve during a normal month.
the calendars that last look different on the page. they are shorter, more repetitive, and less impressive to present internally — which is precisely why they keep working after the person who built them has moved on to something else.
— 01plan formats, not posts.
the durable unit is a format rather than an idea: a repeatable shape you can fill without inventing anything. a weekly answer to a customer question, a monthly walkthrough of a finished job, a fortnightly staff feature, a standing before-and-after.
four or five formats fill a month with a fraction of the effort, because the hard decision — what shape is this, how is it shot, how long is it — was made once. all that remains is choosing the subject, which anyone in the business can do.
this is also what makes delegation possible. "film a customer question" is a brief a team member can execute; "post something engaging on tuesday" is not, and the second is what most calendars actually say.
write each format down as a one-page brief: what it is, how long, shot how, what it must include, and one example. that page is what lets somebody else produce it while you are away, and it is the difference between a system and a habit that depends on one person.
build the format library first, then map it onto the month. the calendar becomes an assignment sheet rather than a creative exercise, which is why it survives. it also makes a gap recoverable: a missed week means one format skipped once, not a plan that has fallen apart.
| abandoned by week three | still running in month six | |
|---|---|---|
| the unit of planning | thirty individual post ideas | four or five repeatable formats |
| production | daily, alongside the day job | one batched day per cycle |
| ownership | a shared document | one named publisher |
| approvals | a committee per post | format approved once |
| slack in the system | every slot filled | two weeks banked, two slots open |
| review | none, or a redesign | monthly format cull |
— 02one owner and a real production day.
a calendar with no named owner is a shared document that nobody updates. one person needs to own publication — not the ideas, not the approvals, the act of publishing — and they need the authority to publish without a committee.
and the production has to be batched. a monthly or fortnightly shooting day that produces the whole cycle in one session is the difference between a system and a scramble. daily production competes with the day job and loses every time.
the arithmetic is favourable: one prepared day produces more usable material than fifteen improvised half hours, and the quality is more consistent because the setup and the light are the same. approvals belong at the format level too — approve the shape of a customer-question video once, and every subsequent one can publish without a review cycle that adds three days to a two-minute clip.
— 03keep two weeks in the bank.
the single most useful structural rule is a buffer. finish each production cycle with two weeks of scheduled content ready to publish, and a bad week stops being an outage.
without the buffer, every unexpected event — travel, illness, a launch, a genuinely busy fortnight — creates a visible gap, and gaps are what break the habit — for the audience, who stop expecting you, and for the team, who stop treating the schedule as real. the account goes quiet, restarting feels like effort, and the calendar quietly ends.
leave deliberate space too. two or three open slots a month for whatever is actually happening keeps the feed current, and a fully booked calendar has no room for the thing worth posting today. the timely piece almost always outperforms the planned one, which is an argument for leaving the space rather than for abandoning the plan.
— 04review it monthly and cut.
once a month, look at what performed and what nobody watched, and change the format mix rather than the individual posts. formats that consistently underperform should be removed, not improved — you are choosing where finite production capacity goes. give a new format three cycles before judging it, though — one weak result is noise, and a format that needs a fourth attempt is common rather than a failure.
this is also when to be honest about capacity. a calendar planning twelve pieces a month when the team reliably produces seven is not ambitious, it is a monthly reminder of failure. plan seven properly and add the eighth when seven is comfortable.
and write down the decisions. a calendar with a short record of what was tried and dropped stops the team relitigating the same ideas every quarter — which is the part of strategy work that actually compounds, and why we build the production rhythm before the posting schedule.
read next: a content calendar that works, build a system, not a calendar, a content calendar that holds in the uae.