Building a content operations system that survives a busy quarter

Why systems beat effort in content

Ask ten teams why their blog is behind schedule and most will say the same thing: not enough time. Look closer and the time is usually there. What is missing is a system that survives the week when three people are on holiday and a product launch eats everyone's afternoon.

A content operations system is not a document management policy. It is the answer to four questions, written down and agreed on: what gets written, who decides, who checks, and when it goes live. If any of those four answers lives only in someone's head, the queue stalls the moment that person gets busy.

A programme that produces six good posts a month with a boring process beats one that produces twelve brilliant posts for two months and then nothing.

The four artefacts that keep a queue moving

Every stage of a working pipeline hands a specific artefact to the next stage. If the artefact does not exist, the handover is a conversation, and conversations do not scale.

1. The topic map

A topic map is the list of pages you intend to own, grouped by intent rather than by keyword volume. It answers "what job does this page do" before anyone writes a word. Without it, you get five posts circling the same query and none of them ranking.

2. The brief

A brief names the audience, the angle, the required sections and the claims you are not allowed to make. Keep it to one screen. A brief nobody fills in is worse than no brief at all, because it creates the illusion of a process.

3. The draft with its checks

The draft travels with a checklist: heading structure, query coverage, internal links, metadata. Run those checks before a human reads the piece. Editors should spend their attention on argument and accuracy, not on counting H2s.

4. The publish record

What went live, when, who approved it and what the page is expected to do. This is the artefact almost everyone skips, and it is the one that makes refreshes possible six months later.

Ownership, not committees

Every page needs one owner. Not a team, not a channel, one name. Owners can delegate the writing, but they carry the deadline and the outcome. When ownership is shared, the default behaviour is waiting: everyone assumes someone else is moving it forward.

Approval works the same way. Two-step approval is reasonable. Four-step approval means nothing ships in a busy quarter, because four people have to be available in the same window. If your approval chain has more links than your publishing cadence has days, you have designed a bottleneck.

Choose a cadence you can defend

Pick the cadence you can hold in your worst month, not your best one. Two posts a week that always land will out-perform a plan for five that produces two in practice and a demoralised team. Cadence is a promise to your process, not an ambition.

A useful test: look at the last three months of published dates. If the gaps are irregular, your stated cadence is fiction. Set the real number, then improve it deliberately once the system holds.

What to automate and what to leave alone

Automate the parts that are repetitive and rule-based: structure, formatting, metadata generation, optimisation checks, scheduling, and the reminder that a page is due for refresh. These are the tasks that consume editorial hours without using editorial skill.

Leave alone the parts that require judgement: the angle, the accuracy of claims, first-hand examples, and the decision about whether a page should exist at all. If you automate those, you get volume that nobody wants to read and search engines have no reason to rank.

• Automate: outlines, metadata sets, internal link suggestions, publishing, refresh detection
• Keep human: the angle, sourcing, examples, final approval
• Review quarterly: which automated steps are still earning their place

A thirty-day plan to get started

You do not need a rebuild. You need four weeks of disciplined narrowing.

Week one: list every page you published in the last quarter, with its owner and its job. Most teams find a surprising number of pages with neither.

Week two: build a topic map for the next quarter. Group by intent, mark overlaps, and cut anything you cannot justify in one sentence.

Week three: write one brief template and use it for every new page. Resist the temptation to make it comprehensive; make it fillable.

Week four: set the cadence, assign owners, and schedule the first month of publishing dates before the drafts exist. Deadlines that arrive with the work are not deadlines.

After thirty days you will not have a perfect system, but you will have a system, which is the part most programmes never reach.