The Marketing Department Is a Board

Most marketing teams describe their work in decks. Mine lives in a project tool, and it has for years — across an industrial coatings company, a marketing consultancy, a neighborhood news site, a coaching practice, a gym, and a handful of brands that never made it past the logo.

This paper documents the system itself: how the work is structured, what gets a project and what gets a task, where procedure lives versus where records live, and what the structure buys you when you are the entire marketing department.

It is not a case for Asana over anything else. It is a case for the shape of the work. The shape would port.

The unit of organization is the business function, not the campaign

The workspace holds roughly seventy projects grouped into portfolios, and the portfolios are not campaigns. They are functions and clients:

• Marketing — content calendars, lead boards, the website dashboard, spend
• Quality, Operations, Shipping, Banking, IT, HR — the rest of the company, where marketing has to plug in
• The consultancy — my own firm's work product
• Client portfolios — one per account, however small
• Budget — monthly spend, treated as its own function
• Project archive — where finished work goes to stay findable

The consequence is that marketing sits next to quality, shipping and banking rather than in a silo. When an audit finding or a shipping change needs to show up in customer communication, the connection is one portfolio away, not a meeting away.

A campaign, by contrast, is never a portfolio. A campaign is a project, and it ends.

Project status is a real lifecycle, including failure

Every project carries one of four states: On track, Complete, Dropped, or Archived.

Dropped is the important one. A cold-email programme built for aerospace is dropped. A LinkedIn lead board is dropped. An internal communications calendar is dropped. Those boards still exist, fully built, with the reasoning intact.

Keeping dropped work visible does two things. It stops me re-proposing an idea that already failed, and it preserves the built asset — a five-email sequence still exists whether or not it ran.

Procedure lives in the project tool; records live in the CRM

The clearest example is the inbound request-for-quote project, which is not a task list at all. It is a written standard operating procedure, structured as six sections, each step a task with its own notes and attachments:

1. Receive — four inbound types (direct email, form submission, copied-on email, spam), each with its own handling
2. CRM data entry — add the contact and log the email, verify the name, fill contact info, fill inquiry details
3. Respond — four response types, plus a support-materials task carrying the accumulated attachments
4. Update contact status — lifecycle stage, lead status, referred-to
5. Schedule continuous follow-up — create the task, enter the sequence
6. File the email — so the inbox stays a queue, not an archive

The division is deliberate. The CRM holds what happened to this lead. The project tool holds what we do with a lead — and that is where the knowledge survives a person leaving, a tool migration, or eleven months of nobody touching it.

The same split produces a department index: accounts, the shared inbox, dashboards, the automation layer, hosting, the SEO tool, plus a standing check-in list with the owner. When someone asks where a thing lives, the answer is a task, not a memory.

Content calendars are matrices, not lists

Two brands run the same calendar template, rebuilt each year, with three parts:

1. Graphics direction — the design handoff, assigned to the designer, separate from publishing
2. Dated occasions — one task per holiday or event, a year in advance
3. Per-channel completion fields — scheduled, website, and each social channel, marked Yes / No / N/A on every task

That last column set is the whole trick. A post is not "done" as a single state; it is done per channel, and N/A is a first-class answer. At a glance I can see that a holiday post went to the website and one network, was still in progress on another, and was never meant for a third.

Asset specs live with the work too — a task titled with its pixel dimensions and file-size ceiling is a brief nobody has to ask for. And the identical structure runs inward as an internal communications calendar: holiday notices, closure notifications, security awareness, credential updates. Internal comms gets a calendar because it is communication, not because it is marketing.

Lead work is a monthly rhythm with a named output

Demand generation runs on three boards, and each resolves to a deliverable with a date: a monthly lead pull per task; a board sectioned by month and by source, separating the partner's list from mine; and a campaign board where the sequence is designed before it is built.

The pattern holds even when the campaign dies: the work is designed in the project tool, built in the marketing platform, and the task remains the record of the design.

The reporting companion is the one I'd defend hardest — the dashboard project is written as questions, not metrics:

• How many referrals by month?
• What industry are they from?
• Feedback, good and bad
• What type of inquiry?
• Which product are they actually asking about?
• Which certifications do they need?
• How many leads and emails this month?

Defining a dashboard as the questions it must answer, before touching the reporting tool, is why it gets built once instead of three times.

Spend is tracked at the line item, fixed separated from variable

Spend runs monthly, one task per vendor, with fields for amount, category, and — the useful one — fixed or variable. Subscriptions, stock imagery, contractors, SEO tooling, link management, print, travel: each its own line, each with a status.

A separate project holds the stack itself, so the list of things that renew is never inferred from a credit-card statement.

That is the difference between defending a budget and reporting one — and renewal season stops being a surprise, because the fixed lines are labeled fixed.

Client work runs on one repeatable spine

Across very different clients — a coaching practice, a local news site, a gym, a services brand — the build sequence is the same three moves: logo → brand standards → website, then launch checklists for website, social and email.

Two details make it work in practice. Review happens in the task, so the comment thread and the attached versions are the record of what the client approved. And iterations get versioned tasks — header V1 through V5 — rather than one task edited five times, so you can see how many passes something actually took.

Asset tasks carry their specs in the title. A client board is legible to someone who has never seen the account.

Where the system strains

An honest paper names the failure mode. Mine is the overdue count — a long list of tasks past their due date, some carried for months.

A tracking system you have learned to ignore is worse than no tracking system, because it still costs you the time to maintain it.