Campaign Operations
HOW IT RUNS
The Framework Reference explains why. This explains how — the roles, the cadence, the measurements, and the rules that make it stick.
Internal Reference · April 2026 · RCA Records
In every situation, when any team at any point in a campaign is asked to do something, they understand why — and how their work fits into the larger process. That's what Campaign Ops is here to build.
Three roles touch every campaign. Each has a defined lane.
Campaign Ops
The process coordinator
Owns the system, not the strategy. Maintains gates, tracks prerequisites, routes information, captures meeting outputs, surfaces blockers. Present from start to finish as the impartial observer. Runs the retrospective.
Campaign Lead
The project owner
Owns the artist strategy and campaign plan. Decides creative direction, allocates budget, manages the artist relationship. Responsible for the outcome — Campaign Ops is responsible for the process.
Department Leads
The execution teams
Own their deliverables within their lane. Campaign Ops doesn't tell them how — the system tells them when it's due and who's waiting on it.
Routines build habits. Habits build norms. Norms build culture. This cadence repeats until it's invisible.
Mon AM
Weekly status check
All active releases reviewed against their current gate. What's blocked? What's approaching? What changed? Generates the week's priority list.
STANDARDIZATION
Mon
Production Meeting
Delivery, physical product, scheduling. Decisions and blocked items captured. Recap same day.
ROUTING
Tue
SMT
Leadership priorities. Campaign Ops listens for decisions that affect timelines — date changes, priority shifts, budget approvals.
VISIBILITY
Wed
Active Projects (3×/month)
Primary operating meeting. Brief goes out before with gate status per artist. Recorded + transcribed. Same-day recap: decisions, actions, blocked items, cross-dept routing.
ROUTING STANDARDIZATION
Thu
Exec scheduling deadline
All Friday scheduling items submitted. Campaign Ops confirms gate prerequisites are met before requests proceed.
STANDARDIZATION
Fri AM
Exec Scheduling
Release dates, date changes, conflicts. Campaign Ops surfaces gate failures — requests that haven't met prerequisites.
STANDARDIZATION
Fri PM
Week close + voice note
What happened. What's carrying forward. What patterns are emerging. Not distributed — builds institutional memory.
VISIBILITY
Post-release
Retrospective
Non-negotiable. After every campaign cycle: what worked, what broke, what to change. Data-driven. No blame. Campaign Ops facilitates as the impartial observer. Results feed back — gate criteria updated, lead times adjusted, baselines refined.
RETROSPECTIVE
The frequency is the point. People can't forget a process that touches them Monday, Wednesday, and Friday. They can forget a quarterly initiative announced in a deck.
Campaign Ops builds the system. Leadership enforces it. If leadership doesn't visibly reference the gates, hold departments to the cadence, and ask "did we hit the prerequisites" — people will route around it within weeks.
The system says no
Gates block requests when prerequisites aren't met. Campaign Ops doesn't deny anyone — the checklist does. Accountability lives in the system, not in a person.
Leadership references it
When leadership asks "where are we on gates?" every time — not once — the system becomes real. If leadership bypasses it, everyone else will.
Equal accountability
Every department's status is visible. Every missed deadline is on the record — not as punishment, but because if nobody tracks it, nobody fixes it. Same standard for everyone, including Campaign Ops.
Build in the open
Processes, dashboards, meeting outputs — visible to department heads, not built in private. Success is measured by adoption, not by what you built.
04
How We Know It's Working
You can't improve what you don't measure. You can't measure without a baseline. Some metrics are available now. Most need 2–3 cycles.
North Star
Company-wide
Market share. Publicly available, measurable weekly, can't be gamed. Not Campaign Ops' number alone — it's the label's. But it's the scoreboard.
Leading
What we control
Gate completion rates. On-time prerequisite delivery. Recap turnaround. Routing accuracy. Campaign Ops' direct metrics — measurable now.
Lagging
What improves over time
Fewer fire drills. Shorter A&R-to-street-date timelines. Less rework. Cross-dept coordination through system, not chasing. Needs 3 cycles.
Baseline metrics to establish (next 3 campaign cycles):
Metric
How measured
Baseline status
Target
Dept lead times
Days from gate trigger to prerequisite completion, per dept
No data. Establishing.
Variance under 2 std deviations
Gate pass rate
% of releases that clear each gate on first attempt
No data. Gates not yet live.
Improving quarter over quarter
Recap turnaround
Hours from meeting end to distributed recap
Same day (current)
Same day (maintain)
Unknown field rate
% of Release Runway fields marked Unknown at gate check
~100% for SAA/SAMP/Agreements
Under 20% at Gate 3
Routing adoption
% of cross-dept items that reach target dept through system vs. chasing
No baseline. All manual.
50%+ through system by Q3
Market share
Weekly public data
Current baseline available
Trend direction (up)
The variance problem: If lead times range from 2 weeks to 3 months, the gates aren't actionable. Three cycles will tell us. If variance is too wide, we adjust — shorter gates for predictable departments, wider for variable ones.
05
How People Start Using It
Build in private, launch all at once — that's how systems die. Make it useful before it's mandatory — that's how they stick.
Phase 1 — Be useful now
Same-day recaps. Pre-meeting briefs. Gate status before the room asks. Solve a problem people already have. They adopt because it helps, not because they're told to.
Phase 2 — Give them the podium
Highlight other departments' work. Let them demo their wins. Adoption happens through ownership, not monitoring. The value of the podium is giving it away.
Phase 3 — Make it the default
When enough people use it voluntarily, it becomes the path of least resistance. You don't announce the mandate — the system becomes the mandate.
Phase 4 — Retrospective proves value
First full cycle through the system, the retro shows the data. The pilot proves itself. The conversation shifts from "should we do this" to "how do we scale this."
Quick wins and architecture are not mutually exclusive. Every recap uses the same format. Every gate check feeds the baseline. They see the win. You see the infrastructure.
06
What Sticking Looks Like
Not because someone said "good job." Because the behavior changed.
Before
Campaign Lead chases 10 departments for updates. Decisions disappear by the next day. Nobody knows what gate a release is at. Fire drills are the norm.
After
Campaign Lead updates once, system routes to every department. Decisions captured same day. Gate status visible without asking. Fire drills are the exception.
The test: Can a new Campaign Lead — someone who's never worked here — look at this system and know what to do, when, and who's responsible? If yes, it works. If no, it's still dependent on memory.
The bottom line
None of it works without frequency. None of it works without leadership adoption. None of it works without measurement.
Build the routine. Measure the baseline. Prove the improvement.
Campaign Ops