Kanban Metrics for Marketing Teams: What to Track in Jira

[#1]

When people talk about Kanban metrics, the examples are almost always from software teams — Cycle Time on a dev board, WIP limits on engineering columns, throughput per sprint. But marketing teams run on flow just as much as engineering does, and often with far more handoffs.

A single campaign asset usually passes through a brief, a first draft, design, an internal review, a stakeholder or legal approval, scheduling, and finally publishing. Every one of those steps is a place where work can sit and wait. And unlike a dev bug, a delayed blog post or a stuck landing page usually has a launch date attached to it.

This article covers the core Kanban metrics worth tracking for a marketing team, the marketing-specific time metrics that matter most, and how to measure them directly in Jira.

🎯 Why marketing teams need flow metrics

A Kanban board makes work visible — you can see what's in progress and what's stuck. But a board alone doesn't tell you why things are slow, or whether they're getting slower.

Marketing work is a good fit for Kanban precisely because it's continuous and deadline-driven: requests arrive from many directions, priorities shift, and several assets move through the same pipeline at once. That also means marketing teams run into the classic flow problems:

• Work piling up in review or approval while stakeholders are busy
• Assets aging quietly in a column because nobody owns the next step
• Too many campaigns in progress at once, so everything moves slowly
• No clear way to explain to leadership why a launch slipped

Metrics turn "it feels slow lately" into something specific you can investigate and report on.

📊 The 4 core Kanban metrics, in marketing terms

These four are the foundation of any Kanban measurement, whether you're shipping code or campaigns.

Metric	What it measures	Marketing example
Lead Time	Total time from request to delivery	From "content request submitted" to "published"
Cycle Time	Time from when work starts to done	From "writing started" to "published"
Throughput	Items completed in a period	Assets published per week or month
Work in Progress (WIP)	Items actively being worked at once	Campaigns or pieces open right now

Lead Time measures the full duration — from when a request enters the workflow to when it's published — so it includes the time an item waits in the backlog before anyone picks it up. Cycle Time measures only the active part, from the moment work actually starts to done. Because Lead Time includes that pre-start wait and Cycle Time doesn't, a big gap between the two usually means items are sitting in the queue before work begins — not that the team executes slowly. 

Throughput tells you your delivery rate. A steady throughput is easier to plan campaigns around than a number that swings wildly month to month.

WIP is the one marketing teams most often underestimate. Every extra campaign in flight adds context-switching. Watching WIP helps you see when the team is overloaded before deadlines start slipping.

🔍 The metrics that matter most for marketing

The four above are universal, but marketing pipelines have their own recurring pain points — and they nearly always live between two specific statuses. These are the metrics that usually tell you the most:

• Time in Review — from "Ready for Review" to "Approved." Review is the classic marketing bottleneck.
• Approval Time — from "Submitted for Approval" to "Approved," especially when legal, brand, or leadership sign-off is involved.
• Design turnaround — from "Handed to Design" to "Design Done."
• Waiting-on-stakeholder time — time spent parked in a "Waiting" status while someone outside the team responds.
• Time in Status — how long work sits in any single stage, so you can spot where it stalls.

The reason these matter: when a launch slips, the delay is rarely spread evenly across the whole process. It's usually concentrated in one or two stages — often a review or approval step that depends on someone outside the marketing team. Measuring the time between the exact statuses where handoffs happen is what makes the cause visible.

⚙️ How to measure this in Jira

Jira's built-in boards show flow, but they don't calculate how long work spends between the statuses you care about. This is where Time Metrics Tracker | Time Between Statuses fits in.

The core idea is simple: you create a time metric between any two statuses in your workflow. For a marketing pipeline, that means you can define exactly the metrics above — not just generic Cycle Time.

When you set up a metric, you can:

• Choose the start and end statuses — for example, "Ready for Review" → "Approved" to measure review time.
• Exclude statuses that shouldn't count — for example, don't count time spent in "Waiting for Legal" or "Waiting for Stakeholder," so the metric reflects active work, not idle waiting.
• Apply a work schedule — count business hours (Mon–Fri) only, so a request submitted Friday evening isn't penalized for the weekend.
• Set warning and critical limits — so you can see when an asset exceeds the time you'd normally expect for a stage.

Once a metric exists, it flows into reports, charts, and Jira dashboard gadgets. The app calculates the metric from your status history; gadgets like the Time Metric Trend Gadget, Status Contribution Chart Gadget, and Agile Metrics Gadget help you monitor it and report it on a dashboard without exporting anything to a spreadsheet.

🩺 Reviewing workflow health in one view with Flow Insights

Individual metrics answer specific questions. But when a metric gets worse — say Review Time jumps this month — one number isn't enough. You need to see the trend, where the time goes, and which pieces are creating the risk.

Flow Insights brings that together in one connected view for a selected metric, project, and period. It sits on the pages you already use to review work items, so you can analyze flow without leaving the report.

The summary panel shows KPI cards for the selected metric, including its Trend (improving, stable, or worsening), the Median and P85 duration, how many work items completed the metric, and the total tracked time. From there, the full view opens four charts that answer the follow-up questions:

• Trend chart — is the metric drifting up or down over the period, and is it becoming less predictable?
• Status Contribution chart — which workflow stage is accumulating the most time? (For marketing, this is often where you confirm the delay is in review or approval.)
• Work in Progress chart — is active work building up, and are items aging before they're finished?
• Scatter plot — are delays spread across many assets, or concentrated in a few outliers?

These charts let you drill down into the specific Jira issues behind a data point, so you can move from "review is slow this month" to "these three assets are the ones that stalled." Flow Insights doesn't replace your detailed work items report — it adds a flow-health layer on top of it, while the full issue data stays available for deeper analysis.

✅ A few tips

• Measure the handoffs, not just start-to-finish. The stage-level metrics (review, approval, design) usually reveal more than a single Cycle Time number.
• Decide what "waiting" means. Excluding stakeholder-waiting statuses keeps your team's metrics honest and separates "we're slow" from "we're blocked."
• Watch WIP alongside speed. Rising WIP is often the early signal that explains why Cycle Time creeps up later.
• Keep clean status transitions. Metrics are only as good as the workflow behind them — vague or skipped statuses make the data harder to trust.

Marketing teams already generate all the flow data they need just by working in Jira. The step most teams skip is turning that history into metrics that name the real bottleneck.

Try it on your own workflow

You don't need to overhaul your process to start. Pick the one stage you suspect is slow — usually review or approval — create a metric between those two statuses, and watch it for a couple of weeks. That single number is often enough to turn a vague "we're behind" into a clear conversation about where the time actually goes.

You can set this up on your own Jira and see your real numbers with a free trial of Time Metrics Tracker | Time Between Statuses.

👉 Start your free trial on the Atlassian Marketplace

[Yana Misiura_BrizoIT]

This was super useful! I especially liked the examples for marketing teams

[Anastasiia Maliei SaaSJet]

@Yana Misiura_BrizoIT I'm really glad this article was helpful!