When campaigns ship late, the cause is rarely the campaign. It is the queue in front of it. Mapping that queue is usually the cheapest improvement available to a marketing team, and it needs no new tools.
Map the request, not the org chart
Take one real request from last month, the kind that took longer than it should have, and write down every step between the ask and the published work: who held it, how long, and what they were waiting for. Repeat for three requests. The same two or three waiting points usually appear in all of them.
The four common stalls
- Approval with no deadline: work sits with a decision maker who does not know when it is needed.
- Briefs that describe a format instead of a job: the producer guesses, and the first draft becomes a workshop.
- Single person dependency: one designer, writer or analyst that everything passes through.
- Restarting instead of editing: feedback that reopens the concept rather than improving the execution.
Fix the stall, not the symptom
If approvals are the stall, put a default: no response within two working days means the current version proceeds, and changes move to the next cycle. If briefs are the stall, require one line describing what the asset must make the reader do, and refuse briefs without it. If one person is the stall, document their part and train a second owner.
Measure the queue, then the output
Track time from request to publication, and the number of times work restarts. Both are visible without new software, both respond quickly to process changes, and both predict output better than volume targets do. A team that halves its waiting time ships more without working harder, which is the whole point of improving operations.
Keep the map current
Processes drift as teams change. Revisit the map once a quarter, with the people who do the work rather than only the people who manage it, and change one thing at a time so you can tell what worked.