#194 [Radar Recap] Scaling Data ROI: Driving Analytics Adoption Within Your Organization with Laura Gent Felker, Omar Khawaja and Tiffany Perkins-Munn

Hi, I'm Maggie, VP of Curriculum at datacamp. And I know firsthand how overwhelming it can be to keep up with the rapid changes in data and AI. But staying ahead doesn't have to be hard. That's why our curriculum team has curated the best learning content to help you and your team stay ahead, covering everything from data and AI literacy for busy executives to cutting edge generative AI for developers, and everything in between. Whether you're upskilling yourself or your team, we make learning practical, engaging and flexible.

It just works.

Power your data and AI transformation journey on datacamp.com.

One of the big problems with making use of data is that you have to spend money on tools and employees. And that means that at some point, someone in management is going to want to see a return on investment for spending. So in this session, we're going to look at what sort of a return on investment you can expect, and we're going to discuss the changes you need to make to your organizational processes and your culture in order to achieve those returns. And we've got three fantastic guests to guide you through the process. So, first up is Laura Gent Volker. She's the go to market analytics lead at MongoDB and she's previously the Senior Director of Insights and Scalability at Salesforce. Secondly, we have Omar Khawaja. He's their chief Data and Analytics officer and also global Head of Data and analytics at Givaudan, and previously he was the head of Business Intelligence at Roche Diagnostics. And he's also a founding member of the data product leadership community. And last but not least, we have Tiffany Perkins Munchkin. She's the Managing Director and head of Data and Analytics for marketing at JPMorgan Chase and was previously the Managing Director and global Head of Research for analytics and Data at blackrock. So, yeah, welcome all three of you. Now, all three of our guests have got a lot of experience in building and running data teams that are tightly integrated with business. And frankly, between them, they've solved all the data team problems that you haven't even thought of yet. So we only bring you the best of the best here at Radar. So let's hear what they have to say. Now, to begin with, since we are talking about return on investment, it'd be nice to know what that actually means. So just in practice, what does return on investment mean for data initiatives? Tiffany, do you want to leave this one?

Yeah, sure. So, first of all, thank you, Richie and Radar for having us. This is going to be a really exciting discussion and I Know, I am, I'm assuming Laura and Omar as well are really excited to be here. So just in really simplistic terms, when I think about return on investment, it's really about how do you use data and analytics to achieve like a specific business goal? Right. And I think often in firms that I've worked in anyway, people get caught up in value, meaning dollars or revenue. And yes, that's important because obviously revenue growth is a key sort of business goal related to, you know, how are you acquiring customers, are there cross selling opportunities, et cetera. But there are lots of other value metrics that we also want to take into consideration when we think about business goals. So are we reducing costs? Are there operational efficiencies? Are we optimizing processes? Are we allocating resources appropriately? There's also customer experience metrics. Are our customers happy with us? Are they willing to recommend us to others, or are we retaining them? Are they loyal? And the one that I think we forget about a lot is actually are we making ourselves smarter internally? Like, are we making quality decisions? Are we making those decisions faster? Are we building business intelligence tools to help us make more accurate speed to market kind of decisions? And then in my space, just to give an example, one of the things that really matters in terms of value to a specific business goal is risk management. Are we detecting fraud? You know, we're in a space where privacy matters. There are lots of fraud issues out there. Are we using data and analytics to mitigate those risks? Are we detecting fraud? Are we ensuring that we are compliant with regulations? How are we actually using algorithms, predictive models, et cetera, to protect our customers assets, to mitigate financial losses, and basically to build that trust with the consumer. So when we, when I talk about ROI and value, I'm talking along sort of that continuum of metrics that matter.

I think it's really important that it's not always going to be directly tieable back to the revenue of your company, but actually there might be some department specific metric that you're working towards on that. Excellent. Yeah, really comprehensive set of metrics there. I like it. All right, so beyond simply buying tools at a high level, what do organizations need to do to improve their data capabilities? Laura, since you work for a tool vendor, I'm going to get you to talk about what do you do beyond tools. Do you want to go first on this one?

Yeah, absolutely. Beyond tools, I think process is one of the most imperative elements of data. So really making sure that we identify end to end on what I call the data supply chain to identify where are the bottlenecks. So we are able to get a very fast and efficient set of data and metrics so we can measure that quickly. Like Tiffany is talking about using data beyond tools. If you don't have the adequate process and then the adequate trained up system skills of the future for people not just in the data and analytics org but through and through across the company to enhance the data literacy, I think you could have the best tool in the world. But if you have bad data, bad process and you don't have people that are data literate, it's not going to be successful. Of course we always want to leverage the best in class tools but there's those two other key pillars that are really important in it.

Excellent. Yeah, like you got the right supporting infrastructure. Omar, do you have anything to add to that?

Yes, Racheer, thanks. And please first allow me to show my appreciation for inviting us and glad to be here today sharing this panel discussion with Laura and Tiffany. Let me complete the triangle right. Laura talked about processes, I'll talk about people. People in my view are the key pillar of any data initiative. They make and break everything. And when it comes to people you can range from top executive committees of the company in different shapes and forms. They can be the board of the company, they can be the executive leadership team of the company and drilling down all the way to the people on the front lines, on the frontline managers, the sales teams, the people on the shop floors. And these people have job to do, they know what they are for in the company, they come to the office, they do their work. And for data leaders to be successful it's important to understand what these people jobs are, these Personas are, what their needs are before any tool discussion can start. I mean process examples that Laura mentioned are so important in this. Do these people receive the insights they need or or not? What's in it for them to use the tool and what kind of tool they need? Maybe somebody is very happy with a mobile phone in a company and another set of Personas may not even have a company mobile phone. And this can be device dependent. This can be the area they work. You might have a very fancy tool that works on a cloud and the person works underground where there is no Internet connectivity. So how that person needs to receive the insights in that area, the tool comes always later. It's about the people, it's about the process. The business outcomes that Tiffany mentioned are so important. So those are just my two cents on that.

Absolutely there with you that people Side of things are very important. It seems like non technical people are then going to need some kind of data skills, but there's nothing to be quite daunting for them. So do you have any advice on how to improve the data skills for these workers? Maybe. Omar, do you want to go again? We'll do reverse order this time.

And how about I reverse the order of the question as well? Richie, it's not about the business people only learning tools and the tech. I think with the, with this modern age, people are becoming tech savvy. The traditional data skills are no longer locked in the IT department or only in the data department. We have more and more citizen data roles evolving. While that is happening. For each of those Personas, there should be a targeted data literacy program, AI analytics literacy program as well. But I want us to step back. I want us that teams that are more tech savvy, the teams that are more data savvy, they also need to understand the business as well to make an impact. An organization is there for the purpose. They have their vision, their mission. They are there to achieve that target no matter which industry they are in. And the data teams needs to understand in which business they operate. How does the business value chain works, who are the key stakeholders and what decisions they need to make. We already can see that there is a nice balance. It's not just one way education about tools and technologies and making people tech savvy. I think that's not that difficult part. It's about understanding the business and meeting where your customers are. That will make a lot of difference.

Interesting. So you're going to have some technical skills and some business skills and hopefully that's going to help people communicate. All right, Tiffany, do you want to expand on this? Like, do you have any advice on how you can improve communication between like your technical employees and your business employees or other non technical?

Yeah, so yes. Thank you, Richie. So I can't stress this enough, but I think this is so critically important and it's really storytelling, storytelling, Storytelling, storytelling. I know it sounds a little weird in the data space.

Plus one on that.

Right. But people have been talking about it more. But it's really about like training on storytelling techniques to help the technical teams convey insights in a compelling and relatable manner. Right. To non technical but super smart audiences. It's not about dumbing down information, it's just about learning how to tell the story. And I know that we, at least in a lot of the firms I've worked in, people get caught up in the Jargon, the acronyms. And by the time they explain what they're doing, everybody's like, wait, what just happened? What are they doing? Who, who do I need to talk to? Like, no one knows. So some combination by the way of this storytelling exercise and then collaborative workshops where you have these brainstorming sessions that encourage open dialogue, idea exchange, problem solving with the storytelling, I think really helps to bring together the technical and the non technical. And it actually teaches everyone how to speak in very simplistic, easy to digest language that anyone can understand.

Love that.

I wanted to add to that. You know what Tiffany was talking about is we all have to be speaking the same language and know the language of our stakeholders end to end. So as a leader in the analytics organization, I pivot between data engineers, data scientists, social media, super duper technical people to our business stakeholders that are in sales and other go to market people. And I've talked to my team about this. We have to be able to pivot both languages. You can't be bringing up a python script to a sales leader, but you need to be able to use that python script to tell a story. So meet them where they are. So I can't agree more and more on that. Just wanted to add to that, Richie.

I like that you're both talking about storytelling because we had a session on storytelling earlier today. So for anyone who missed that, you're going to have to catch up on the recording. For anyone who attended, I'm hoping you're aligned on this, that storytelling is a really good idea in the data world. All right, so from storytelling, I think we can talk more generally about culture and what constitutes like a good data culture. So in order to change how you work with data, you're going to have to change the data culture of your organization. What are some good goals around this? Like what should you be aiming for? If you say, okay, we want to change the culture to get better at data. Do you want to talk us through this?

I'll give it a go, Richie. And then Laura and Tiffany, please feel join in. So there are two ways to looking at it, right? This is one of the misused terms a lot data driven culture, Data driven culture. And then we recently also come up with is your company data driven or is AI driven or data informed and all of these things out there. I think companies have a culture without data, without AI. This is how people live, tell stories, they talk to each other, they react to each other, they work with each other. That's a company culture existing already in any company where does data and AI play a role in that? That's important thing to understand. That's an important thing to embed and infuse in that. Otherwise we will end up oh, you have a finance culture or you have a HR culture or is there a supply chain culture? And then you know, we have a culture silo maybe. So as a data leader, I think it's important to go to that point, understand how the company is operating, what is the company's culture and infuse this data thinking over there. This means understanding the people a lot. This means building upon earlier storytelling. Comment. How can I tell the story to a salesperson versus to an executive, versus to a engineer in a, in a factory for example, or versus to a planner? Sitting in supply chain will be very different and you need to really make a point that what's in it for them. So as a leader who's talking about data analytics, AI, they need to really understand how the people will use their data and analytics and insights. For instance, can they do their job better? For example, if they use the data in their work, can they get insights in a very different way? Rather than reviewing 20 reports and then doing something and then doing something with it. This is how you can understand that. I think that's one thing. The second aspect is towards the data team as well. I think there is a high need to take a different approach from what we have been doing in past. We need to show a little bit more love towards how we treat data instead of protecting it and shackling it. How can we unlock the potential of the data? How can we give it the same love to improve data quality, to maintain the data pipelines? It's free freshness, its completeness so that people can make informed decisions. Right? So this aspect is very good.

This is hashtag free the data, free the data.

I love it. I love it. Tiffany?

Yes, Excellent.

I always called it being a data shopkeeper versus a data gatekeeper because you want to keep your shop nice and clean. You want to be shopping at the best in class place where you feel good to go to, but you want to open your doors to other other people. Right? And I think that's going to help unlock a data culture to empower the user. But also having those right governance, right. You don't want to go into a messy shop. You're just going to be really overwhelmed in that kind of situation. But if you go and it's nice and clean and you can find your stuff real quick, you're going to feel good when you Leave and you check out. So that is one analogy as Omar was talking about it and Tiffany said, free the data. I was like, keep that data shop nice and clean.

All right, so we got lots of great ideas unpacked there. I think, Omar, your first idea was start with your business values and make sure the data is aligning to those and supporting whatever your business goals are. Tiffany, free the data. And then, Laura, make sure that your data, you're governing it well. All right, so one thing I'd like to talk about is who are the people that are involved in this? So you say, okay, we're going to change our data culture. We're going to get better at working with data. Like which teams need to be involved, which roles, what do they actually do? Yeah, go on, Tiffany, do you want to talk us through, like, what's the process here? Like, who needs to do what?

Yeah, so I think that this can happen in one of two ways, right? It's either, and it depends on the culture of the organization. So you have to sort of be aware of that. But it either happens from the top down where the executive leadership says, this is a change we're making, or it happens, and I've been in organizations where it's happened both ways, or it happens in a grassroots way where there's groundswell, there's interest, and it kind of bubbles up to executive leadership. Regardless of the path it takes, though, I think the same teams or groups of people need to get involved to make the change. And those people are the executive team because you need the executives at the top to champion the initiatives, to set the tone for the data culture transformation and obviously to allocate the resources. So let's not forget that then you also need the data and analytics teams, obviously, right? They, you need to empower them. All of the scientists, the analysts, the engineers, they are the ones who are going to be able to really drive data literacy. What are the best practices? How do we innovate across the organization in this space? And then obviously the partners are the business units and operations. You have to get them to integrate the data into the daily operations, into the decision making processes and the performance metrics. Human resources has a key role because they are going to develop the data literacy programs, the workshops, the resources for employees across the different levels. And then I think really good organizations have these change agents, right? The people who are, who can promote the data culture, who can share the best practices, who can facilitate the knowledge sharing. The. Sometimes there are transformation offices or change management teams, or sometimes it's the design team that does that, pulls that together. But regardless, I think those five roles or those five teams are really critical in making a lasting long term data culture change.

Okay. Lots and lots of teams involved there. So we've got executives, we've got data practitioners, HR business functions, all sorts of. Yeah, most of the business can be involved in this.

I'm curious, can I just say, Richie, really quickly that when you, when people. I think one problem that a lot of organizations face is that they try to do it with one or two of those teams. Like the data team tries to affect a change that the executive leadership hasn't adopted. Or the businesses want to do something, but they can't seem to figure out how to make it a broad offering because HR isn't involved. Right. So every team has a role and I think that's an important takeaway for people to consider when they're thinking about modifying data culture.

All right, so it's going to have to end up being pretty broad scale with lots of people involved. I'm wondering, how do you get started? Do you have to mobilize the whole business at once or there are a few people who you can begin with? Laura, do you want to take this?

Sure. I mean, I start with a small cohort of people. Right. And I can't agree more with Tiffany making sure the right infrastructure essentially is in place to be able to mobilize. So you want that executive team through and through to continue to keep beating the drum. Not just once, not just one all hands. But we want to keep talking about the data culture at the organization. But I always try to find a cohort of advocates within the business to kind of start with and then they actually will speak the best to say, hey, this is the best thing. This is the outputs of being a data informed culture. And these are the particular projects where it has helped me and why and what's the art of possibility? Because not everybody knows everything that we can do across data and we don't have to do data science at day one. Right. Nor would I recommend that. But with that said, like a lot of people might not even know what's possible in their data. So I've always found that advocacy route and finding a small cohort of people that want to be involved and that want to help make that change and be that change maker. And then people start really, really coming along with that.

All right, so you get the people who want to be involved involved first and then hopefully things can grow from there.

Then that snowball. It's like, kind of like going down the mountain. I live in Colorado, so I'm all about snow and, and it's just a keep. The ball keeps getting bigger as you go down the mountain. Right. And so I really believe that if you get a few strategic partners and you really market it accordingly, the people that might not have been as like excited about a data informed culture going towards more data organization, they'll then say, oh, that's in it for me too.

We call those people in the business friendlies. Like, go find some friendlies who will champion your idea. Right. And then you take that small core cohort that Laura's talking about and you build on it, build on it, build on it. And if they come out of the business where the objectives are set, you'll get a lot of traction because then people will start to see how it's impacting different initiatives and they'll start to, you know, it'll have a little bit of a snowball effect like Laura said.

I like that. Yeah. Building things up one step at a time. Okay, so Omar gone.

I was, I just want to say plus one to Laura and Tiffany. And it's like you have a word of mouth ambassador in the company within the companies as well. It's like a reference customer who's speaking about the benefit of the data literacy program or how they were able to do their job better with something. Whether it's a process improvement or a tool improvement or just the awareness and the knowledge that they have doing these lunch and learn sessions, coffee chats, virtual or in person. This really creates that snowball effect. It triggers that snowball effect. Cannot stress enough to do that.

I like the idea of having just some regular sort of training sessions just to make sure that people are on board. One thing that's been mentioned a couple of times is that executives need to be involved. We don't really talk about which executives. Is this something that a chief data officer would own or this is going to go all the way to the CEO, like who's going to be in charge of changing data culture.

So I think a lot of executives will need to be to sign off on it. But clearly you can't have everybody at the table being the owner. It feels like a strategic initiative. Right. So like a chief strategy officer, but in partnership, as we've all said here with the data owners and the business owners. Right. But because it is a company wide exercise, I think you want it to be something that sits not in a business unit but across the organization. It might sit as one idea with like a chief strategy officer type, but in partnership with obviously the key players who would be needed to make it successful. That's just one idea. I could also think of others, by the way.

And I think it depends on the organization, the size of the company, the culture that already exists. But I mean, I think the CEO a lot of times does set the precedents right on the culture of the company and stuff. But depending on where processes lie, it could be the cfo, the cio, chief, chief strategy officer. It really depends on your organization. But the CEO probably wouldn't own the initiative, but they'd be that advocate to set the tone and then one of those chief officers would actually own it through and through.

Right, okay, agreed.

All right. So whenever you're trying to change culture, there's always some, in fact trying to change anything at all. There's always someone who complains. And so I think we need to talk a little bit about change management. So if you have employees who are kind of pushing back, going, well, this is the way I've been doing things for like three decades now. I'm not going to change my practices. How do you encourage them to make more use of data or change your tools and things like that?

I can start.

Okay, cool.

Only because I have a funny analogy. When I first started out, like, forget like way before Tom Davenport came out with the article that said, here's the sexy new career data scientist. So a decade before that, right. I would go, I started in investment banking. And so I would go into the company and I would say, yeah, we're going to use data and analytics to talk to your clients. And they would say to me, what, what are you talking about? I've had these relationships with these clients for 20 years, 25 years. Like, what on earth are you going to tell me using data and analytics that I don't already know about these clients? Because you know, it's a very relationship driven business in that state space. Right. And so scalability is not the same as when we think about it in the consumer facing spaces. It's just a funny analogy to your point, but I think one of the things that you do to help adopt change, I would say two things actually. One is I've learned over the years that pilots are really helpful, like POCs, proof of concepts, like we're not going to boil the ocean, we're not going to change all your processes today and start doing things new tomorrow. We're going to do take a little sample of people and do a pilot and let's See if it works and then if it does, then let's talk about the next step, like incremental steps to get people to buy in coupled with their, this is key by the way, their involvement and ownership. They have to be involved in the decision making process. We have to go out and get their input, particularly from the naysayers. And we have to empower them to take ownership of the changes and the impact because then they feel accountable. And once you get people to feel accountable for something, they are more likely to be in support of it and to try to drive it forward successfully.

I love the idea of a proof of concept, Laura, it seems like you might have some ideas around this.

Well, not around the proof of concept, but honestly I was thinking as Tiffany was kind of talking, I really want to understand why people have that kind of fixed mindset. What is that stemming from? Of why they're afraid of the change. And that's really important for me to know as a stakeholder. If they say hey, I've been doing this for the last 10 years and I don't want to change, is it because they fear their job's going to go away? Is it because they don't see much value in what you're doing? And so really understanding that why with folks that kind of fear that change, you can then address it accordingly. And that's been how I've kind of approached it in the past and it's really been successful.

Okay. Actually speaking to colleagues and finding out why they don't want to do something actually sounds like very useful advice. Okay. Omar, do you have any advice on like what a good sort of first step might be for like getting people like encouraging people to make more use of data or do data driven decision making.

I think stepping into their shoes, understanding their pain points and the opportunities that they have with data is the starting point for me. Then you can relate to whether it's an initiative in terms of tools introduction or an initiative in terms of process change. That why this will help them either achieve that new opportunity or address the pain point that they have. It may be you are trying to introduce a self service data management tool or maybe you have a new fancy data visualization tool or you have a new data catalog launch or you have a new and the best data warehouse in the cloud, for example, you choose the right audience and the wrong tool, you are ending up in a blank faces in a meeting room.

Right.

What's in it for me? So you have the best data warehouse in front of our end business executive. He's like, so what do I do with it? Do you want me to become a data engineer now? So we need to definitely match the audiences we are speaking to. And earlier as we were discussing the importance of communication and targeted communication, that's so important when it comes to this. So addressing those pain points, finding those quick wins, because you can't have a six month project to address a pain point which is happening today, we need to find tactical quick wins. It doesn't have to be perfect, but it needs to work for that Persona, that user. And I think those quick wins make a lot of impact. You get your customer referrals, you get that once again, that snowball effect started. If you have those quick wins.

Excellent. I like that. Start small and then build things up. So we've talked about getting started, but as data sets keep getting bigger, a lot of organizations struggle to keep up. So one of the main blockers to scaling up your analytics capabilities. You got something already. You want to go bigger. More data sets, Bigger data sets, faster analyses, things like that. Tiffany, do you want to take this?

Yeah, sure. So by the way, this is a super easy question. I'm not going to say anything that everyone on here doesn't already know. There's no secret sauce here. The blockers are always the same. Data quality, is the data accurate? Is it consistent? How do you avoid discrepancies? What's the reliability? Then you have infrastructure limitations. Do you have the right data storage, processing power, scalability of existing infrastructure to kind of handle increasing volumes and complexity? And then I think as we move into this data space, we have skill gaps. So where's the bridging that gap in data management, analytics, data engineering, so that we can effectively process and analyze these large data sets? We also have lots of integration challenges, right? We're migrating, we're moving from the lake to the cloud. We have siloed data sources, we have disparate data formats. So I know all of this sounds familiar. And then ultimately we have regulatory compliance issues. Right? So as we move into new systems, new processes, we have to make sure we're compliant with data privacy regulations. Are we upholding security standards and ethical considerations when handling and analyzing our data? So that's sort of a myriad of issues, but I think all of those contribute and it depends on where organizations are in their journey, really. Right. To how quickly they can scale the.

Analytics function and to package that all up, it's identifying the bottleneck in the process. Right. And the issue. And so Tiffany laid out all the issues really well and so that's where I can kind of see is like depending on where you are in your journey, you might have different bottlenecks. And then how do you relieve that bottleneck? Is it a data quality issue? Is it an infrastructure that. And how do you make sure there's funding towards that bottleneck?

Thank you for wrapping that up so beautifully, Laura.

Yeah, so data quality and governance and then identifying bottlenecks. Excellent. Okay, so thank you all for your insight so far. And this question comes from Awanish saying, how do we reconcile an analytics led culture with gut feeling decision making that may be entrenched in the organization's history? Is this a battle of change management or do we need proof points? I'm not sure what proof points are, but I like that idea. Like you get some points for providing proof. Yeah, I know we talked a bit about change management. Do you want to talk about, like, is there still a role for gut feel decision making?

I mean, I think that there can be. Right. Not everything's predictable, but there should be. Like there's still human led decision making that should be backed by data. Right. And so being able to change the culture, it just depends. Again, go back to that advocacy or friendlies Tiffany was talking about, which I really like that I might start using that term. Tiffany.

Yeah, I think Laura's absolutely right that you want to think about how do you human. We can't lose like the value of human intuition, you know, when things are going well or not, you have a gut feeling. I think all of that is very important. But then how do you tie that to the quantitative results that you want to achieve? And I think this idea of proof points, proof of concepts, pilots, you know, anything that you can utilize in a quantitative way to show why moving from a more qualitatively driven culture to a more quantitatively driven culture matters, I think is very important.

I like that. And Omar, do you have anything you wanted to add on that plus one.

To the previous recommendations? I think the idea should not be to remove the human aspect from decision making. It's very important that we stay there. It's all about raising the trust level in the data so that people can rely on the data to make that decision. And is it easily accessible for them in time? If I need to make a decision today and I'm getting something in five days or five weeks, what good is it that for me? So we need to provide that old saying, right information to the right people at the right time in the right format, on the right device. All those rights are Absolutely important. And we need to establish this trust so that people who are the decision makers can trust that data to make that decision. And you combine that with your supporters, you combine that with communication, you combine with role modeling from the top executives that will initiate that change that we need. It is about change management.

Okay. If you can't trust your data, you're probably not going to use it for decision making or if you are, it's not going to go down very well. Okay, we've got time for one or two more questions. So Anes asks, do you know any differences how data is leveraged in the private sector versus public sector? So maybe you can talk about this in the context of like how is it going to change your data culture whether you're in private sector or public sector? Actually, since we're supposed to talk about roi, is what you're going to measure as like your return on investment, is that going to differ if you're like in a non profit sort of place?

Let me do that in two aspects.

Right.

I have seen that there are public private partnerships are also starting when it comes to data, especially on data sharing, for example. Example, because it's no longer just about the data within an enterprise, for example in private sector it's also about how can I leverage something which is outside. And that also means that there needs to be a fundamental shift in the culture of the organizations both on private and public side on data sharing and collaboration. That's quite a big industry wide change we are talking about. Right. It's huge. At the same time, whether the organization is, let's say public or private or they are not in profit, for example, there are goals that their organization still needs to achieve. That organization still needs to work efficiently. For example, they need to make the big bang on their investment. Still they need to measure whether they are initiatives in terms of for data and AI, are they being used even or not. So those principles are still common. Of course, the organization goals itself might be very different.

All right, I feel like we've come full circle back to the very first question where Tiffany's talk about, well, it might not be revenue that you're measuring. It's going to be like some sort of team specific goal. But you just want to make sure you're working towards something you can measure. So Ryan asks, how can we make our data sources and insights widely available across an organization while still maintaining chain control of the story the data tells, ensuring everyone speaking the same language. So I think that's how do you make sure data is Discoverable and accessible, but also make sure that different teams understand each other. It's a tricky. This is a big topic. It seems like.

Not to put Laura on the spot, but it seems like a MongoDB kind of question. Sure.

I mean, I think the biggest piece here is to make sure that there's good data owners to the process and to make sure that we educate stakeholders through and through across the board. Right. So if we democratize data, you know that people aren't cutting the data all differently and all have different answers for the same question. That is my worst nightmare. That's where part of the data literacy comes from into play. Making sure there's sources of truth and data owners assigned to that and then official reporting to make sure that there's defined official reports for certain things. So I think those are the three elements that come to mind for me with that question.

I will answer it with I will just add a hashtag, Tiffany, free the data, and that will lead you to the place you want to go. Go ahead, Tiffany.

Sorry. Thank you, Omar. I was just going to add that I also think it's important for metadata strategies. So right now we have all these data sets. I can pull revenue from five different data sets, and I have five different revenue numbers. And I need meta tags, Right. To help me understand so that everyone knows what they're pulling and looking at. So sometimes even when you don't have the infrastructure in place, if you could get a tagging strategy that is consistent so that everyone who's pulling something is actually pulling the same thing, even though it's coming from different places. Because I do understand that technology build outs can be expensive. Then you get to a place where people can start kind of utilizing the same information and singing from the same songbook, telling similar stories, et cetera, about success.

It's all about keeping that shop clean. Going back to my shop.

That's right.

No rats in the basement. Hopefully.

Not in Laura's basement.

No, absolutely not.

All right, Wonderful. We've got 30 seconds left. You got 10 seconds each for final advice on how to get better at using data and making more money from it or hitting whatever roa you want. Oh, my. Do you want to go first? What's your last advice?

We talked about roi, change management. I would like to leave with the thought, be the change you want to see in the world. Be a role model of owning the data, practicing it, loving it, curating it, sharing it, taking the ownership.

All right, I like that. That's a call to action for everyone in the audience. Go and do something. Make data better at your own organization. Excellent. Laura, do you want to go next?

Have a long term vision, but have a lot of short term wins so you can keep seeing value over and over and over with your data projects. I like that.

Yeah. No waiting for years before you see some kind of benefit. And Tiffany, would you like to wrap us up?

Yeah. I would say align with business objectives. So make sure your data initiatives are closely aligned with business goals, strategic priorities, and key performance indicators so that you can drive tangible value and outcomes.

I love that. Align with whatever metrics or business goals you've got. That sounds like very useful advice. Okay. With that, we are done. So thank you, Omar. Thank you, Laura. Thank you, Tiffany. That was amazing.