We Launched the Campaign, Nobody Was Proud. Here's What Was Actually Broken.
- Jonathan Martinez
- May 14
- 4 min read

The campaign went live on a Thursday. Nobody celebrated.
We were just relieved it hadn't collapsed. The creative arrived two days late. Someone on the team had been working off a brief that had been updated without anyone telling them. And I found out about a deadline change three days after it had already shifted through a Slack message buried under 20 other notifications.
We hit publish. We moved on. And I sat with this quiet, uncomfortable question for days afterward: why does it always feel like this?
Not "why did this campaign underperform." Not "why is this team not good enough?" But why does executing a campaign feel like surviving one? The answer, when I finally found it, wasn't what I expected. It wasn't the team. It wasn't the strategy. It was the infrastructure or the complete absence of one.
Campaign management breaks in four specific places. And until I could name them exactly, I kept applying the wrong fixes. More check-ins. More meetings. More Slack channels. None of it worked because none of it addressed what was actually broken.
Here's what I found and what finally changed things.
Ownership
The first thing I noticed was that nobody actually owned the handoffs. Campaigns are cross-functional by nature, copywriters, designers, PR, external agencies. And when each of those groups lives in its own corner with its own tools and its own communication rhythms, handoffs become the casualty. Feedback lands in a meeting half the team missed. Assets are scattered across three different folders in two different drives. Your agency is still waiting on a brief that two people each assumed the other had sent.
"Nobody was dropping the ball on purpose. The ball just had no clear path from one hand to the next."
What Changed?
Before any campaign kicks off now, we build a template that maps every deliverable, every owner, every deadline. The same template, every time. And everything lives in one place, Asana where every handoff is visible and nothing quietly disappears between tools.
It sounds almost too simple. But the first time a campaign ran without a single "wait, who was supposed to send that?" moment, I understood why structure isn't a nice-to-have. It's the whole thing.
Reporting
By the time a campaign looks off track, it usually already is. And course-correcting at that point is expensive in time, in budget, and in the kind of trust that takes months to rebuild with a client or a leadership team.
I used to think we had a productivity problem. People were busy but nothing felt like it was moving. Then I read something that reframed everything: the average worker burns over 80 minutes every single workday just hunting for information they need to do their job.
"We didn't have a productivity problem. We had a visibility problem. And visibility problems masquerade as everything else."
What Changed?
We set a reporting cadence that doesn't require a meeting to function. Weekly status updates that the system generates are not someone's Friday afternoon. Monthly reviews that catch a small slip before it defines the quarter. When your campaign data deliverables, timelines, performance all live in the same place, building a dashboard stops being an ordeal and starts taking three clicks.
We connected Asana to our CRM and reporting stack. The data comes to us now. We stopped chasing it.
Workload
There was always someone buried. Always someone with breathing room nobody knew about. And the result was entirely predictable every single time: the most capable people got loaded onto the biggest campaigns, other work quietly stacked up, and nothing surfaced until a deadline got missed.
I didn't see it clearly until I started documenting how long recurring tasks actually took. Not how long I thought they took, how long they actually took. Writing copy. Producing a webinar. Building a landing page. The gap between those two numbers is where your resource planning falls apart.
What Changed?
Workload visibility. Seeing in real time what every person on the team is carrying not just this week, but over the coming weeks before the pressure becomes a crisis. We started shifting things earlier. The buried people got breathing room. The work stopped stacking up in silence.
Creative Review
Review cycles are where campaign schedules go to die. Too many reviewers. Too many versions. Feedback scattered across emails and comment threads and Slack replies that nobody can find again three days later. Nearly two thirds of marketing professionals report genuine digital exhaustion from bouncing between tools just to chase approvals. I believed that statistic the moment I read it because I had lived it for years.
"We weren't slow because we were disorganised. We were slow because our review process was designed for chaos and we'd just accepted it as normal."
What Changed?
We cut the reviewer list to only the people whose feedback would actually change the work. We told them exactly what kind of input we needed. We standardized on one design tool and connected it directly to where the project lived so review, approval, and asset storage all happened in the same place.
Version confusion doesn't survive a single source of truth. That's not a theory. That's something I watched happen in real time.
Every one of these breakdowns came from the same place: work fragmented across too many tools, with nobody having a complete picture of what was actually happening.
The answer was never working harder. It was never hiring more people. It was building the infrastructure that lets a team work with actual clarity so that when a campaign goes live, the feeling in the room isn't relief.
It's pride.
If your last campaign launch felt more like survival than success. That's not a team problem. That's a system problem. And it's fixable.
Book a free strategy session with us, and we'll map exactly where your campaign process is leaking time and energy, then show you how to close those gaps in Asana before your next launch. No pitch. Just a clear look at what's broken and how to fix it.





Comments