Content operations covers the arrangements that turn intentions into published, maintained content: how requests arrive and become briefs, how work is scheduled, drafted, reviewed and approved, which tools people use and whose time it takes, along with the routines that keep live material accurate. It’s often shortened to ContentOps, by analogy with DevOps. The term earns its keep wherever content is made by many people.
It sits between strategy and the content itself. Strategy decides what should exist and why; operations is how that becomes ordinary practice. Both belong to a content operating model: strategy sets the rules once, and content operations makes the calls against them, week after week. The model also takes in the wider arrangement – who decides, where teams sit, what’s shared – and the ways teams across the organisation collaborate. Workflow, governance and the content lifecycle are parts of content operations rather than alternatives to it.
Why it matters for content
Many content problems that look editorial turn out to be operational. A page goes out with last year’s eligibility rules because the policy change never reached the writer, or reached them as an attachment in someone’s inbox. Requests arrive by email, chat and corridor conversation, so nobody can see the whole queue. A launch depends on one person who knows which forms need updating. When the Government Digital Service examined how GOV.UK content was produced in 2016, it found more than 300,000 items, 73% of them viewed by fewer than ten people a month, and traced much of the problem to how the work was organised: departments publishing in silos, content designers stuck as intermediaries and content treated separately from the services it described.
Operations also decides what an organisation can sustain. Every new format, channel or microsite adds work that continues after launch: reviews, corrections, translations, migrations. When that work is visible, a team can plan for it, retire something or decline the next request with evidence. When it isn’t, the content estate grows faster than the people looking after it, and quality slides without anyone deciding it should. The same goes for the experience of the people doing the work: a CMS that fights its users or an approval route with six stops becomes a quality problem in its own right.
How AI changes the picture
Cheaper drafting moves the constraint. When a first version takes minutes, the scarce resources become good briefs, reliable sources, review capacity and the time to keep everything current. Operations is where an organisation decides how to spend the hours AI frees: more research and testing, more maintenance, or more output for the same number of reviewers, which tends to end badly.
AI also gives content operations new things to run. Approved source collections, instructions and prompts, evaluation examples, tool permissions and model versions all shape what gets published, and each needs an owner, a review routine and a record of changes, like any other content. A charity adapting one approved explainer into a newsletter item, social posts and a briefing for local groups has multiplied the places a correction must reach; operations decides which version counts as the source and what happens to the derivatives when it changes.
The opportunity is in the coordination work itself, which has always eaten a surprising share of content teams’ weeks. Assistants can sort incoming requests, find the pages a policy change affects, draft change summaries for owners and flag missing metadata before publication. Those are configured uses rather than defaults, and each depends on the team having agreed what should happen next: who gets the summary, who decides and by when.
Questions people ask
- When does an organisation need to think about content operations?
Usually before it notices. The signs are familiar: more than a handful of people publishing, content that outlives the people who made it, requests arriving through several channels at once and launches that depend on late nights. None of these calls for a programme of work, but each calls for someone to look at how the work runs.
- Who looks after content operations?
In a large organisation, often a content operations manager or a small team that owns the tools, workflows and standards everyone else works within. In a smaller one it’s usually part of a head of content’s job. Either way, the people doing the work need a say, because they know where it sticks.
- Is ContentOps DevOps for content?
It uses some of the same ideas: repeatable processes, automation where work is predictable, versioned and structured material, and steady improvement rather than occasional rescue projects. The analogy is closest in documentation teams that manage content like code. Editorial judgement and approval don’t map neatly onto a build pipeline, though, so the comparison works better as inspiration than as a blueprint.
- How can you tell whether content operations are working?
Output alone says little. More useful signs are the time from request to publication, the share of live content with a named owner and a review date, how often published content needs correcting and how much of the team’s week goes on chasing and coordinating rather than on the content.
Learn more
- Content Operations from Start to Scale – an open-access collection edited by Carlos Evia (Virginia Tech Publishing), with practitioners including Sarah O’Keefe and Rahel Anne Bailie explaining ContentOps and how it grows across an organisation.
- GOV.UK’s content operating model: what’s next after discovery – Trisha Doyle’s 2016 account of what GDS found when it examined how government departments produced their content for the site, and why it proposed redesigning the operating model around publishers’ needs.
- Content Maturity framework – the Contentious model in which operations is one of five areas, assessed through collaboration, workflow, maintenance, skills and training.