How to map a marketing campaign process
How to map a marketing campaign process: parallel builds that converge on one gate, a go/no-go with a date-must-move exit, and a loop back to the next brief. Live example.
A campaign launch is several teams building at once and then needing one decision. Mapping it well means drawing the parallel builds, the single gate they all feed, the exits when the answer is not yet, and the lessons that return to the next brief.
The short version
- Draw parallel builds as separate steps that all feed one QA step.
- Put brief sign-off before builds start and give it a Changes requested exit.
- A go/no-go needs more than two exits: Go, Not ready and Date must move.
- Make slipping the date a recorded step with stakeholder notification.
- Chart pausing a live campaign as a normal exit, not a failure.
- End by returning lessons to the next brief.
Many builds, one gate
Marketing campaigns look simple on a task list and complicated in practice. Creative, channel setup and tracking are built by different people at the same time, and nothing can launch until all of them are ready. The usual failure is not a missing task but an invisible dependency: someone finds on launch morning that the tracking was never tested.
A good campaign chart has three features. Parallel builds that point at one QA step show that the launch date is set by the slowest build. A go/no-go decision with distinct exits shows what happens when the answer is not yet: fix and retest if the problem is small, move the date if it is not. And a post-campaign loop returns results to the next brief, so the process has an end that is also a start.
The example below is a general multichannel campaign. Budgets, approval thresholds and channels vary by organisation, and any day counts are placeholders. Treat it as a structure to adapt. If requests reach your team informally, start earlier with /templates/marketing-request-intake-process, and for the QA step in detail see /templates/email-campaign-qa-process. For the handoffs between teams, /guides/how-to-map-process-handoffs covers the lane crossings.
A campaign from goal to the next brief
One campaign from agreed goal to post-campaign review. Notice three builds converging on one QA step, and the loop that ends where the next campaign begins.
A brief that is signed off, not just written
The campaign starts when leadership agrees a goal, and the brief is written next. "Objective, audience and budget signed off?" is a decision with two labelled exits: Signed off continues, Changes requested returns to the brief. Putting sign-off before any build starts is cheaper than discovering a disagreement over budget after assets exist.
Parallel builds that converge on one check
"Kick off the creative and channel builds" points at three steps at once: assets and copy, channel plans and ad, email and social setup, and tracking, UTM tags and audience lists. All three lead to a single step, "Run the pre-launch QA checklist". The point of drawing it this way is that the launch date depends on the slowest of the three builds, which a linear list of tasks hides.
Go or no-go, with a date-must-move exit
"Go or no-go for launch?" has three exits: Go, Not ready and Date must move. Not ready sends the team to fix the failed checks and retest, looping back to QA. Date must move leads to an exception step that slips the date and notifies stakeholders, then also returns to fixing and retesting. Separating those two exits makes a schedule change a recorded decision instead of a quiet slide.
Launch, monitor and adjust
Go leads to launching across all channels at the scheduled time, then daily monitoring of spend, delivery and results. "Performance on track?" sends an off-track campaign to a choice between adjusting, which loops back to monitoring, and pausing live activity and reporting why. Pausing is drawn as an exit, so stopping a campaign is a defined option.
The loop back to the next brief
Every path eventually reaches the post-campaign review, then "Record results and lessons for the next brief". The final step is labelled as feeding the next campaign brief, which is the loop that makes the process improve over time. The lane columns show the campaign manager, creative, channel specialist, marketing ops and approver, so each handoff in the converging builds has an owner.
How it works
Start with the sign-off, not the build
Add the brief and a decision on whether objective, audience and budget are signed off. Label the branches Signed off and Changes requested. Everything downstream depends on this, so show it as a gate.
Split the builds into parallel steps
List the workstreams that run at the same time, such as creative, channel setup and tracking. Give each its own step and lane, and connect the kickoff step to all of them. In the Line to column, one row pointing at three rows draws the fork.
Join them at a single QA step
Point every build at one pre-launch checklist. This shows the reader that the launch waits for the slowest build and gives you a place to attach the checklist itself.
Draw the go/no-go with its three exits
Add the decision and label Go, Not ready and Date must move in Line text. Not ready returns to fix and retest. Date must move goes through a step that slips the date and tells stakeholders, then returns to the fixes.
Add monitoring and the pause option
After launch, chart daily monitoring, a performance decision, and a choice between adjusting and pausing. Adjusting loops back to monitoring. Pausing exits with a report of why.
Close the loop to the next brief
End with a review, a record of results and a final step that states the lessons feed the next brief. Agree who owns the record and where it lives; the timing is yours to set.
Mistakes to avoid
A launch checklist as a single task
Hiding the three builds inside one step hides the dependency. Draw each workstream and join them at QA.
A go/no-go with only yes and no
Without a Date must move exit, a slipped date has no owner and no notification. Give it its own branch.
Starting builds before sign-off
If the brief is not approved first, rework lands on finished assets. Put the decision before the kickoff.
Treating a pause as an unplanned event
Stopping a live campaign is a decision someone must make. Chart who decides and what is reported.
No path back to the next campaign
A chart that ends at launch loses the lessons. Add the review and the record.
Map your own campaign process
Open the campaign launch example as your own chart, swap in your channels and add the go/no-go criteria your team uses.
Related guides
Frequently asked questions
What is a marketing campaign process?
The sequence from an agreed goal through brief, build, quality check, launch, monitoring and review. Mapping it shows who builds what, where the work converges, and what decisions control the launch date.
Why draw the builds as parallel steps?
Because they happen at the same time and the launch waits for the slowest. One kickoff step pointing at several build steps, all joining at QA, shows that dependency clearly.
What should a go/no-go decision include?
At least three outcomes: go, not ready and date must move. The chart should say who makes the call; the criteria are your own and belong in the QA checklist.
Where does a campaign request start?
Often earlier than the brief. See /templates/marketing-request-intake-process for intake and /templates/email-campaign-qa-process for the QA step on email.
Can I start from a template?
Open /templates/campaign-launch-process and rename the lanes and steps to your channels. All timings are placeholders to replace.