How to Build a Metrics Culture That Drives Better Marketing Decisions

Episode Transcript

How many dashboards does your team have right now? Not counting the ones you built for that one campaign and never looked at again. Not counting the ones your agency sends over that nobody opens. The real number — the ones somebody actually checks.

Even without counting those random ones nobody looks at, I'll bet it's more than you'd like. And I'll bet that having all of them isn't making your decision-making and prioritization processes any easier.

That's the thing nobody tells you about marketing data. You can be drowning in it and still be starving. You can have a wall of green and red numbers and still walk into a planning meeting with no real idea what to do next. More measurement doesn't automatically make you more informed. It might just make you overwhelmed.

So here's what I want to do today. Data and metrics is one of the core pillars of the Agile Marketing Operating System — it's a big chunk of the "What" — and it is also, in my experience, the pillar teams are the most confused about. They think the problem is that they don't have enough data. It's almost never that. The problem is they don't have a rhythm or a process for using the data they already have.

That's the whole episode, really. A healthy metrics culture isn't about collecting more. It's about building the operating rhythm that turns numbers into decisions — and it turns out Agile is one of the best ways to build exactly that rhythm. Let me show you what I mean.

---

Welcome to The Agile Marketing Edge, the first podcast dedicated to turning Agile theory into real-world marketing breakthroughs. I'm Andrea Fryrear, CEO of AgileSherpas and your guide on this climb to smarter, faster, outcome-driven marketing. Every week we dig into the what, who, and how behind Agile marketing — from building high-velocity workflows and cutting waste, to measuring what actually matters and scaling success across teams.

Today we're staying right on that phrase — "measuring what actually matters." Because the data pillar of the operating system is where a lot of teams think they're doing great and are actually doing the least useful thing possible: measuring constantly and deciding rarely. We're going to look at what a real metrics culture looks like, why most teams don't have one, and how Agile rhythms close the gap between having data and using it.

---

Let me name the actual dysfunction, because "we need better data" is the wrong diagnosis for almost every team I've worked with.

Here's how we find this out: we ask a few simple questions in our assessment and then watch as the data category quietly gets the lowest score of any of the nine we measure. Well, these days it comes in ahead of AI readiness and benefit realization — but still really low.

Here are the questions, which people rate on a scale of 1 to 5:

- I have strong confidence in the accuracy of the marketing data we collect.
- Data is readily available and easily accessible when my team needs it.
- We review and act on data often so we stay current with experiments and their performance.
- We use data to inform the planning and execution of marketing activities.

Not that hard, right? But average scores on these questions routinely come in two or more points lower than anything else.

The dysfunction is that data and decisions live in two separate systems. The data lives in dashboards. The decisions get made in meetings — often the annual plan, sometimes a quarterly review — and in between those meetings, nobody is systematically looking at what the numbers are telling them and changing course. The dashboard updates in real time. The plan updates once a year. That gap is where all the pain lives.

And it's not just one-off client assessments that show this. In this year's State of Agile Marketing Report, we asked 500 people how often their teams update or adjust their plans. Among Agile marketers, 89% do it at least monthly. Among non-Agile marketers, that number drops to 66%. Flip it around and it's even sharper: a third of non-Agile teams — 34% — update their plans quarterly or less often.

That means a third of teams are looking at real-time data and adjusting their actual plan of record four times a year or fewer. The data is fast. The response is slow. That's not a metrics problem in the sense of "we need a better dashboard." It's a cadence problem. The measurement is happening. The metabolizing of it isn't.

So the first shift I want you to make is to stop asking "do we have the right metrics?" and start asking "how often does a metric actually change what we do?" If the honest answer is "basically once a year," no new dashboard is going to fix that — not even one that updates automatically thanks to your LLM of choice. Because you don't have a data problem. You have a rhythm problem.

---

Now, the usual advice when someone says "we're drowning in dashboards" is: cut the vanity metrics. Focus on the north star. And there's real wisdom in that — the folks at Amplitude and Reforge have done great work here. The north star idea is a good one: pick the single leading indicator that best captures the value your customer actually gets, and make sure it isn't a vanity number. The test Amplitude uses is clean — can this metric go up while the business gets worse? If yes, it's vanity.

That's a genuinely useful lens. Here's where I want to complicate it, though, because I think most marketing teams import the north star framework and still don't fix anything.

Picking the right metric is a one-time act of clarity. Using it is a repeated act of discipline. And teams love the first part — the offsite, the whiteboard, the "words before numbers" exercise where you finally name the one metric that matters. It feels like progress. Then everyone goes back to their desks and the north star gets a nice tile on a dashboard next to forty vanity tiles, and nothing about the actual operating rhythm changed.

Here's my contrarian take: vanity metrics don't proliferate because teams don't know which numbers matter. They proliferate because there's no regular forum where you have to use a number to make a call. When there's no cadence forcing a decision, every metric is equally optional — so you keep all of them, just in case. The dashboard sprawl isn't ignorance. It's what happens when measurement has no consequence.

Which means for a lot of teams the fix isn't primarily "choose better metrics." It's "build the recurring moment where a metric has to earn its keep by informing a decision." Get the cadence right and the vanity metrics starve on their own, because nobody's using them for anything. Get the cadence wrong and the cleanest north star framework in the world just becomes one more tile you don't act on.

---

So if the problem is cadence, let's talk about what Agile actually installs — because this is the part that's mechanistic, not motivational.

Agile marketing isn't a vibe. It's a set of recurring events that each have a specific job, and two of them are metrics events whether you call them that or not. The iteration or sprint review is where you look at what you shipped and how it performed. The retrospective is where you look at how the team worked and what to change. Both of them are, functionally, forced appointments with your data. You cannot skip them without skipping them on purpose. That's the mechanism: the rhythm removes the option of not looking.

And you can see the downstream effect in the data. It's not just that Agile teams adjust plans more often — we covered that. It's what that frequent adjustment does to their confidence in where their effort is going. We asked how confident people were that their planning habits keep them focused on the most important work. Among Agile marketers, 82% said extremely or very confident. Among non-Agile marketers, it was 59%. That's a 23-point gap in something incredibly valuable — the felt sense that your effort is landing where it should.

Notice what that number really is. It's not "we have more data." Both groups have plenty of data. It's "we trust that our data is steering us." That trust doesn't come from the dashboard. It comes from the fact that every couple of weeks, the data got looked at, discussed, and acted on. Confidence is a byproduct of cadence. You can't dashboard your way to it. You have to metabolize your way to it, on a schedule.

There's also a fear this addresses head-on. A lot of leaders worry that reacting to data constantly means chaos — that if you're adjusting every couple of weeks, you'll just spin. The report answers that directly. When we asked whether teams could stay organized when priorities change, every single Agile marketer we surveyed said they were at least somewhat confident they could. Not a majority — all of them. The rhythm is what makes frequent, data-driven change feel organized instead of frantic, because it's happening inside a structure, not on top of one.

---

*Quick pause, because this is exactly the kind of thing we teach people to actually operationalize — not just nod along to.*

*If you want to take what we're talking about today and build it into how your team really works, come check out The Ropes. It's our online learning platform, and we've just ungated about $1,600 worth of material — free. Real training on the rhythms and practices that turn this stuff from a good idea on a podcast into something your team does every sprint. There's also a quarterly certification workshop if you want to go deeper and come out with a credential that makes the case for you internally.*

*Head to theropes.agilesherpas.com. Go poke around. It's free, it's substantial, and it's built for exactly the marketer who's listening to this thinking "okay, but how do I actually do this on Monday?" That's the whole point of The Ropes.*

---

Here's a piece of the data pillar that dashboards are actively bad at, and it's the one I'd most want you to fix.

When we asked how often teams use customer insights or data to guide what they work on, 87% of Agile marketers said they do it often — versus 72% of non-Agile marketers. And I want to be precise about why that gap matters, because it's easy to file "use customer insight" under generic best-practice advice.

Most of what lives on a marketing dashboard is behavioral exhaust — clicks, opens, sessions, conversions. It tells you what happened. It is almost silent on why. And "why" is the thing that actually lets you make a good next decision. A conversion rate dropping tells you something is wrong. It does not tell you that your new landing page is confusing the exact segment you were trying to win. Only talking to, or listening to, actual customers tells you that.

This is the north star lesson turned inside out. The reason a good north star metric is a leading indicator is that it captures customer value — not internal activity. But most teams try to infer customer value entirely from quantitative exhaust, because that's what shows up on a dashboard and is relatively easy to get.

Customer insight is the input that keeps your metrics honest — it's how you catch a number that's going up while the customer experience is quietly getting worse. That's the vanity-metric trap the product folks warn about, and qualitative customer insight is the antidote to it.

Agile teams do this more not because they're universally more curious people. It's the rhythm again. When you're reviewing work every couple of weeks and planning the next slice, "what are we hearing from customers" becomes a live input to a real decision, not a research project that gets commissioned once and shelved. The cadence pulls the customer voice into the room on a regular schedule. So build customer insight into your review rhythm as a standing input — not a special occasion. Every time: what did we learn from customers this iteration, and what does it change?

*Side note: if you want to go deeper on customer centricity in Agile marketing, go back and check out episode 32.*

---

Let me pull this all together into the thing I actually want you to walk away believing, because it reframes what "good at metrics" even means.

Most teams, if you ask "are you data-driven," will point at their instrumentation — the dashboards, the attribution model, the tooling. That's evidence of measurement. It is not evidence of a metrics culture. Those are different things, and confusing them is how you end up with a very expensive analytics stack and a team that still plans on gut feel, or on whatever the highest-ranking executive said last week.

A metrics culture is a behavioral property, not a technical one. You can see it in the answers to three questions, and none of them are about tools: How often does a metric change a decision here? When the numbers say something uncomfortable, does the plan actually move? And is the customer's actual voice in the room when we decide what to build next?

That's the reframe. And it maps cleanly onto the operating system. This is the "What" pillar — what work gets chosen and measured — but it only comes alive through the "How," through the day-to-day practices and the cadence. The data pillar and the practices pillar aren't separate. Your metrics culture is only ever as good as the rhythm you run it on. A team with mediocre dashboards and a disciplined biweekly loop will out-decide a team with a beautiful analytics stack and no cadence every single time. Every time. Hit your back-ten-seconds button on that one if you need to, because it's the argument of the whole episode: the rhythm beats the instrumentation.

---

So here's what to actually do this week. No need for a data transformation. Just a few concrete moves.

**One:** Count your dashboards, then count your decisions. Literally — list every dashboard or report your team maintains, then write next to it the last decision that dashboard actually changed. The blank rows are your vanity metrics, and now you know which ones to stop maintaining. Start there, because you'll free up time immediately.

**Two:** Install one recurring metrics appointment. If you already run iteration reviews, good — make "what did the numbers and the customers tell us, and what does it change?" an explicit, non-skippable part of it. If you don't run reviews yet, that's your first Agile practice to adopt, and it's the highest-leverage one for this problem.

**Three:** Name one leading indicator — and give it a decision, not just a tile. Do the north star exercise if you want. But the test isn't whether you picked a good metric. The test is whether, at your next review, that metric is required to inform an actual call. A metric with no decision attached is just decoration.

**Four:** Put the customer's voice on the standing agenda. One question, every iteration: what did we hear from customers, and what does it change? That's it. That's the input most dashboards can't give you, and it's the one that keeps every other number honest.

Do those four and you won't have more data. You'll have less — and you'll finally be using it. That's a metrics culture.

---

Until next time, I'm Andrea Fryrear. And remember: the struggle is real. But so is Agile marketing.