Seven conversations, one full day. The through-line: nobody can see what happens when in a release, so everyone waits until the day-before to ask. That's the map.
The Big Rocks
The four that actually move Campaign Ops. The map is the one to own ruthlessly.
Quick To-Dos
Owner / timing noted.
Meetings to Set
Flags — where today pulled you off compass
You're becoming the scheduling catch-all.
You committed to do Red Clay Strays yourself, Scott's circling, Carlos thinks "ops does scheduling now," Allie flagged it's premature. Fixing the template is your lane. Filling out everyone's requests is the grinder, not the conditions-builder. Decide the boundary with T out loud before July, or it gets decided for you.
Bespoke favors dressed as tooling.
T's email-drag grid, Nikki's mockup, Alexis's stuff — all good, but build one reusable system, not three one-offs per person.
The consumer RCA newsletter / Salesforce is marketing's to fix.
Surface it to Tarek; don't adopt it.
Christian / "keep a list of his mistakes."
Enablement reminders = fine. Documenting every team's knowledge gaps tips into surveillance — the exact who's-responsible map you're trying not to be. His performance is Allie/Tarek's to manage.
Steve Lacy creative reconciliation — already declined. Good. Leave it declined.
Soft one: most of today was emotional-support 1:1s for people who don't report to you.
Shani, Allie, Alexis. Real value — but unrewarded labor and a real time sink. Be deliberate about the dose.
If you only own three this week
The map — the through-line of the whole day
The scheduling boundary— not the scheduling work
The trigger framework for Alexis — find it, send it
Parsed from 6/4/26 conversation log · private to meg.mugzyboez.co · checkmarks save to this browser only