Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Operations

Marketing Process Design

Process design decides how a marketing request becomes live work: the stages it passes, the procedures used inside each stage and the handovers between people. This hub explains the four parts of a marketing process, points to the core workflow and procedure guides, adds further guides on reviewing errors, mapping a process, service levels for requests, prioritising operations work, limiting work in progress, handovers when someone leaves and key-person risk, and shows how to measure whether the process is getting better.
SectionintermediateUpdated

In this section

Why process beats heroics

Every team has a few people who can rescue a launch at the last minute. They know which platform setting breaks the tracking, which stakeholder must see the copy before it goes out and where the current logo files are. Teams lean on them because it works, until one of them is on holiday, leaves, or is simply doing three rescues at once. Heroics scale with headcount at best; usually they scale worse, because the rescuers become the bottleneck for every launch.

A designed process moves that knowledge out of heads and into the route itself. The stage that asks for a campaign name in the agreed format at intake removes the evening spent renaming ads before launch. The written procedure for setting up a paid campaign means a new starter gets the tracking parameters right without asking. The gate that requires a signed brief before build stops creative being made against an idea nobody approved. None of this is bureaucracy for its own sake: each element exists because a specific, recurring failure costs more than the element does. If a stage or a check cannot be traced to such a failure, it is a candidate for removal, and good process design removes as readily as it adds.

Workflow, procedures, handovers, improvement

Process design has four parts. They are easy to blur together, and most process problems come from fixing the wrong one.

PartWhat it decidesWhat it looks like when it worksWhere it is covered
WorkflowThe stages work passes through and the gates between themEvery item has a visible stage; nothing skips a gateCampaign workflow guide
ProceduresHow a recurring task inside a stage is doneA new starter completes the task from the document aloneSOP tutorial
HandoversWhat passes between people or teams, and in what stateThe receiver never has to chase missing informationThe core guides, at each stage boundary; Handing over work when someone leaves
ImprovementHow the process is reviewed and changedMeasures are reviewed on a cadence and stages are retired as well as addedThis page, below; Prioritising operations work, Mapping a marketing process

The workflow is the skeleton and the procedures are the muscle. A workflow without procedures tells people where work goes but not how to do it, so quality varies by person. Procedures without a workflow are a library nobody opens at the right moment. Handovers are where the two meet, and they deserve explicit design: a handover is complete when the receiving person has everything needed to start, not when the sender has pressed send. Improvement is the part teams forget, and the reason documented processes drift away from practice within a few months.

The core guides

The core guides are written to be read in order.

  • Campaign workflow from intake to launch draws the end-to-end route: how requests are taken in and triaged, how the brief and kick-off work, how build, creative and trafficking run in parallel, which review and approval gates sit before launch, and what the handover after launch must contain. It is the map on which every other operations fix is drawn.
  • Writing a marketing SOP step by step is a tutorial that produces one standard operating procedure for one recurring task, from choosing the task to rolling the procedure out and scheduling its review. It includes a template you can copy.

The published campaign launch QA checklist is the companion to both core guides. The workflow decides where the launch check sits; the SOP tutorial shows how to write a procedure that ends in a checklist of that kind. Checks on tracking parameters, including every UTM on every link, belong in that checklist rather than in someone's memory. For the wider context of process alongside systems and governance, start from the marketing operations hub.

Further guides

Further guides cover the work around the route: seeing it as it really runs, learning from errors, agreeing what requesters can expect, deciding which fixes come first, controlling how much is open at once, and keeping work going when people leave or are away:

Measuring a process: cycle time and rework

A process that is not measured cannot be improved except by opinion, and opinions about process are usually shaped by the last bad week. Two measures do most of the work, and both can be recorded in any work management system that tracks stage changes.

Cycle time is the elapsed time from an accepted request to live work. Break it down by stage and the picture becomes useful: most of the time a campaign spends in a workflow is waiting rather than working, and the stage where it waits longest is usually a review queue or an asset request. Shortening the work itself rarely moves the total; removing the wait does. The theory of constraints and its focusing steps turn that observation into a method: find the stage that limits throughput, get the most from it, pace the rest of the workflow to it, then add capacity there. Waits also grow when too much is open at once, and the guide to limiting work in progress sets limits by stage or by person from the team's own records and pulls new work in only when something finishes.

Rework is the share of items sent back from a gate to an earlier stage. A high rework rate at the approval gate usually means the brief was weak, not that the reviewer is difficult. Rework at the launch check usually means the build procedure is missing a step. Each returned item should carry a reason, so the pattern can be read.

Treat both as operational measures, not as a KPI for the people in the process. If cycle time becomes a target for individuals, gates get skipped to hit it. Changes to a process can be tested much as campaigns are: run the new stage on one stream of work, keep the old route on another, and compare over a reasonable period. It will not be a clean A/B Test, but it beats changing everything at once and guessing which change helped.

Illustrative example — not a real result

A furniture retailer reads its cycle time

Oakhurst Living, an online furniture retailer, logged stage changes for every campaign for one quarter. The median cycle time was 19 working days, of which 8 were spent in "awaiting brand review" and 4 in "awaiting assets". Rework at the brand review gate was 41% of items, and the most common reason given was "offer wording not agreed". The team added an offer field to the intake form that required sign-off from the trading manager before a brief could be written. In the following quarter, rework at brand review fell to 17% and median cycle time to 13 working days, with no change to the reviewer or the build team.

Common process problems

Most process complaints are one of a few symptoms. The table routes each to the guide that fixes it.

SymptomUsual causeGuide
Requests arrive by email, chat and corridorNo single intake route with required fieldsCampaign workflow
Creative is rebuilt after reviewBrief not signed before build; reviewers see work too lateCampaign workflow
The same launch mistake keeps recurringThe task has no written procedure, or the procedure lacks a checkWriting a marketing SOP, Reviewing a marketing error
New starters ask the same questionsProcedures exist only in people's headsWriting a marketing SOP, Building an onboarding pack
Tracking is wrong on live campaignsLaunch check missing or skippedCampaign launch QA checklist
Documents describe a process nobody followsNo owner and no review date on proceduresWriting a marketing SOP
Nobody knows what happens after launchNo post-launch handover definedCampaign workflow
A problem on a live campaign ran for days before anyone saw itNo named monitor, unclear limits on changes, no cover, no normal range, silent tracking or no route for reportsLive campaign problems found too late
Much is started and little is finishedToo much work open at once; new work pushed in before current work finishesLimiting work in progress
Requesters cannot tell when work will be doneNo agreed turnaround by request type; the requester's side never written downSetting service levels for requests
Work stops when one person is away or leavesRecurring tasks and admin rights held by one person; cover never testedReducing key-person risk, Handing over work when someone leaves

When a process symptom has already reached the reports, such as campaigns that cannot be grouped or a monthly pack that takes days, the marketing operations troubleshooting section diagnoses it cause by cause.

Terms used on this page

Frameworks

Related