How to run content operations with a team of two or three people

The marketing director left in February. The replacement hire fell through. Now content operations sits with two people — one of them you — and nobody has cut the publishing calendar to match.

Most content ops advice assumes you have a dedicated editor, at least two writers, someone who handles distribution, and a strategist who maintains the editorial calendar. When the reality is two or three people handling everything from ideation to analytics, that advice becomes a fantasy document.

Content operations small team setups require different systems. Not simplified versions of enterprise workflows — entirely different structures built for the constraints of running lean.

Why enterprise content workflows break at two people

The standard editorial workflow has stages: ideation, briefing, drafting, editing, approval, publishing, distribution. Each stage assumes someone available to hand off to. With a small content team workflow, those handoffs create gaps where work stalls.

A brief sits waiting for someone to pick it up. A draft needs edits but the one person who does editing is in client meetings until Thursday. The approval bottleneck means three articles queue behind someone's inbox while the publication date passes.

Enterprise workflows assume parallelism — multiple pieces moving through different stages simultaneously. Two people can't run parallel processes. They run sequential ones, which means the whole system needs to be rebuilt around that constraint.

The three roles that actually need covering

Strip content operations to its functional minimum and you get three jobs that can't be skipped:

Someone decides what to write. This includes keyword research, understanding what the business needs right now, and maintaining the editorial calendar so content serves actual goals rather than just filling slots.

Someone produces the writing. Drafting, editing, formatting. Whether that's original writing, working with AI writing tools, or managing freelancers — words need to appear in publishable form.

Someone handles the infrastructure. CMS uploads, image sourcing, scheduling, making sure the publishing system actually delivers what was produced.

With ten people, these are departments. With two or three, these are hats the same people rotate through. The workflow needs to account for the context-switching cost of that rotation.

Content workflow structures that work at small scale

Batch by function, not by piece. Instead of taking one article from idea to published — which requires switching between strategist brain, writer brain, and operations brain multiple times — do all the strategic work in one session, all the production in another, all the publishing tasks in a third.

Monday morning: plan the month's topics, pull keyword data, write brief notes for each piece. Tuesday through Thursday: production only. Friday: upload, schedule, queue distribution. This reduces the cognitive load of constant role-switching.

For content ops lean team setups, the editorial calendar isn't a planning document — it's a production schedule. It should show what's being worked on right now, not what you hope to publish eventually. A wishlist disguised as a calendar creates anxiety without creating output.

Where AI writing tools fit without creating more problems

The promise of AI writing tools is volume. The reality for small teams is often more work — reviewing and fixing output takes longer than expected, and the writing sounds like it could be about any company in the industry.

The useful application isn't replacement but acceleration. Use AI for first drafts when you have clear brand inputs. Use it for research synthesis. Use it for generating structural options when you're stuck on how to approach a topic.

That's exactly where BrandDraft AI was built to help — it reads your website URL before generating anything, so the draft already references your actual product names and terminology instead of generic industry language. The difference matters when your editing time is the bottleneck, not your ideation time.

What doesn't work: treating AI output as publishable without significant editing. A content team two people deep can't afford the reputation cost of obviously machine-generated articles. The tool should reduce editing time, not create different editing problems.

The briefing trap that kills velocity

Detailed briefs are insurance against misalignment. When a writer you've never met is producing content, the brief protects both parties. When the same two people produce everything, that insurance becomes overhead.

Content operations startup teams often inherit briefing templates from previous roles at larger companies. A 500-word brief for a 1,200-word article makes sense when the brief-writer and article-writer are different people with different contexts. When it's the same person, or two people who talk daily, the brief should be a note — three sentences on the angle, the primary keyword, and any specific points to hit.

The goal is capturing the thinking, not documenting it for an audience that doesn't exist. You can scale your blog output without briefing every article if your workflow supports it.

What a realistic publishing cadence looks like

Two people, assuming content isn't their only job: 4–6 pieces per month is sustainable. 8–10 is possible during quiet periods but collapses when other priorities surge.

Three people with content as a primary focus: 8–12 pieces monthly, with capacity for occasional sprints.

These numbers assume editing and publishing — not just drafting. A draft that sits in the CMS unpublished for three weeks didn't actually add to your output.

The mistake small teams make is committing to weekly publishing because that's what the content marketing playbook recommends. Then missing weeks, then feeling behind, then batch-publishing three mediocre pieces to catch up. Twice monthly at higher quality beats weekly at lower quality — and creates less operational stress.

The only metric that matters with limited capacity

Throughput: pieces published per month divided by total hours spent on content operations. Not just production hours — include planning, meetings, revisions, publishing tasks.

Track this honestly for a quarter. You'll find where your time actually goes, which is rarely where you think it goes. Most small teams discover they spend more hours in planning and coordination than in actual production. Fixing that ratio is where efficiency gains live.

A content workflow that publishes six articles from forty hours of work outperforms one that publishes eight articles from eighty hours — even though the raw output is lower. When capacity is the constraint, efficiency is the strategy.