Content Operating Lead

A lightweight content operations system for product content: one source of truth for every content item, a clear lifecycle from request to retirement, risk-based governance, and Claude-assisted automation for the repetitive parts. Example content is taken from the Admirals public FAQ.

The problem it solves

Content lives in several platforms (website, help center, app, emails, chatbot) and nobody has a full inventory
Reviews and approvals happen in DMs and email, so there is no audit trail
Regulated content (fees, withdrawals, leverage, entity-specific rules) goes stale without anyone noticing
Tagging and metadata are inconsistent, so content is hard to find, reuse and audit

How it works

Intake. Every new piece or change starts as a request in Requests. No request, no work.
Inventory. Every live item has one row in Content Inventory: owner, SME, platform, entity, risk level, review dates, tags.
Production. Each item is produced on its own page using the Content item template (brief, draft, QA, approvals, publishing, change log).
QA and approval. Definition of Done + QA checklist. High-risk content needs a compliance sign-off.
Publish. Scheduled on the publishing calendar, published by a human, verified live.
Maintain. Review dates are set by risk level. Overdue items surface automatically. Each review ends in Keep / Update / Merge / Archive / Remove.

Operating principles

One item, one owner. Content without an owner is not published.
Risk sets the rigour. High risk = SME + compliance review and a 3-month review cycle. Low risk = 12 months.
Every change is logged. What changed, why, who approved, when it went live.
Claude prepares, humans decide. Automation drafts, tags, checks and reminds. People approve and publish.

How this maps to the role

Responsibility in the job description	Where it lives in this system
Coordinate and execute publishing across platforms	Content item page → Publishing section; Inventory → Publishing calendar view
Maintain inventories, metadata, tagging, documentation	Content Inventory database; Standards → Tag taxonomy
QA reviews: accuracy, consistency, accessibility	Standards → QA checklist; Automation 3 (pre-review QA)
Identify, update, archive, remove content	Lifecycle → Review outcomes; Inventory → Review overdue view
Governance, priorities, lifecycle management	Lifecycle, RACI & Governance
Coordinate workflows, reviews, approvals, dependencies	Requests; Content item → Approvals; weekly digest
Content audits and inventory assessments	Automation 4 (ROT audit); Metrics
Discoverability, usability, customer experience	Tag taxonomy; Metrics (search, support contacts)
Feature development: requirements, testing, feedback	Automation 7 (test notes → structured feedback)
Document processes, standards, best practices	Standards & QA; Lifecycle, RACI & Governance