SCOPE
Editorial Strategy · AI workflows · Documentation
ROLE
Strategy, system design, implementation
From random content production to a compounding editorial system.
The content operation had volume. It didn't have direction. I built the strategic architecture first, then the AI workflows on top. The system is documented and runs without me.
3
Layer built
strategy → operations → documentation
100%
Documented
transferable without quality loss
5
Tools integrated
Claude, Notion, Slack, Codex, Gmail
0→1
Full build
no inherited system
CONTEXT
Volume without direction
Articles, newsletters, emails, social posts. Plenty was being produced. The issue was that none of it connected to anything.
No defined pillars. No real sense of who to talk to. No map. Each week's content was basically independent of the last.
And content that doesn't compound doesn't grow. Pieces landed or didn't, but nothing was accumulating. No authority building, no deepening relationship with the reader, no flywheel. The whole thing ran on effort instead of structure.
1
Strategic layer
Defined content pillars for each publication. Built real audience profiles. Not demographics, but worldview, frustrations, what these people are actually trying to solve.
Then mapped out the content landscape: what existed, what was missing, what each piece was supposed to do.
2
Operational layer
Once the architecture was there, I built AI-assisted workflows to produce content within it.
Information monitoring, relevance filtering, automated brief generation, iterative drafting, editorial review. The AI works inside the constraints the strategy defined, not around them.
3
Documentary layer
Behavioral guidelines for how AI operates in the system.
What it can do. What it can't. Which calls require a human. How voice and quality hold at volume.
Someone else can pick this up tomorrow and nothing breaks.
Building faster systems for producing directionless content would have made things worse, not better.
THE APPROACH
Strategy first, always
The instinct in most content teams is to reach for better tools—faster drafting, more automation, tighter workflows.
Understandable, but wrong order.
​
If the operation doesn't have direction, automating it just produces more of what wasn't working. So I treated this as a strategy problem before it was an operations problem.
Information monitoring → Relevance filtering → Gap identification → Automated brief → Iterative drafting → Editorial Review → Publication
WHAT IT DOES
AI handles the mechanical. Humans handle the judgment.
On the input side: the system monitors sources, filters for relevance against the pillars, spots content gaps, generates structured briefs. No one's spending time scanning feeds or deciding what's worth writing about.
​
On the output side: drafts produced within established voice and format guidelines. Editorial checkpoints in the workflow, not after. The AI doesn't decide what matters: it drafts within constraints a human already set.
​
Human judgment ends up concentrated where it actually moves the needle: strategic direction, editorial calls, voice, quality.
Content started compounding
Each new piece connects to a larger logic. The archive works as an asset now, not just a backlog of posts.
Production got faster without quality dropping.
AI takes the mechanical work: monitoring, briefing, first drafts. Human time goes to decisions that actually affect the output.
The system is fully documented
Every constraint, every workflow, every guardrail, written down. No single person's institutional memory required to keep it running.
The sequence was the whole thing.
Pillars and audience model first. AI workflows second. That's what made compounding possible.
What this project taught me
AI content infrastructure is only as good as the thinking underneath it. Build on unclear pillars and undefined audiences and you'll get more of what wasn't working, just faster.
​
The compounding problem wasn't a tooling problem. It was a clarity problem. What is the content for? Who exactly is it for? How does each piece connect to the accumulation?
​
The AI layer came last. Thinking came first.