Marketing teams are the hardest test of any project management tool. Volume is high, work is bursty, deadlines are real, and the same person is simultaneously running a campaign, reviewing creative, briefing an agency, and answering “can you just do this small thing” from sales. We've set up Asana for a lot of marketing teams, and most of them — left to themselves — end up with the same shape of mess after six months.
This is the reference architecture we install for marketing teams when we start cleanly, plus the operating rituals that keep it working when campaign volume spikes. It's deliberately opinionated. The point isn't that every team should copy it verbatim — it's that having any coherent structure beats the natural drift.
The structure: three layers, no more
Layer 1: Goals (where the strategy lives)
Quarterly or annual Goals at the team level — “Generate 1,200 MQLs in Q3,” “Launch the new product line by October,” “Grow newsletter subscribers to 50K.” Three to five is plenty. More and they stop being priorities.
Every project in the workspace connects to a Goal. If it doesn't, it's either strategically irrelevant or wrongly named.
Layer 2: Projects (where the work lives)
Three project types cover 95% of marketing work:
- Campaign projects.Time-bounded. One project per campaign, with a start and end date. “Q3 Product Launch,” “Holiday Promo 2026.”
- Recurring workflow projects.Ongoing. “Content Calendar,” “Paid Media — Always On,” “Customer Email Programme.” These have sections (often by status: Brief → In Production → In Review → Live) and tasks rotate through them.
- Request intake projects.One per requesting stakeholder group. “Sales Enablement Requests,” “Brand Asset Requests.” Forms feed into these so requests have a single front door instead of arriving by Slack DM.
Notice what's not on this list: a “General Marketing” project. The dumping-ground project is the single biggest predictor of Asana decay. Resist it.
Layer 3: Portfolios (where the leadership view lives)
Three Portfolios are usually enough:
- All active campaigns — for the marketing lead. One row per campaign, with start, end, owner, and status.
- Always-on programmes — for the operations lead. Recurring projects with health indicators.
- Cross-functional initiatives — for the executive view. Selected projects that have visibility outside marketing.
Each Portfolio rolls up to the relevant Goals. That gives leadership a one-screen view of where the work is and whether outcomes are on track, without anyone having to assemble a status deck.
The custom fields (small, global, enforced)
A small set of workspace-wide fields, used consistently:
- Campaign (text or dropdown) — which campaign this task belongs to, so you can filter across projects.
- Channel (dropdown) — Email, Paid Social, Organic Social, Web, Print, Event, etc. Standardised values.
- Stage (dropdown) — Brief, In Production, In Review, Approved, Live. Drives reporting more than column position does.
- Priority (dropdown) — P1/P2/P3 with explicit definitions in a pinned doc, not vibes.
- Effort estimate (number) — used by team leads for capacity planning. Optional for individuals.
Resist the temptation to add a sixth, then a tenth. Every custom field has an upkeep cost; unused fields clutter the UI and erode trust in the ones that matter.
The intake pattern: one form, one front door
The single highest-leverage configuration choice for a marketing team is the request intake form. Every request — from sales, from product, from leadership — should arrive through a form, not a DM, not a hallway conversation.
The form should capture the minimum:
- What do you need?
- Who is it for (audience)?
- When do you need it?
- What's the business outcome (the one sentence that says why)?
- What's the budget or effort range?
Form submissions land in the intake project. The marketing operations lead triages weekly: accept (assign to a campaign or backlog), defer (with a clear reason), or decline (politely). The intake project itself becomes the answer to “why are you saying no to my request?” — it's visible and prioritised.
The content calendar pattern
The most common ask from marketing teams is “how do we manage our content calendar in Asana?” The answer is a recurring project with the Timeline view enabled, custom fields for Channel and Campaign, and tasks that represent individual content pieces.
Two specifics that matter:
- Use the task due date as the publish date.Not the deadline for finishing. Other internal deadlines live as subtasks (e.g. “copy draft due,” “design due,” “legal sign-off”) with their own dates.
- Filter Timeline view by Channel.An unfiltered content calendar with 200 items is unreadable. By channel, it's a clean weekly view that anyone can scan.
The campaign template (the magic step)
Every campaign of similar shape should be created from a template. The template includes:
- Standard sections (Strategy, Creative, Production, Launch, Post-launch review).
- Standard subtasks for common deliverables.
- Pre-assigned roles where they don't change campaign to campaign.
- Default due dates relative to the campaign launch date.
A campaign that takes a marketing manager two hours to scaffold from scratch takes ten minutes from a template. More importantly, nothing gets forgotten because someone was tired the day they set it up.
The operating rhythm that holds it all together
Architecture is the easy part. Rhythm is what keeps it alive. The minimum rituals:
- Weekly intake triage — 30 minutes, marketing ops lead, work through new form submissions.
- Weekly campaign standup— 15 minutes per campaign, owner and contributors, what's blocked.
- Monthly portfolio review — the marketing lead walks the leadership team through the campaign portfolio. Status updates posted in Asana, not in slides.
- Quarterly retro and cleanup— 60 minutes, the whole team, what worked, what didn't, archive completed projects, retire unused custom fields.
What to retire from the old setup
Most marketing teams arrive at Asana from a mix of tools — Trello, Monday, spreadsheets, Notion, email. Things to actively retire as part of the rollout, not run in parallel:
- The shared spreadsheet calendar.
- The “requests” Slack channel where DMs go to die.
- The email folder that's really a backlog.
- The standing meeting that exists because no one trusts the tracker.
If you run parallel systems for more than four weeks during the rollout, you're not migrating — you're adding tools. Set a date, switch, and accept some short-term turbulence.
The honest bottom line
Marketing Asana setups don't fail because of the tool. They fail because the structure is improvised by people who are also running campaigns. A deliberate three-layer architecture — Goals, three project types, three portfolios — with a small set of global fields and an honest weekly rhythm survives the year. Most improvised setups don't survive the quarter.
If you're inheriting a marketing Asana instance that's already a mess, the highest-leverage moves are usually: install the request intake form, archive every project that hasn't had activity in six months, and introduce the weekly triage. The rest can wait until the next quarter.