One place where work lives
The single most useful rule in marketing operations is that work exists only if it is in the work system. A request that arrives by email is not accepted until it is in the intake form. A review that happens in a chat thread is not complete until the decision is recorded on the work item. A launch date agreed in a corridor is not real until it is on the item. The rule sounds strict, and teams resist it for a few weeks, but without it no calendar is accurate, no capacity conversation is possible and no process can be measured.
The choice of approach comes before the choice of tool. Three broad approaches exist. A board shows work moving through stages and suits the continuous flow of campaigns, content and requests. A dated plan shows tasks with dependencies against a timeline and suits large launches and events. A queue shows requests in order and suits service-style work such as design or web changes. Most marketing teams need a board as the default, a dated plan for a few large pieces of work and a queue for one or two shared services. Choose a tool that can show the same items in all three views, rather than three tools that each hold part of the work.
Which product to buy is a separate decision with its own criteria, and the guide to choosing and evaluating marketing tools covers how to run that evaluation. The operational requirements to bring to it are the ones in this guide: work types, stages, views, links to assets and approvals, and reporting.
Boards, stages and work types
A board is only as useful as its design. The two design decisions that matter are the work types it holds and the stages each type passes through. Work types are the categories of work that behave differently: a paid campaign, a content piece, an email, a web change, an event. Each needs different fields, different stages and different reviews, so treating them as one type either buries simple work in process or leaves complex work under-controlled.
| Work type | Typical stages | Fields that matter | Review |
|---|---|---|---|
| Campaign | Intake, brief, build, review, launch check, live, closed | Objective, channels, budget, campaign name, success measure, launch date | Matrix by risk |
| Content piece | Idea, brief, draft, edit, review, scheduled, published | Topic, format, owner, target page, publish date | Editorial and brand |
| Email or nurture step | Request, build, test, review, scheduled, sent | Audience, template, send date, offer | Brand, and compliance where there is an offer |
| Web or landing page change | Request, spec, build, QA, review, live | Page, change type, tracking needed, deadline | Brand and technical QA |
| Event | Plan, logistics, promotion, delivery, follow-up | Date, venue, budget, registration route | Budget holder |
| Small request (fast lane) | Request, done, checked | Asset used, channel, date | Launch check only |
Stages should map to decisions, not to people. "With design" is a person; "build" is a stage that may involve design, copy and a channel specialist. When stages are named after people, the board becomes a map of who is busy rather than of where work is, and every reorganisation breaks it. Keep the number of stages small enough that every item can be seen on one screen per work type, and give each stage an exit condition so that "done" means the same thing to everyone.
Keep required fields to the minimum that a report or a decision actually uses. Every field nobody reads is a small tax on adoption, and adoption is what makes the system worth having.
The marketing calendar as the single view
The marketing calendar answers a question that every stakeholder asks: what is going out, when, and on which channels? It is also how the team spots collisions, such as two promotions to the same audience in the same week, or a launch landing on a day with no one available to monitor it. The campaign calendar guide covers how to plan a calendar from the marketing plan, and the content pillars and calendar guide covers the editorial calendarA shared schedule of what content will be published, on which channel, when and by whom.; this section is about keeping whichever calendar you plan accurate once work starts moving. The content calendar template lists the fields each editorial row needs before it becomes a work item.
The operational answer is to make the calendar a view of the work system rather than a document of its own. Every work item has a launch or publish date; the calendar is those items, filtered and displayed by date and channel. When a date changes on the item, the calendar changes with it. A calendar maintained by hand in a spreadsheet alongside the work system is always out of date, because updating it is a second task that nobody owns.
Two layers help. A planning layer holds the campaigns and themes agreed in the plan before work items exist, so that the calendar shows intent as well as committed work. A committed layer holds the work items themselves. Planned entries become committed ones when they pass intake. Colour or label by work type and channel, not by person, and give stakeholders read access to the calendar view so that they stop asking for updates by email. A team that markets in several countries can add a market field and a saved view per market, as the tutorial on building a marketing calendar for several markets does.
Asset libraries, versioning and rights
An asset library is a system of record: the place where approved creative, copy, brand files and templates live. Its job is to make the current, approved, licensed version of an asset the easiest one to find. When the library fails, people reuse whatever they can find in old campaign folders, and out-of-date offers, superseded logos and images whose licence has expired go live.
Four pieces of information turn a shared drive into a library. Approval status says whether the asset is approved for use, and by whom. Version says which iteration it is, with older versions archived rather than deleted. Rights records where the asset may be used, for how long, and any restrictions, which matters most for licensed photography, music, model releases and creator content. Expiry is a date after which the asset must not be used, with a routine that flags assets approaching it.
The library and the work system should link rather than duplicate. A work item points to the assets it uses; the asset records which campaigns used it. That link makes it possible to answer, quickly and reliably, where an asset is live when its rights expire or a claim in it must be withdrawn. Without it the answer is a search through every channel by hand. The tutorial on setting up a marketing asset library turns those four pieces of information into a field set and walks the move from shared folders step by step.
Templates and intake forms
Templates and intake forms are how the work system shapes work before it starts. An intake form per work type collects the information that the first stage needs, in a consistent format, and refuses requests that lack it. A template per work type creates the item with its stages, its subtasks and its standard fields already in place, so that nobody builds a campaign plan from a blank page.
Good intake forms are short and specific. They ask for the objective, the deadline and the reason for it, the channels, the budget source, any offer or claim, and a proposed campaign name in the agreed format. The campaign name and tracking fields are where the work system meets data operations: a form that builds the name and the UTMURL tags identifying traffic source. parameters from dropdowns, rather than accepting free text, removes a whole class of reporting errors at the source. The data operations guide sets the taxonomy those dropdowns use. Requests for a new tool are a work type of their own, and the guide to handling requests for new marketing tools sets out the few questions their intake form needs and how to triage them against the tools already owned.
Templates should carry the procedure as well as the structure: each subtask links to the SOP for that task, and the final subtask is the launch check. When a procedure changes, update the template so that new work picks it up; work already in flight keeps the version it started with.
Reporting from the work system
A work system that is used properly becomes a source of operational reporting that no other system can provide. It knows how long each item spent in each stage, how often items were sent back, how much work of each type the team delivered, and how much is waiting. Those are the measures that tell a marketing lead whether the operation is healthy, and they come for free once stage changes are recorded.
| Report | What it answers | Built from |
|---|---|---|
| Cycle time by work type and stage | Where does work wait? | Stage change dates |
| Rework by gate | Which gate returns most work, and why? | Returns with reason codes |
| Throughput by work type | How much does the team deliver? | Items closed per period |
| Work in progress and ageing | What is stuck? | Open items by stage and age |
| Capacity versus demand | Can we take on more? | Accepted requests against delivered items |
| Late launches | Which commitments slipped, and at which stage? | Planned against actual launch date |
Treat these as operational measures for improving the system, not as a KPIA metric tied directly to an objective. for individuals. When cycle timeThe elapsed time from an accepted request to live work, read stage by stage to show where work waits; a process measure, not a target for individuals. becomes a personal target, people skip gates and close items early. Changes to the work system, such as a new intake field or a merged stage, can be compared over a reasonable period in the same spirit as an A/B TestControlled comparison of two variants.: change one thing, watch the measure it should move, and keep or revert. When the work in progress report shows more open than the team ever finishes, the guide to limiting work in progress turns it into agreed limits by stage and a ready queue that new work is pulled from.
A B2B services firm consolidates its work
Calder & Finch, a professional services firm with a marketing team of twelve, ran work across an email inbox, a chat channel, two spreadsheets and a project tool that only the content team used. Its campaign calendar was a spreadsheet updated on Mondays. The team defined five work types, built an intake form and a template for each, and made the calendar a filtered view of the project tool. Requests outside the form were answered with a link to it. Within one quarter, 92% of work items were in the tool, the calendar stopped needing a weekly update, and the first cycle-time report showed that web changes waited an average of 9 working days for a developer, which became the case for a shared web queue.
When a new work management tool is introduced, the marketing tool onboarding SOP covers access, configuration, training and ownership so the tool is actually adopted.
Common mistakes
- Buying the tool before designing the work. Without work types and stages agreed, any tool becomes a digital version of the old chaos.
- Stages named after people. The board then tracks who is busy rather than where work is, and breaks at every reorganisation.
- One work type for everything. Simple requests get buried in campaign process, or campaigns get the light process meant for requests.
- A calendar maintained by hand. It drifts from the work system within weeks; make it a view instead.
- A shared drive called an asset library. Without approval status, versions, rights and expiry, it cannot stop the wrong asset going live.
- Free-text campaign names on intake forms. Every variation becomes a reporting problem later; build names from controlled fields.
- Too many required fields. Each unused field lowers adoption; remove fields that no report or decision uses.
- Never reporting from the system. The work system's measures are what justify the effort of keeping it current. The systems hub explains how this fits alongside data operations.
