Kevin asks, “How do we standardize metrics and measurement, especially when different parts of the company do things differently?”
Great and very common question. The answer is, unsurprisingly, a framework:
- Goal alignment
- Exploratory data analysis
- Model creation
- Model validation
- Model deployment
- Adoption, training, and compliance
- Measurement of compliance
- Refinement and improvement
If this sounds familiar, this is also the process for bringing machine learning models to fruition as well.
Can’t see anything? Watch it on YouTube here.
Listen to the audio here:
- Got a question for You Ask, I’ll Answer? Submit it here!
- Subscribe to my weekly newsletter for more useful marketing tips.
- Find older episodes of You Ask, I Answer on my YouTube channel.
- Need help with your company’s data and analytics? Let me know!
What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for watching the video.
In today’s episode, Kevin asks, How do we standardized metrics and measurement across the organization special in different parts of the company do things differently? different business units have their own style of doing stuff? It’s a great and very common question, especially in larger companies and enterprises. The answer to
this question is not surprising. It’s going to be a framework, it’s going to be a model for building a model, kind of a meta model, if you will. So let’s
look at this on fact, to bring this up here.
This is the process for putting together a an enterprise analytics system or standardization or framework or whatever you want to call it. It should look familiar, by the way, because this is also the model that we use for things like machine learning, and for data systems, and bi and all the technology that we want to deploy in a way that max Mises adoption and compliance.
So let’s go through this for the first part is goal alignment, what goals are we trying to align our system with?
What are the business goals that everything has to roll back up to, if we don’t have that clearly defined and written out, nothing’s going to work here, because everyone’s going to keep trying to address their own specific goals, instead of the big picture goals, we need to make sure that we have those goals documented, and that we have the process for the obtain them documented, and frankly, the governance who’s in charge of these different goals, having that document to because if you don’t have those stakeholders clearly mapped out, you’re going to create something that nobody’s gonna want. So that is super important. That’s why this comes first. Second, is exploratory data analysis, given that we understand the goals, what are all the systems that feed into those goals, there’s a little worksheet that I typically use that has, you know, the KPIs, people normally measure with the business goals, and you try and connect the dots to see how things get put together. But exploratory data analysis is super important. It requires statistics and data analytics tools, it may require some machine learning, it may not, but it requires you to take all the, the the KPIs and metrics that you’ve got, and essentially do mass statistical analysis to figure out what of all this data that we collect actually has a mathematical relationship with the outcomes we care about. So very, very important. The third step is creating that framework, once you have the math proven out, and you create a framework and say, Okay, these are the things that are important. So on the marketing side, for example, very silly example, let’s say that you’ve gone and, and connect to all your social and search and email and referral traffic, and all that stuff. And, and it turns out that email sent on Thursdays plus tweets containing emoji are the thing Great, now, you create a model for that saying, hey, these are the things that we need to do. And when we validate the model we tested, we will want to prove that this is the case. And so what you go through and, and you you document out all the things that that mathematically have relationship. And that brings us to the next stage, which is validation. So now that we’ve got this model, now we test it and we say, okay, hey, Social Media Manager, tweet more emoji, and see what happens, right? Hey, email team sent two emails on Thursday instead of one, or make sure you send an email every Thursday instead of every other Thursday with the
intent to prove causality. One of the the biggest traps and the oldest traps in analytics is making the assumption the correlation is causality. That’s not the case, you have to prove it through the scientific method. That’s what the validation stages validation is, essentially using the scientific method to rigorously prove that the data you’ve collected is causal in nature. And, and can we translate it as such, one, you’ve validated your measurement model, your metrics model, then you roll it out, that’s where we get to deployment. And that means taking all the systems that you’ve engineered up to this point, and transforming them into production systems, to taking them out of test environments, making sure that they are secure, which is a really big deal, making sure that they are idiot proof, I guess,
but require the minimum amount of hand holding, so that the system can scale up as fast as possible. And deployment can take a long time, depending on how complex the system you’ve built, it can take months, possibly even years, because you need to do it right, you need to make sure that everybody who gets it can adopt it and work with it. The next second stage is adoption. This is adoption of the system, which means training, which means development, which means compliance. Just like if you were rolling out of medication at a hospital, you’d want to make sure that your your users were complying with it, they were actually using it. So making sure that you’ve got this framework in place, and that you’re measuring the next stage is measuring that compliance, what are people doing are people using system I mean, not using the system if you if that’s not the case, then gland going back to the beginning with that goal alignment, that governance process is when you identified all the people who have a stake in this thing, this when you’re at the adoption and measuring phases, you have to go back and check on those people and say, Are you using the system, why you’re not using system if you’re not what needs to be improved if you are using it, and what are the consequences of a failure to comply. So if it’s, you know, if there are people in the company who are just not doing the thing, even though they’ve received a directive from high end up, again, back to the goal line, but section, you’ve got that executive buy in you, you’ve you’ve established that. And so now we get to the adoption phase, it’s like, you got to do the thing, because everybody who signed on to this project said they were going to do the thing. So do the thing.
If in the measurement phase, you find that people are not doing the thing, they’re not using the model, they’re not using the systems with the software, that’s when you go into the improvement face. And the improvement face doesn’t necessarily mean improvement of the model and improvement, maybe improving the people improving the processes that the model needs in order to be functional, because chances are hopeful you worked out a good number of the bugs in the creation and validation stage. The improvement maybe improving the uptake of the model and its participation. There will of course, be things like software changes, software updates, as technologies change, that improvement and refinement process is always ongoing, and then brings us full circle back to goal alignment. So you’ve developed Do you’ve deployed this thing, it’s in place,
it is proven it is functional people are using it great is is it delivering the impact that you want? If not, we go back to gold alignment. Okay, was there something that got missed the company’s business change, did technology change so substantially, that all the efforts to that point have been nullified again, that’s a real risk when you’re talking to three four year deployments for massive massive systems. So anybody who’s been through an ER p system deployment, how much fun it is and how quickly it doesn’t go and, and you can see why the cycle has to be iterative and ongoing. If you want to kick it up a notch if you can kick it up a notch because your company culture supports it, take a look at this model and then transform it with agile using agile methodology instead of one big waterfall process. How do you do this in an iterative fashion that allows you to upgrade your standardization upgrade your metrics, measurement and model on a rapid frequent basis. You need to have it in place first, you can’t sort of iterate through the plane. So trying to fly at least the first pass but after that, how do you upgrade those efforts to using an agile model if your company culture supports it? So great question. common question, complex question. This is something that’s going to take a very long time it will not be something that is easy or overnight even for the smallest companies because again, that exploration that model creation that model validation using analytics using data science using machine learning, not something that is an overnight thing despite our best wishes. So great question. As always, please subscribe to the YouTube channel in the newsletter and I’ll talk to you soon. Take care
if you want help with your company’s data and analytics. Visit Trust Insights calm today and let us know how we can help you
You might also enjoy:
- How I Think About NFTs
- Marketing Data Science: Introduction to Data Blending
- The Basic Truth of Mental Health
- Understand the Meaning of Metrics
- Best Practices for Public Speaking Pages
Want to read more like this from Christopher Penn? Get updates here:
Get your copy of AI For Marketers