Implementation worksheet · 6 min read
A Growth-Team Campaign Ownership Matrix
For each campaign stage, name exactly one accountable person, the people responsible for doing the work, who must be consulted before, and who is informed after. Check first the stages that sit between roles: audience sign-off, the consent and suppression check, the kill switch while a send is running, the post-send readout, and switching off journeys nobody watches any more. Put a person against each, never a team alias, and give every accountable person a deputy with the same authority. Where a marketing agent does the work, list it as responsible for the steps its permissions allow; the accountable name stays human.
Scope: a growth team of lifecycle marketers, an analyst, a product manager, an engineer, legal or compliance, support, and marketing agents working within a permission matrix. Starting state: everyone knows roughly who does what, and incidents end with 'I thought you had it'. Boundary: campaign and journey work from brief to retirement, not headcount or reporting lines. Intended outcome: a one-page matrix in which every stage has one accountable name and a reachable deputy.
Put it into practice
1. List stages at the grain decisions are made
Goal and brief, audience definition, consent and suppression check, content, legal and brand review, QA and test send, scheduling and launch, monitoring during the send, post-send readout, retirement. A single 'execution' row hides the kill switch inside it.
2. One accountable name per stage
Accountable means answerable for the outcome, and it is one person. Two accountable names amount to none, because each can assume the other decided. Responsible can be several people, and can include an agent.
3. Give every accountable person a deputy
With the same authority, written down. The kill switch in particular has to be reachable during every send window, including a send that runs overnight in the owner's time zone.
4. Replace team aliases with people
'Marketing ops' in the accountable column means everyone on the alias can assume someone else handled it. Put a name. If the name changes with a rotation, put the rotation and where to see who is on it today.
5. Add the agent explicitly
If a marketing agent drafts copy or proposes segments, list it as responsible for those steps, within the levels its permission matrix grants. Accountability means answering to the business for the outcome and having a deputy when you're away, and that stays with a person.
6. Assign retirement
Journeys outlive the people who built them. Someone is accountable for reviewing live journeys on a schedule and switching off those with no owner, no traffic or an outdated offer.
7. Worked example (illustrative, synthetic)
A seven-person team fills in the matrix and finds three gaps. The suppression check belonged to 'marketing ops', an alias of three people; it goes to the lifecycle ops manager, with the analyst as deputy. Only an engineer eight hours ahead could pause a send; pause rights go to the on-duty lifecycle marketer. Nobody owned the post-send readout; the analyst takes it, with results due five working days after each send.
Campaign ownership matrix (illustrative roles)
Copy this structure into your review document and record your observed result for each row.
| Stage | Accountable | Responsible | Consulted before | Informed after |
|---|---|---|---|---|
| Goal and brief | Lifecycle lead | Lifecycle marketer | Product manager | Analyst |
| Audience definition | Lifecycle marketer | Marketing agent (proposes) and lifecycle marketer | Analyst | Support lead |
| Consent and suppression check | Lifecycle ops manager | Lifecycle ops manager | Legal or compliance, for any new data source | Lifecycle lead |
| Content | Lifecycle marketer | Marketing agent (drafts), lifecycle marketer (edits) | Brand owner | Support lead |
| Legal and brand review | Legal or compliance | Brand owner | Lifecycle marketer | Lifecycle marketer |
| QA and test send | Lifecycle ops manager | Lifecycle marketer | Engineer, for new events | Lifecycle lead |
| Schedule and launch | Lifecycle lead | Lifecycle marketer | Support lead, for expected volume | Support team |
| Monitoring and kill switch | On-duty lifecycle marketer | On-duty marketer or engineer | Nobody: pausing needs no approval | Lifecycle lead and support |
| Post-send readout | Analyst | Analyst | Lifecycle marketer | Growth team |
| Retirement | Lifecycle lead | Lifecycle ops manager | Product manager | Support lead |
A failure worth checking
The alias as owner. An opt-out sync from a form tool fails silently on a Friday. Everyone on the 'marketing ops' alias sees the error email and assumes someone else has it, and campaigns keep going for three weeks to people who had asked to stop. Beyond the harm to those people, the FTC's CAN-SPAM guidance requires opt-outs to be honored within 10 business days and says that hiring another company to handle your email doesn't transfer your legal responsibility. Verification: ask each accountable person when they last exercised the role. A blank answer marks ownership that exists only on paper.
Common questions
Can the marketing agent own a stage?
It can do a stage's work, as responsible, where its permission matrix allows. Accountability means answering to the business for the outcome and having a deputy when you're away, so it stays with a person.
Is a matrix like this too heavy for a three-person team?
Collapse the consulted and informed columns if you like, but keep one name per stage and the kill-switch row. Those are the two parts that fail without anyone noticing.
Basis and scope
This is a proposed implementation method using illustrative examples, not a measured benchmark or a customer case study. Prepared with AI assistance. Validate product-specific behavior against current documentation and your own test environment.