Content operations
The people, process and tooling that move a piece from idea to published and keep it moving without anyone chasing it.
In depth
What it really means
Content operations is the machinery: who decides what gets written, how briefs are produced, who reviews, where drafts live, how things get published, and what happens after. It is the difference between a team that publishes on schedule and a team where every piece is a small emergency.
Most content problems that present as quality or strategy problems are operations problems. A piece that missed its angle usually had no brief. A post that sat unpublished for three weeks was waiting on a review nobody owned. Fixing the writing does not fix either.
Cycle time = days from brief approved to published
Throughput = pieces published per month ÷ full-time equivalent people on content Cycle time is the diagnostic that matters. A healthy B2B SaaS blog runs 10 to 20 days from brief to publish. Past 30 days, something is queuing, and it is almost always review. Measure where the days actually sit rather than guessing, because teams reliably blame writing when the delay is approvals.
Where the time usually goes
| Stage | Healthy | Common reality |
|---|---|---|
| Brief | 1 to 2 days | Skipped, which costs more later |
| Draft | 3 to 5 days | 3 to 5 days |
| Edit | 2 days | 2 days |
| SME or legal review | 3 days | 10 to 20 days, unowned |
| Publish and distribute | 1 day | Publish 1 day, distribution never |
Pros & cons
Pros
- Makes output predictable, which is what lets you plan anything else.
- Removes the quality variance that comes from every piece being handled differently.
- Scales. A documented process absorbs freelancers and new hires without a founder in the loop.
- Surfaces the real bottleneck, which is rarely where people assume.
Cons
- Process overhead can exceed the benefit on a team of two.
- Over-engineered workflows produce compliance rather than good work.
- Tooling gets bought as a substitute for deciding who owns what.
- Nobody wants to own it, so it decays back to chaos without a named owner.
The mistake people make
Buying a tool to fix a decision problem. Teams adopt a content platform hoping it resolves who approves what, and it does not, because that is a management question. Write down the owner of each stage and the maximum days allowed at each, then pick tooling to support it. In that order.
Best practices
- Name a single owner per stage, with a time limit attached to each.
- Measure cycle time and find the actual queue before changing anything.
- Standardize the brief, since it removes most downstream rework. Our brief generator is a starting template.
- Cap review rounds at two, and make round three an escalation rather than an option.
- Put distribution in the workflow as a required stage, not a hope.
- Build the refresh cadence into the same calendar as new publishing.
FAQs
What is content operations?
The people, process and tooling that take a piece from idea to published and keep it maintained afterwards.
What is a healthy cycle time?
10 to 20 days from approved brief to published for most B2B SaaS blogs. Past 30, something is queuing.
Do small teams need content ops?
They need the decisions, not the tooling. Two people still need to agree who approves and by when.
What tool should I use?
Whatever the team already opens daily. Tooling never fixes an ownership problem.
Where do most delays happen?
Subject-matter expert and legal review, almost always, because those stages usually have no owner and no deadline.
Keep reading
Related on LymLyt
Beyond LymLyt
Further reading
Want this working on your site?
We build the content behind the term, ranked in search and cited by AI.
Book a 30-min call →