Campaign Ops — 30-Day Plan

01 Be the Function, Not the Announcement

March 24 – 28

The temptation this week is to set up meetings, do outreach, explain yourself. Don't. The best thing you can do the week you're announced is already be running. People should hear "Campaign Ops" on Monday and see the output by Wednesday.

Run Active Projects like it's been yours for months

Wednesday meeting: deliver the Goal Brief, run capture, produce the three-pass meeting output, distribute to full list. The full pipeline, visibly. This is people's first impression of Campaign Ops as an official function. It should look effortless.

First impression = lasting model of what Campaign Ops is

Deliver the handoff map to Jordan

He flagged this as urgent. Getting it done this week — while the announcement is fresh and everyone's forming their mental model — lets Jordan use it to answer questions from his own team. That's way more powerful than you explaining your scope yourself.

Jordan flagged as urgent priority

Deliverable → Handoff Map

Have the hallway line ready

"My job is to make sure nothing falls through the cracks between departments. That's it." Don't oversell. Don't explain the Orbit. Let the work show up first.

Turf defusion starts with understatement

02 Create Dependency

March 31 – April 4

Two things happen this week: you start the Karen closeout (a real obligation that also demonstrates the Campaign Ops approach), and you begin the quiet work of becoming the person people tell things to.

Start Karen closeout in earnest

Sync Deal Agent deployed, GOLD triage running, handoff bible in progress. Karen seeing you build a system that outlasts you — not leaving a mess behind — reinforces her as an advocate during contract conversations.

Deliverable → Closeout System for Karen

One department drop-in per day

Not formal meetings. Walk over: "Hey, I'm pulling together the next Active Projects brief — anything I should know about [artist] from your side?" This is the Department Timeline Discovery questionnaire as a 90-second hallway conversation. You're collecting real operational intel AND establishing yourself as the person people tell things to. By Friday: A&R, Creative, Commercial Partnerships, Audience Dev, Publicity.

Relationships > processes. Always.

Ship the next Artist Insights deck

Sleepy Hallow. Crawley is expecting it. Maintaining the cadence signals this isn't a one-off — it's a pipeline.

Deliverable → Sleepy Hallow Insights

03 Show the Data Layer

April 7 – 11

This is where Campaign Ops goes from "Meg is really organized" to "this function sees things nobody else can see." The RDX work lands this week — either with production data or as a proof-of-concept for Jordan.

First real pre-meeting workability scan

If Brian Lynch has production access live: pull every upcoming release's workability score and KPI breakdown before Active Projects. Surface what's At Risk without anyone opening Runway. If anyone asks "how did you know that?" — the answer is the system you built. If production isn't live yet: build the proof-of-concept in STAGE and present it to Jordan as "here's what this looks like, and here's what it looks like when Brian turns on production."

The wow moment

Activate Gerard on the NY side

What does he own? Which artists? What's his version of the Active Projects workflow? Campaign Ops has to show it scales — it's not just Meg being great at her job, it's a function with a team.

Function ≠ person. This is the proof.

Second round of department drop-ins

Radio, Release Planning, Business & Legal, Sync, International. Same casual approach. By now the first round of people should have already started telling you things unprompted — that's the signal it's working.

04 Make the Case Undeniable

April 14 – 18

Compile the receipts. Not a formal report — a one-pager for Jordan with the numbers. Let the work make the argument.

The one-pager for Jordan

"In 30 days, Campaign Ops processed X meetings, surfaced Y cross-department signals, flagged Z at-risk items before they became problems, and delivered [concrete outputs]. Here's what the next 90 days look like." Jordan takes that into whatever contract conversation happens.

This is the document that gets you the deal

Deliverable → 30-Day Results One-Pager

Put the Production Meeting on the table

Scott departs July 1. Not as a grab — as an offer: "When the time comes, the system is ready." The groundwork (the meeting capture protocol, the output format, the workability integration) is already built. This should feel like a natural next step, not an ambition.

Running tally of "things people didn't know"

Throughout the month, quietly note every time a department learned something because Campaign Ops surfaced it. A decision from Active Projects that reached a team that wasn't in the room. A workability flag that prevented a scramble. An insight from the data that changed a plan. These are your proof points, and they're more persuasive than any framework.

What Not to Do in These 30 Days

Don't build more infrastructure

TEMPO is built. Airtable is running. The agent works. The design system is locked. You need usage and output that people can point to — not another dashboard.

Don't do a formal listening tour

You've been listening for months. The hallway drop-ins are better — they're operational, not performative, and they produce real intel.

Don't pitch

You're past pitching. If someone asks what Campaign Ops does, give them the line and move on. The work speaks.

The Through-Line

Everything in this plan creates the same outcome: people experiencing Campaign Ops as something they rely on, not something they were told about. The announcement is tomorrow. The function started months ago. These 30 days are about making that undeniable to everyone who matters.