Scaling Great Work

The Long Game Podcast

Grab a coffee and sit back as co-founder of Omniscient Digital Alex Birkett and Relato co-founder and CEO David Baum discuss the Content Ops Challenge, Scaling Great Work, Saving the Internet, and the Risks of SEO-Only Content in the latest episode of The Long Game podcast.

Key takeaways

The episode covers a lot of ground. Here are a few of the ideas worth carrying into your own work:

• Content ops needs better tools to match how teams now work and manage content.
• Current content ops are often scattered and inefficient because there is no comprehensive platform holding the work together.
• A divide exists between content managers and writers, and each side faces its own set of challenges.
• Focusing only on SEO is risky and burns resources that could go toward better work.
• Keeping the human element online matters as AI starts to overshadow human creativity.
• The internet is healthier when there is more room for unexpected discovery and less dependence on algorithms.
• Finding genuinely new content is still hard given the limits of today’s algorithms.

The content ops challenge, in plain terms

Strip away the jargon and the content ops challenge is simple to state: it is the gap between wanting to publish great work every week and having a system that lets you.

Most teams do not fail at content because they lack ideas or talent. They stall because the operation underneath the work is held together with spreadsheets, scattered docs, and a group chat. Content operations is the system of people, processes, and tools that turns a strategy into something that actually ships on a schedule. When that system is thin, every new writer, format, or campaign adds friction instead of output.

That is the theme Alex and I keep circling back to in the episode. The work can be excellent and the operation can still be the thing that breaks. If you want the fuller version, we laid out a practical model in our content operations framework for B2B teams.

Scaling content operations without flattening the work

Here is the trap. The more content you produce, the easier it is to trade uniqueness for efficiency, to go from artisanal to assembly line. Content operations at scale is really a quality problem wearing a volume costume.

The teams that grow without going generic tend to do three things. They protect a point of view instead of chasing every keyword. They give the operation a spine, so a fifth contributor does not mean a fifth way of doing things. And they keep a single source of truth for briefs, drafts, assets, and status, so nobody is guessing where the current version lives. We wrote a whole guide on the last one: creating a single source of truth in content marketing.

For a deeper walk through the workflows that hold quality steady as output climbs, our guide on how to scale your content program without sacrificing quality covers the request-to-repurpose lifecycle in detail.

What a content operations framework actually needs

A content operations framework is not a forty-page document nobody opens. The version that survives contact with a busy team fits on one page and names five things:

• Who owns the editorial calendar.
• Who owns distribution.
• How a brief becomes a draft.
• Where assets and statuses live.
• Which metrics get reviewed, and how often.

For B2B content operations, add the subject matter expert roster and the review cadence, since expert input and longer approval cycles are where B2B work usually gets stuck. Keep the framework short enough that everyone can hold it in their head, and revisit it each quarter as a living document. If you are moving from a loose strategy to a running system, our piece on how to operationalize your content strategy shows how to turn the framework into a repeatable build.

Frequently asked questions about content operations

What does content operations mean?

Content operations is the system of people, processes, and tools a team uses to plan, produce, publish, and measure content on a repeatable schedule. It is the connective tissue between a content strategy and the work that actually ships each week. The content ops challenge is the gap between wanting to produce great work consistently and having a system that lets you.

What does content operations at scale actually mean?

It means holding editorial quality steady while output, contributors, and formats all grow. The hard part is not producing more, it is producing more without the work turning generic. Most teams hit the wall around 4 to 6 contributors or a dozen pieces a month, when informal coordination quietly stops working.

What does a content operations framework include?

A working framework names five things on one page: who owns the calendar, who owns distribution, how briefs become drafts, where assets and statuses live, and which metrics get reviewed and how often. Keep it short, treat it as a living document, and revisit it every quarter.

What are the most common content operations pain points?

Fragmented tools, no single source of truth for status and assets, a blurry line between what managers own and what writers own, and an over-reliance on SEO volume that pushes teams toward safe, forgettable content. Each one gets worse as the team grows.

How is B2B content operations different?

B2B content operations leans harder on subject matter experts, longer review cycles, and content that has to earn trust with a technical or executive audience. More stakeholders touch each piece, so the workflow and the single source of truth matter even more than they do for high-volume consumer content.