How do marketing teams run projects without losing their mind?

What makes marketing project management actually hard?

The short version: marketing work is creative, cross-functional, and has a lot of stakeholders who do not work in the same tool. That combination breaks most of the assumptions that built tools like Jira or Linear. A piece of marketing work is rarely a self-contained ticket. A single product launch can involve a landing page, a press release, three blog posts, a sequence of social posts, an email, a paid campaign, a sales enablement deck, and someone from legal who wants to read the headline before it goes out. Anatomy of work research keeps finding that this kind of cross-functional handoff is where most of the day disappears.

Each of those pieces has its own review loop. The landing page needs design feedback, then copy feedback, then a developer pass, then a stakeholder check. The blog posts need an editor, possibly an SME, possibly legal. The social posts need someone with brand sign-off. The email needs deliverability and a final read from the campaign owner. None of these are technically hard, but they all happen in parallel and they all converge on a launch date.

The other thing that makes marketing PM hard is that the people approving the work are not always the people producing it. A founder might review the homepage. A product manager might own the launch narrative. A sales VP might want to see the cold email sequence. These people are not going to live in your project tool. They will give feedback in Slack, in an email, on a printed-out page, on a phone call. Pretending otherwise is how campaigns slip.

Where does marketing project management usually break down?

It almost always breaks in the same few places: vague briefs, scattered feedback, weak handoffs, and a content calendar that does not match what is actually being produced. Each one looks small in isolation, but together they make a campaign feel like it is being held together with tape.

Vague briefs are the most common failure, which is why we wrote a longer note on organizing briefs, drafts, and reviews. A request comes in as a Slack message that says something like "we need a landing page for the new feature." Nobody pushes back, work starts, and three rounds in someone realises the audience was wrong, or the offer was unclear, or the channel mix had not been agreed on. Every campaign deserves a brief that names the audience, the outcome, the channels, the asset list, and the launch date before any production starts. If the brief cannot be written, the campaign is not ready.

Scattered feedback is the second one. Someone leaves a comment in a Google Doc. Someone else replies in Slack. The designer gets a Loom video from a stakeholder. Someone forwards an email with notes from a meeting. The designer has to reconcile all of this, often misses something, and gets another round of comments that say "you missed the thing I said in Slack." Batching reviews into a single window, with a single channel for comments, fixes this faster than any tooling change. A campaign board where assets sit with their comment threads attached is the closest thing to a real fix. We built asset reviews into Breeze for exactly this reason: feedback lives next to the work, not in seven different inboxes.

Weak handoffs are the third. Content finishes a post, but nobody tells the SEO person it is ready. Design finishes a hero image, but nobody routes it to the dev team to ship. Legal approves a claim, but nobody updates the actual copy. Every handoff that depends on someone remembering to send a message is a handoff that will eventually fail. Tasks with clear owners and a board that shows what is waiting on whom prevent most of this.

Finally, the content calendar problem. Marketing teams love calendars, and most of them keep one in a separate place from where the work actually happens. The calendar says a post is going out on the 14th. The production board has no idea. The post is not written. By the 12th, panic. A calendar is only useful if it is connected to the production board, so a slipped task moves the calendar date and someone sees it before the launch week. We dig into this more in our note on content planning workflow and the spreadsheet trap in managing campaigns without spreadsheets.

Is engineering-style project management the right model for marketing?

Mostly no. Engineering and marketing share a lot of vocabulary, which causes most of the confusion. Both use boards, both use tickets, both have sprints in some form, both have owners and reviewers. But the underlying work is shaped differently, and the tools that fit engineering well tend to feel awkward when a marketing team tries to live in them.

Engineering work is usually estimable, repeatable, and has a clear definition of done. A ticket is closed when the code is merged. Reviews happen in a pull request, and the reviewer is almost always another engineer. Marketing work is rarely estimable in the same way. A first draft can come back fine in one round or take five. A landing page can ship in a week or take three because someone in leadership wants to revisit the offer. Reviews involve people who are not in the team, do not use the tool, and do not think in tickets.

You can borrow a lot from engineering: clear owners, written briefs, a single board, regular standups when they help. But the assumption that work moves in clean sprints from todo to done is the part that does not survive contact with a real marketing calendar. Atlassian's own writing on cross-functional teams makes a similar point, even though their tooling is built around the sprint model.

Which workflows fit marketing, and which are eng-shaped misfits?

The workflows that fit marketing are the ones built around campaigns, assets, and channels, not tickets and sprints. The ones that do not fit are usually borrowed wholesale from a developer toolkit and forced onto creative work.

Workflows that fit marketing well

A campaign board with a clear start and end. Each campaign gets its own board, with the brief at the top, the asset list as task groups, and the launch date as a milestone. Everyone working on the campaign can see what is in production, what is in review, and what is blocked. This is roughly how marketing campaign boards work in Breeze and it is the structure that fits how marketing teams actually think.

Brief intake as a first step. Before any work starts, a brief gets filled in. Audience, outcome, channels, assets, dates, owner. If a stakeholder cannot fill in the brief, the campaign is not ready to start. This single step kills more wasted production cycles than any other change.

Asset reviews with batched feedback. Each asset has a review window. Comments land on the asset itself, not in side channels. The owner consolidates and the producer addresses them in one pass. Two rounds is the goal. Three is acceptable. Five means the brief was wrong. The same pattern shows up when teams use Breeze to manage client campaign requests.

A content calendar that reads from the production board, not a separate spreadsheet. When a piece slips, the calendar updates. When the calendar updates, the campaign owner sees it.

Workflows that are eng-shaped misfits

Sprints. A two-week sprint does not match a campaign that ships in six weeks. Forcing marketing into sprints usually means tasks get split into artificial chunks and the campaign view is lost.

Story points. Estimating a blog post in story points is theatre. Marketing teams need to know how long things usually take so they can plan launch dates, but the engineering ritual of pointing every task burns more time than it saves.

Per-ticket reviews with no asset attached. Reviewing a landing page in a Jira ticket without seeing the actual landing page is the marketing equivalent of code review without the code. Marketing tools that handle this well let the asset live with the task.

Heavy permissioning. Most marketing teams need their stakeholders, agencies, and freelancers to be able to drop in on a campaign without an IT process. Tools that gate every guest behind seats and role configuration tend to push the real work back into email.

What a workable marketing setup actually looks like

The setup that tends to hold up is boring and practical. A board per campaign. A brief at the top of each board. Asset reviews that batch feedback. A content calendar pulled from the production board. A short standup or written check-in once a week, not five meetings.

For a typical mid-size marketing team, the day-to-day looks something like this. A request lands in an intake form, which becomes a draft brief. The campaign owner reviews the brief with whoever requested it, sharpens the audience and outcome, agrees on the asset list, and only then opens the campaign board. Production tasks get added with owners. Asset review tasks are queued for specific windows, not "whenever you can." Stakeholder reviews are batched. Legal sees the work once, not three times. The calendar reflects the actual state of production.

When Breeze customers describe their marketing setups to us, the ones that run smoothly almost always have those same pieces: a campaign board they can point a stakeholder at, a brief that survived an honest conversation, asset reviews in one place, and a content calendar that is not a separate world from production. The ones that struggle usually have great briefs that nobody references, or a calendar that lives in a Notion page that nobody updates, or a production tool that the freelancers refuse to log into.

Launches deserve their own note. A launch is a project with hard dependencies and a fixed date. Treat it like one. HBR's marketing writing reads the same way: a launch is closer to operations than to creative. Map out everything that needs to happen, who owns each piece, what blocks what, and what the no-go criteria are. The press release cannot go out before the page is live. The page cannot go live before legal signs off. The email cannot send before the page is live. These are obvious in hindsight and routinely missed in practice because no one drew the dependency map.

A few questions worth answering before you change tools

Do our briefs name an audience, outcome, channels, and asset list before work starts?

If not, no tool will fix the downstream mess. Fix the brief intake first.

Where does stakeholder feedback actually live today?

If the honest answer is Slack DMs and forwarded emails, the project tool is not the source of truth, and adopting a new one will not change that on its own.

Can we template one campaign type cleanly?

Pick the campaign you run most often, get the board, brief, and review cycle right, then copy it. Do not try to template the whole department at once.

Pick one campaign type and get the process clean for it

If you take one thing from all of this, take this: do not try to fix marketing project management by rolling out a new tool everywhere at once. Pick one campaign type, usually the one you run most often, and get the process clean. Write a real brief. Build one board for it. Batch the reviews. Connect the calendar. Run a couple of cycles, watch where it still breaks, and adjust. Then template it. Then move on to the next campaign type.

Marketing project management is not a software problem, but the right software helps. Look for something that treats campaigns and assets as first-class objects, lets stakeholders in without friction, and keeps the calendar connected to the production board. Avoid anything that feels like a developer tracker in a marketing skin.

If you want to see what a marketing-shaped setup looks like in practice, a marketing campaign board in Breeze is a fair starting point, but the bigger win is the process you build around it.