Written by the AgileFever editorial team. Facts checked on November 12, 2026 against the official pages of the organizations named in this post. AgileFever sells training for some of the topics covered here, and we say so wherever it applies. Metric definitions are from the Kanban Guide. Every board, team size and number in this post is an illustrative design we built, not survey data or a client result.
Marketing work is not software work. Launch dates are fixed, nothing ships without sign-off, and a three-line social post sits next to a six-week campaign. This post sets up kanban for marketing teams so that all of it runs on one board. We already show a single marketing board in Kanban board examples for software, marketing, HR and support teams. Here we go further: item types, classes of service, exit policies, WIP arithmetic, dependencies and the three metrics that tell you whether it works.
Why kanban for marketing teams needs a different flow design
A software board can treat cards as similar things. A marketing board cannot, for four reasons.
| Feature of marketing work | What goes wrong on a plain board | Design response |
|---|---|---|
| Fixed launch dates | A card finishes late and the date is already public. First in, first out ignores the deadline. | A class of service for date-bound work, with a latest start date worked out from past cycle times. |
| Approvals and legal review | Work waits in someone’s inbox and looks like it is still in progress. | Approval is its own column with a limit, a named approver and a response time. |
| Many small items beside big campaigns | One average cycle time mixes a 3-day email with a 35-day campaign and means nothing. | Work item types, with metrics read per type. |
| Design and agency dependencies | Cards stall and nobody sees why. | A blocked flag with a reason and a date, and a rule for escalation. |
The Kanban Guide from Kanban University (version 2025.5, updated May 1, 2025, checked November 12, 2026) asks for a workflow with a definition of work items, start and finish points, workflow states, a WIP control method, explicit policies and a service level expectation. It does not name columns, classes of service or exit policies. The rest of this post makes those choices for a marketing team.
Model campaigns and content on one system
Kanban for marketing teams works best on one board with two levels of card, not two boards. A campaign card is a parent that tracks the whole effort and the launch date. Each asset it needs (a landing page, three emails, an ad set) is a content card tagged with the campaign name. Content cards move through the columns. The campaign card sits in a top lane with its own limit.
| Work item type | Example | Typical size | Metrics read separately |
|---|---|---|---|
| Campaign (parent) | Spring product launch | Weeks | Cycle time from kickoff to launch |
| Content asset | Blog post, landing page, ad set | Days | Cycle time, throughput |
| Small task | Social post set, SEO refresh | Hours to days | Throughput |
Classes of service say how a card is treated when capacity is tight. Class of service comes from the Kanban method and is not in the Guide, so write your own rules down. Our post on class of service and work item type explains the idea. A starting set for marketing:
| Class | Use it for | Pull rule | Limit |
|---|---|---|---|
| Fixed date | Launches, events, webinars, campaign flights | Pull when the latest start date arrives, whatever else is waiting | Set by the number of live campaigns |
| Expedite | A correction, a legal removal, a response to a public problem | Pull ahead of everything and replace a card rather than add one | 1 card on the whole board |
| Standard | Blog posts, case studies, emails with no hard date | First in, first out | Column limits |
| Always-on | Weekly social, newsletters, SEO refreshes | Pull when a slot is free, never ahead of fixed-date work | Column limits |
Use swimlanes for the class of service, not for every channel. Four lanes stay readable; twelve channel lanes do not. Show the channel as a tag on the card.
Columns and exit policies, including approval and legal
Seven columns cover the usual path. A card may move right only when its exit policy is true. Write the policy on the board, in the column header.
| Column | Limit | Exit policy: a card moves on when |
|---|---|---|
| Ideas | None | Someone has asked for it and named an owner |
| Ready | 4 | The brief is written (goal, audience, channel, date), and the card is tagged needs legal if it makes a claim, offer or comparison. It is a queue, so not counted as started |
| Creating | 5 | Copy and design are complete, tracking links added, assets in the shared folder |
| Internal review | 2 | One reviewer has given one consolidated round of comments and the maker has resolved them |
| Approval | 3 | The named approver has signed off. Legal reviews only cards tagged needs legal, within 2 working days of entry |
| Scheduled | 2 | The asset is queued in the publishing tool for its date and the link was tested |
| Live | None | Published. The finish point. Record the date on the card |
Illustrative design. Started work runs from Creating to Scheduled; Ready is a queue before the start point.
Tagging needs legal in Ready matters more than any other rule here. If legal sees the card for the first time at Approval, the late finding sends the card back to Creating and doubles its cycle time. The tag moves that conversation to the start. Give approvers a response time (two working days, for example) and a named backup. A single approver with no response time is a typical bottleneck. This is a process rule, not legal advice: which claims need legal review is a decision for your own legal team.
WIP limits by column and by person, with worked numbers
The Guide says only that members must control the number of items in the workflow. It sets no number. Little’s Law gives a way to choose one. Average cycle time equals average WIP divided by average throughput, for a stable system. See Little’s Law.
Take the content lane of a team of 5 makers (2 writers, 1 designer, 1 campaign manager, 1 email specialist). Over eight weeks it finished 40 items, 5 a week, with 20 items started at any time.
- Average cycle time now: 20 / 5 = 4 weeks.
- Target of 2.4 weeks at the same throughput: WIP = 2.4 x 5 = 12 cards.
- Split the 12 across the started columns: Creating 5 (one per maker), Internal review 2, Approval 3, Scheduled 2.
Cycle time = WIP divided by throughput. Throughput held at 5 items a week in every row.
Illustrative example: arithmetic on invented numbers, not data from any company. Real throughput moves when WIP changes, so lower limits in steps.
Per-person limit. No maker owns more than 3 started cards: one being worked and two waiting on others. Five makers times 3 gives 15 slots against 12 column slots, so the column limits bind for the team, and the person limit stops one maker holding five cards. For the general method of choosing and tuning limits, see how to set WIP limits.
Campaign cards get their own limit. If your team can support 3 campaigns at once, set the lane to 3 and let a fourth wait in Ideas.
Design and agency dependencies as blocked work
The Guide lists unblocking blocked work as part of managing items but does not define blocked, so define it in your policies: a card is blocked when nobody on the team can move it forward. Three rules keep dependencies visible.
| Situation | Board treatment | Rule |
|---|---|---|
| Waiting on a designer outside the team, a few days | Blocked flag on the card, with reason and date | The card stays in its column and keeps counting against the limit |
| Routine handoff to an agency | A separate With agency column between Ready and Creating, limit 2, due date on the card | Chase on the due date. Past it by 2 days, the owner tells the sponsor |
| Customer or partner sign-off | Blocked flag naming the person | After 5 working days, decide to drop, replace or escalate |
Moving blocked cards to a parking column makes the limit look healthy while work rots. Review blocked cards weekly and ask what the dependency is, not who is slow. Record blocked days per card; the Guide has no measure for it, so define your own.
Three metrics to track, with a worked example
The Guide defines cycle time as the elapsed time between a work item starting and finishing, throughput as the number of items finished per unit of time, and work item age as the elapsed time between starting and the current date. For kanban for marketing teams, read all three per item type. A mixed average hides the story.
Cycle time by item type
| Item type | Finished items | Median (days) | 85th percentile (days) |
|---|---|---|---|
| 8 | 4.5 | 9 | |
| Blog post | 10 | 6.5 | 12 |
| Campaign | 5 | 35 | 49 |
Illustrative example: invented cycle times in calendar days. Percentile by nearest rank: for 10 blog posts finishing in 3, 4, 5, 5, 6, 7, 8, 9, 12 and 16 days, the ninth value is 12. Five campaigns is a very small sample.
The blog result becomes a service level expectation, which the Guide describes as a forecast of how long an item should take, based on historical cycle time: 85% of blog posts finish within 12 days. The campaign result gives a planning rule. For a launch on March 2, 2027, subtract the 85th percentile of 49 days to get a latest start date of January 12, 2027.
Throughput per week
Content lane. Count of cards reaching Live each week.
Illustrative example: 40 items in 8 weeks, an average of 5 a week. It feeds the Little’s Law arithmetic above. For why this is not velocity, read Kanban velocity vs throughput.
Work item age
Age applies to cards still on the board, so it warns you before a card finishes late. Check it in the weekly meeting, oldest first.
| Card | Column | Age (days) | Expectation | Action |
|---|---|---|---|---|
| Blog: onboarding tips | Creating | 4 | 12 days | On track |
| Email: spring email 2 | Approval | 8 | 9 days | One day left: ask the approver today |
| Blog: customer story (blocked 3 days) | Approval | 14 | 12 days | Past expectation: escalate the customer sign-off |
Illustrative example. For the charts behind these numbers, see Kanban reports explained. To compute them from your own dates, use the free flow metrics analyzer.
A sample kanban board for marketing teams
This snapshot uses the limits above. Every column is at or under its limit. A card marked [B] is blocked.
| Lane | Ideas (none) | Ready (4) | Creating (5) | Internal review (2) | Approval (3) | Scheduled (2) | Live |
|---|---|---|---|---|---|---|---|
| Fixed date | Partner event page | Spring: email 3 | Spring: landing page Spring: video cut (agency) [B] |
Spring: ad set | Spring: email 2 | ||
| Expedite (limit 1) | |||||||
| Standard | Case study idea Webinar recap Pricing FAQ |
Blog: onboarding tips Newsletter Dec |
Blog: churn Newsletter Nov |
Blog: pricing | Customer story [B] | Blog: roadmap | Release notes |
| Always-on | Social set, week 48 | Social set, week 47 | SEO refresh batch | Weekly digest | |||
| Count | 4 | 4 of 4 | 5 of 5 | 2 of 2 | 2 of 3 | 2 of 2 |
Illustrative example, not a real team. Started work: 5 + 2 + 2 + 2 = 11 cards, under the total of 12. Ready is a queue and is not counted as started.
If you want a blank board to copy, use the Kanban board template. If you have no budget for a tool, free Kanban boards for startups lists what to check before picking one.
A four-week rollout
List the last 20 finished items with start and finish dates. Sort them into campaign, content asset and small task. Draw the columns from the path those items took, not the process chart.
Write an exit policy per column, an approver response time and the needs legal rule. Set limits from the Little’s Law arithmetic and the personal cap.
Add the classes of service, the blocked flag with reason and date, and a latest start date on every fixed-date card. Hold the first weekly review, oldest card first.
Compute cycle time by type, throughput and age. Write the first service level expectations. Change one limit, then leave the board alone for two weeks.
Mistakes in kanban for marketing teams
| Mistake | What it causes | Fix |
|---|---|---|
| Averaging a campaign and a tweet together | A cycle time that describes neither | Read metrics per item type |
| No named approver or response time | Approval becomes the longest queue | One approver, a backup, a 2-day response in the policy |
| Discovering legal review at the end | Cards bounce back and cycle time doubles | Tag needs legal in Ready |
| Letting every request in as urgent | Expedite grows until nothing is expedited | Limit expedite to 1 card on the board |
| Parking blocked cards in a side column | The limit looks healthy while work waits | Keep blocked cards in place and flagged |
Where AgileFever fits
We sell the Team Kanban Practitioner course, and our board here uses its ideas, so weigh our view accordingly. As listed on November 12, 2026, the Team Kanban Practitioner course costs $600 or ₹14,999, and the next listed batch starts on November 20, 2026. Rupee prices are before the 18% GST we add at checkout for buyers in India. You do not need it to use this post. It suits a team that wants a trainer to review its own board.
Additional discounts are available. Contact us to know more.
Questions people ask
Is Kanban good for marketing teams?
Kanban suits marketing teams whose work arrives continuously and in different sizes, because it limits started work and shows where cards wait. It fits less well for one large project with a single date. Add classes of service so fixed-date campaigns are not treated like routine content.
What columns should a marketing Kanban board have?
For kanban for marketing teams, seven cover most boards: Ideas, Ready, Creating, Internal review, Approval, Scheduled and Live. Give Approval its own column with a limit and a named approver, because that is where marketing work waits longest. Write an exit policy in each column header.
How do you handle campaign deadlines on a Kanban board?
Use a fixed-date class of service. Take the 85th percentile cycle time for that kind of work, subtract it from the launch date, and pull the card on that latest start date. In the example here, 49 days before March 2, 2027 is January 12, 2027.
How many WIP limits should a marketing team set?
Put a limit on every column between the start and finish points, and cap each person at around three started cards. Choose the total from Little’s Law: target cycle time multiplied by weekly throughput. At 5 items a week and a 2.4-week target, that is 12 cards.
How do you manage work that depends on an agency?
Flag the card as blocked with a reason and a date, and keep it inside its column limit. For routine handoffs, add a With agency column with its own limit and a due date. Review blocked cards weekly and set a rule for escalation.
