Rules
Part of A 90-day plan to set up marketing operations in the right order
How to manage marketing operations week to week
How to manage marketing operations week to week: a review rhythm, a weekly agenda, a capacity check by skill, an emergency path and what to retire.
What to take away
- Match each review to its rhythmtriage daily, flow and risk weekly, portfolio monthly or quarterly.
- Run the weekly review on four questionsdemand, capacity, delivery and learning.
- Subtract recurring operations, leave and incidents before promising initiative work.
- Give emergency work a documented path, and review afterward whether the urgency was valid.
- Retire reports, tools, fields, templates and services that nobody uses.
How to manage marketing operations day to day comes down to a rhythm the team keeps. A team that reviews everything at once reviews nothing well, so each question gets its own cadence and its own owner.
Set the review rhythm
Match each review to the speed at which its subject changes. Triage can be daily, flow and risk weekly, portfolio monthly or quarterly, and controls on a risk-based schedule tied to change and evidence.
| Cadence | What it reviews | Output |
|---|---|---|
| Daily | New requests: complete, fit, urgent | Accept, return or defer |
| Weekly | Flow and risk across the open work | Escalations and resequencing |
| Monthly or quarterly | The portfolio of services | Services to add, change or retire |
| Risk-based | Controls on platforms and data | Change, test and evidence |
The rhythm only works if requesters know what each service is. Each service needs inputs, owner, lead time, output, acceptance, escalation, and a self-service route.
Service Definition Checklist
- Eligible work
- Inputs
- Owner
- Lead time
- Output
- Acceptance
- Escalation
Run the weekly review on four questions
The weekly review is short because it asks the same four questions every time. Bring the evidence, decide, and leave with a named owner for each action.
| Area | Review question | Evidence to bring | Required action |
|---|---|---|---|
| Demand | What entered and why? | Intake log with sponsors | Accept, return, defer, or reject |
| Capacity | Which skill is constrained? | Hours by role | Limit or resequence work |
| Delivery | What is blocked or at risk? | Campaign states and blockers | Escalate with evidence |
| Learning | What failed or repeated? | Defects, rework, incidents | Assign and verify a change |
Over time, track demand, queue, cycle, on-time delivery, rework, defects, incidents, budget, tool use, and stakeholder effort. Compare them with recurring time and benchmarks instead of with last week's mood.
Check capacity by skill
Estimate recurring time first: operations, maintenance, governance, meetings, and leave. Add incidents before assigning initiative work. Capacity is counted by skill, because a spare designer does not clear a data bottleneck.
For instance, 30 available hours divided by 3 hours per campaign build gives 10 builds. Apply the same math to each role, such as copywriter, designer and automation specialist, then subtract recurring operations, leave, and incidents.
Limit work in progress, and map bottlenecks in creative, data, legal, and platform work, then localization and review. A smaller queue that finishes beats a portfolio where every campaign remains almost ready. Longer-range planning belongs to resource management.
Handle emergency work without breaking the queue
Emergency work will arrive, so give it a documented path. The path names who has authority, the minimum evidence, a record of displaced work, monitoring, and a later review of whether the urgency was valid.
Record every override and the work it displaced. Bring both to the weekly review under demand, so the team sees what the exception cost and who accepted the trade.
Keep campaign states and platforms visible
Ask each week which campaigns sit in which state and what evidence moved them. Define states, entry and exit evidence, owners, allowed transitions, briefs, workback plans, approval scope, QA, launch monitoring, and retrospective. Workflow management covers the approval side.
For each platform, keep a business owner and a technical owner, and review permissions and data when something changes. Test material changes with representative records and recovery steps before they reach live audiences.
Retire what nobody uses
Run retrospectives on constraints, assign improvements, and verify completion. Then retire unused reports, tools, fields, templates, and services, because every item kept alive costs review time.
Pilot a change and expand only after operators and internal customers use it consistently. Start with one high-volume process and one constraint. The operations checklist is the companion for a full review of purpose, ownership and intake.
Borrow priority and control vocabulary
Adapt the priority-setting guidance to marketing while preserving local commercial, legal, customer, and operational obligations. It helps the weekly demand question.
Use the service-management control model as a vocabulary for governed marketing systems, not as a claim that the public-network procedure fits every private platform.
Before you act
- Fix the daily, weekly and monthly or quarterly review slots.
- Put the four weekly questions on a standing agenda.
- Count capacity by skill, after recurring work, leave and incidents.
- Write the emergency path, with authority and a displaced-work record.
- Review campaign states and platform owners each week.
- Choose one unused report, tool or template to retire.
Common questions
How often should marketing operations review work?
Triage can be daily, flow and risk weekly, portfolio monthly or quarterly, and controls on a risk-based schedule tied to change and evidence.
How should emergency work enter?
Use a documented emergency path with authority, minimum evidence, displaced-work record, monitoring, and a later review of whether the urgency was valid.
What should be standardized first?
Start with the highest-volume or highest-consequence workflow where unclear inputs and states create repeated delay, defects, or customer risk.
