Video: Data to Value Talk: The Data Value Gap: Why Good Intentions Aren't Enough | Duration: 1844s | Summary: Data to Value Talk: The Data Value Gap: Why Good Intentions Aren't Enough | Chapters: Welcome and Introduction (6.08s), Guest Introduction (42.82s), Business-First Data Strategy (145.36s), Warning Signs (300.11s), Critical Data Assets (487.74s), Go-to-Market Transformation (733.03s), Data Governance Reframed (980.94s), Data Ownership (1137.51s), Executive Leadership Buy-In (1279.98s), AI and Data (1431.52s), Key Takeaways (1618.58s), Q&A and Closing (1715.975s)
Transcript for "Data to Value Talk: The Data Value Gap: Why Good Intentions Aren't Enough": Alright. Good morning, good afternoon, or good evening, everyone, and welcome to our first episode of data to value talks. Thank you for joining us today. This is a live session that's being recorded, and we welcome your active participation, for your questions. There will be a q and a part at the end of the event, but feel free to, well, to ask your questions in in the chat at any time during the session. We will answer them either immediately or at the end. Okay. Let's get right into the topic of today's session. One thing I hear, from, yeah, from customers almost every day is this. We are investing more in data than ever before. We are modernizing platforms, launching governance initiatives, and increasingly using AI. But tell me, how do we turn those investments, into measurable business value? And that's exactly what today's conversation is about. I'm delighted to be joined by Sean Conolly, vice president of data strategy consulting at Precisely and one of the industry leading experts in data strategy, governance, data management, and business value realization. Over the years, Sean has advised organizations around the world, on how to build trusted data foundations that support better decisions, operational efficiency, digital transformation, and AI readiness. Today, we will explore why some data initiatives succeed while other struggle, what the warning signs are when programs start drifting, of course, and more importantly, how organizations can close the gap between good intentions and real business outcomes. Sean, it's great to have you with us today. Yeah. Thanks, Ralph. It's great to see you. And, it's great to be here because that's exactly where, you know, many organizations find themselves today. They have got data initiatives. They have data teams. They have some governance programs. And most have AI pro projects going on. But they're still asking, you know, how do I change the organization? Where is the business value? And that's really the conversation that we need to have with organizations. Alright. Sean, when you look across the organizations you are working with today, there certainly isn't a lack of ambition. Right? Companies are investing heavily in data and AI, and most of them have an earnest desire to become more data driven. No doubt about it. On paper, that should be a leap for success. Correct? But many leaders still struggle to demonstrate tangible business outcomes from those investments. So let me start with a simple question or actually to why is turning data into into business value still so difficult for many organizations, and why do so many data programs still fail to deliver the expected value, Sean? Yeah. So, you know, I think the biggest biggest reason is actually quite simple where, you know, most organizations, they tend to start with, looking for a silver bullet. They start with data and they start with technology. And really instead of focusing on a business challenge or a business opportunity or a business outcome, some some case that's impactful for the business. So they'll launch governance programs and they'll buy tools, create councils. Oftentimes, they've defined some policies and built some dashboards, but, you know, business leaders don't invest in data for the sake of better data. They invest because they expect their organization to get better and they expect results Yeah. like they. do with any investment. So when data and the data programs, become disconnected from these priorities, people will lose interest. Leaders will not provide funding, or it becomes very difficult at best, and momentum often fades. And frankly, we get called in kind of in any number of situations, but this is a fairly common one. Most successful organizations, they kinda flip that where they start with some type of business challenge or some type of opportunity, and they identify the critical data that impacts that challenge. And then they focus on investing their time, investing their people, investing in purchasing capabilities, where, you know, that measurable value can be achieved for solving that problem. I mean, you know, it's funny because it sounds a little bit obvious, but I just don't. see many companies, actually doing it consistently. Okay. So well, that's that's interesting. So the key is really starting with the business outcomes first, not the data and technology. Alright. So but but what are the the the symptoms that should alert us? I mean, you have worked with a lot of organizations over the years. Yeah. When when you walk into a company and look at the a data program, what are some of the warning signs that immediately make you think, okay, this initiative is maybe in trouble. Sean? Yeah. I mean, there are definitely some red flags, and and I would say first, the organization or more likely IT is talking about data quality. I mean, when I go someplace and then we sign in to register at the front desk and our contacts are all in IT, that's probably gonna be a bit of a challenge. But when parts of the organization are really it can't explain what business process is being impact, impacted by good or bad data, you you're it's gonna be in trouble. It's you know, I love to use analogies, but it's sort of like a hospital obsessing over how clean the floors are, right, while kind of ignoring what's going on with the patients and not focusing on helping people get better and healthy. Clean floors matter for sure, and it's part of the the, you know, what makes a good hospital a good hospital, but that's not why the hospital exists. And that's not why data programs exist. Data programs don't exist just to create good data. Right? So we need to focus on what actually matters. And second, the executive sponsors, who are often part of, you know, some type of data board or decision making body for around data. When they stop attending meetings, that's a problem. And when they can't articulate why, that's also a problem. But when we think about just having meetings, proper meetings that you have with, some type of leadership council, they need to be there to make decisions. They're not there to have an update on how well you're doing with the project or the program. It's not a status update thing. You're looking for impact and you're looking for decisions from leadership. I would say the third thing is that teams can be obsessed with kind of the governance, activities themselves versus kind of the outcomes. And kind of the I would say maybe fourth. The the most important thing is that nobody can quantify the value. So whenever I hear, you know, like, oh, our data quality scores are improving in this area of that, my next question is, well, which business objective or problem is prioritizing this, what processes and and this business KPIs, have improved because of it. You know, so if nobody can answer those questions, chances are that the program is not kind of instantiated and has drifted away from business relevance. They're just doing it for the sake of doing it and kind of nobody cares. I would say that's usually when, it's kind of obvious that there's gonna be some challenge with the program. K. So so if the problem is that we are focusing too much on data and not enough on outcomes, what's the mindset shift leaders need to make? Where do successful organizations start differently? How can organizations make the transition practically? What's your recommendation or guidance, Sean? Well, I think, you know, I gave the hospital analogy earlier and kind of the cleaning the floors versus helping patients. Right? So if you think about it like an emergency room, you can't treat everybody at once, so you gotta figure out who needs help most urgently. And really kind of the same thing holds with our data. Not all data is created equally. As soon as we say that this data is a priority and it's a critical data asset, it's an investment in people and process and coming up with data quality rules and all of the things that go along with that. Every organization has a handful of things that really matter kind of the most like revenue, customer experience, compliance. The question is is which data is directly keeping those things healthy or hurting them? And that's where you focus. Everything else can wait. But so I worked with a client, a few years ago that was building out their data program. Kind of I was helping them build their data program from scratch. This is kind of burrow maybe, I don't know, seventy years ago. And, when I started working with them, their CEO was very focused on having the best customer experience, white glove or premier service. Higher price was okay, than the competition, even kind of seen as a good thing just to retain that sort of top shelf, you know, view or perception of the customer. So that was the foundation in the direction of my data program. That's the data we were gonna go after was specifically around those things. You know, and and cost didn't matter as as much. So transactions cost, that was lower priority data for us. But, then the CEO was fired, and, they said that they the board and new leadership had talked to the customers, and the customer said basically, the feedback was, you know, hey. Stop trying to be different and just be good at what you do. And then the board came in and said, by the way, we want you to make money. So when you think about the data that we were going after and had to be, good to support that direction, it was different data. Right? So, companies, you know, that that that focus on those outcomes and focus on what leadership needs is super important because it drives that critical data like I described a minute ago. And and the investment in ensuring that that data is gonna be trusted. So like I said, companies have, like, a handful of very top priorities. Usually, you can find it either in annual report or on their website, or certainly by talking to the organization, you can find what the top things are. And then functions will provide you what the challenges are and what their goals and objectives are. But things like revenue growth, operational efficiency, customer experience, risk management, you know, all of those are usually pretty top of mind. And then the question is, which data impacts those? Which processes? And we really encourage our clients to have a very fact based way to do that. So we we call it kind of a decision tree where we're looking at, a repeatable scalable process in order to determine which data is gonna be critical. Because like I mentioned earlier, it's an investment. As soon as you say some data is critical. So we wanna ensure that we're aligned to where that, effort it should be concentrated. So when organizations focus on those critical data assets tied to efforts and specific business outcomes, they really can demonstrate value very quickly, and then you start to see momentum in a data program. Super critical. Mhmm. Mhmm. That's very interesting, Sean, but could you maybe bring this to life with with another real world example? Is there a customer story that really illustrates what happens when a company starts connecting data initiatives directly to business outcomes. Yeah. So so data, you know, doesn't happen in isolation. And and data as a part of a business process really is kinda where the change takes hold. So we worked with a client, around a go to market challenge. So this particular company, it took them about eighteen months to from the time a food scientist mixed up a new granola or new yogurt, to get that product to market, to actually get it to the store labeled, you know, with all the marketing materials and everything in place. So that process was built because they've been in business for a long time. You know, most companies that I deal with, very few are born in the cloud and don't have any infrastructure or buildings or old processes. They've grown through mergers and acquisition or just, you. know, whatever. So data tends to be a bit messy. Well, having this history isn't necessarily a bad thing, but, now it's not okay. Twenty years ago, it might have been okay that it took that long to make a change, but now there's just no barriers to enter anymore. I mean, I can mix up some kinda cool granola or something in my kitchen, get the right labels printed, have somebody test it, in in multiple channels, whether it's Amazon or whatever to get that product actually out to customers. So competition has not stood still. It's just sped up, and the the barriers to entry are just not what they used to be. So, anyway, we worked with this company to really take a hard look at optimizing that entire business process, which is extremely complex. An SAP shop, so tons associated with all that, but not just SAP, lots of other, systems involved in that process as well. And as you can imagine, from marketing to the food scientist to, quality to what can we say that it has no peanuts in it? So all the allergens all the way through manufacturing. Every single company, function in the cuff company was almost involved. So when we look at business processes like that, most processes and companies are not down to a deep enough level. They're. just at a higher level, level one, two. We go all the way down to level four, level five, looking at data down to the task and activity level. And it's really complex, so many functions. And, having the right person know at the right time, entering data and making those decisions super challenging and super important. So for example, don't ask the food scientist while they're mixing up the new whatever it is to, tell me what the final weight of the product is gonna be or the size of that big package because they're just gonna enter wrong data with some mandatory things and move the process along. So so, anyway, we kind of reengineered that process with them, really focused on process efficiency and data, and got them down to the point where we were able to decrease the time to market by nearly 50%, Wow. the number of touches. So imagine me passing off decisions and data and that, reducing the number of touches by 68%, and billions in inventory cost reductions, more than about $27,000,000 annually. So it was a huge difference for the organization. But it really was not just about solving a data problem. It was aligning. the people, the process, Yeah. accountability, and trusted trusted data to those measurable outcomes. And and that's kind of really where the value came from. I know, sorry, kind of a long example, but. it. just kinda shows you the importance and the complexity of you know, you can't just pick data out of the air and say this is critical and, you know, let's have some data quality or data governance around. Yeah. Yeah. Well, that was a very impressive example, Sean. Thanks for sharing this with us. Let's talk about data governance for a moment, Sean, and the word alone tends to make people very nervous still. Yeah. Many executives still see governance as bureaucracy or control. How would you reframe that conversation? How should leaders think about data governance today, Sean? Yeah. Governance has had kind of a PR problem for years and years and years, probably since inception. I think you might have been at the conference that somebody it was in Frankfurt, and somebody asked me if there was a university program for governance governance. And I'm like, no. Because nobody would sign up to do that. It's Yeah. but imagine if we had called it, AI enablement or. process. You know, I'm I'm sure we could've it could've been named better. But, anyway, I mean, yeah, AI I AI enablement now is a large part of what people are doing. So it's it's more it's more than just governance. But anyway, so many people view it as kind of policies and, you know, more like if you're driving a car, it's the brake pedal. It's, you know, something that's gonna slow us down and it's problematic and somebody's just looking over my shoulder. But in reality, governance really should be the accelerator. I mean, if we're good in our data, we can do so much. It provides clarity to the organization. It creates and establishes ownership. It defines accountability. It really does enable organizations to make decisions faster with much greater confidence. And, you know, organizations that look at it as an enable enabler. So, again, the accelerator and not the brake pedal. They're gonna make the greatest progress, and and they don't treat it like just a compliance exercise or somebody looking over their shoulder. They really treat it as a business capability. So so done right, it more it's more like a traffic light, I would say, where. where nobody I don't like stopping at red lights, but but without traffic lights, I mean, everything either grinds to a halt or there's gonna be crashes. And governance creates that that flow within in the organization to ensure we're having, you know, clarity and who owns what, who can move when, who makes the decisions, how do we, how do we move faster instead of sort of second guessing the data that you're looking at? Yeah. Yeah. Yeah. Alright. So, Sean, you you've just mentioned, responsibility and accountability. And I've noticed that these topics are really coming up more frequently in conversations conversations with clients. And, everybody agrees that data is important, but when actual issues appear, responsibility suddenly becomes a bit less clear. So, why is ownership still such a challenge, Sean? Yeah. That's a good question. I think that, data doesn't really have org charts. Certainly doesn't respect org charts. It Yeah. it's typically has cross organizational life. So for example, sales creates a customer record, operations is gonna use that to fulfill orders, finance is gonna create invoices and report on it. IT kinda supports the whole process. But so when ownership is unclear, problems really kind of fall through the cracks. There's lots of finger pointing that goes on in an organization, but no resolution. And even if there is resolution, it's not lasting resolution. The problem, you know, might get fixed just to get that order through or to get that invoice sent. But systemically, it it without rules and ownership, it it just doesn't get fixed. And and that's why we emphasize I think I mentioned earlier that IT shouldn't own data. I mean, business people own data. And that's why we emphasize it, that whole thing. about business ownership versus technical. Ultimately, people are responsible for business outcomes, people in the business, people in the functions, they have to also be responsible for the critical data. Otherwise you're just never gonna get there. And so a big part of like the top two questions I get asked all the time is how do I show value of my data program and how do I get people to care? And I'll tell you when you solve people's problems, when you help them meet their objectives, they care. So you just have to kinda get to that point. And like I mentioned earlier, the prioritization is ensuring that you're doing the work that that is gonna matter to people. So, you know, if data is everyone's responsibility, then it's no one's responsibility. And so, you know, I mean, accountability is super critical. Yeah. So in your experience, how important is executive engagement then in this context? Can a data initiative really succeed if senior leadership sees it as something that belongs only to the data team? Sean, what would you say? Yeah. I mean, actually, I got asked that about a month ago with a client, how important is leadership and what if you have leadership that kinda doesn't really kind of understand and get in. I'm like, that's that's the number one reason why I would tell you things fail. I mean, leadership is probably the single biggest success factor. And, honestly, Mhmm. in my experience, you can have the best data team in the world, and still fail without executive buy in. And when I say buy in, I mean, like, deeply at emotional level, leaders need to understand and even kinda feel the impact of big data or good data for that matter. It's really critical that the companies that get this right have leaders. that don't just show up to daily. I mean, they make it about revenue, impact, risk, and customer outcomes. When the when the conversation is at the top, is at that level, And and really focused on business value. So. for example, the one I gave earlier around kind of the go to market thing. I mean, that's a much easier and more impactful conversation to have than data hygiene. Right? I mean, it just it just doesn't matter. You can get alignment so much faster when you focus on that. So really talking about these, you know, kind of major areas that I described earlier, revenue, around customer improvement areas, risk mitigation, outcomes. I mean, even regulatory compliance. I mean, I get that, you know, people don't wanna get fined, and they don't wanna go to jail, and they don't. have so. so that's important, but, like, we should all be doing that anyway. And and organizations don't get excited, about regulatory issues. So really kind of creating alignment, and ensuring that resources are focused, like I mentioned earlier, really matters the most. And but but I will tell you at the end of the day, without executive sponsorship or the data program and for, you know, kind of the prioritization of what capabilities people and process are being invested in, I'll I'll go far enough to say that I the initiative will likely fail. Okay. Alright. So, Sean, we really can't get through a data conversation these days without talking about AI. Have you noticed Yeah. It goes. change? Yeah. Have you noticed a change in the in the questions customers are asking since AI became board level priority? How has the the rise of AI changed the discussion? Yeah. I mean, every AI has basically removed all the safety nets that we had. For year years, you could get away with messy data. Right? Because you had smart analysts or a savvy manager who could look at something and say, oh, well, that doesn't look good. Let me check it out. Well, AI doesn't do that. It doesn't stop and take a breath and kind of reevaluate. It kinda looks at face things at face value with the data that it has and it runs. And it doesn't paper over them, doesn't clean it up, it just amplifies the problem. So the old saying of garbage in garbage out, now that's just more garbage faster and more garbage out faster. It's. a big problem, but. it's a significant risk. And, you know, precisely we're really focused on and have been for a number of years is data integrity and trusted data. The the trusted data is just not a data management issue anymore. It's really kind of an AI readiness issue. Mhmm. So leadership that wants to run fast, in the direction of AI, they need to run faster to ensure that their data program is, is is ready, that their data can be trusted, that people are using it in the right and responsible way. Okay. And actually something I've become kinda passionate about lately, and more outspoken about is not just the organizational risk, but kind of the environmental impact as well. Yeah. Right? Oh, yeah. Like, Yep. AI now without a solid date data program is just irresponsible. So running models again and again with the wrong data, bad data, old data, uses tokens. Yes. But, you know, I mean, it also uses a lot of electricity, a lot of processing power, a lot of water. And Yeah. I think we are all aware that. that is problematic today and gonna be more a problem in the future. It's just gonna continue. Right? Yeah. Okay. And the other thing. I I would say is context matters. So, where people have been buying data for a long time, Mhmm. having deeper and richer context, is even more important for AI models. So I do a lot of cycling and I, you know, the type of clothes I what I choose to wear on my ride this morning depends on the weather. That's the context as to what I should wear. Well, I mean, it's it's super important for the models, Mhmm. Yeah. to ensure that we have context. And as you know, I mean, Precisely really does take that holistic approach. I mean, we look at we think about trusted data as having capabilities, having, you know, enriched data to make good decisions, and then, you know, the right people and. process and services around that. So, really, all three are required. You know, well, obviously, we could do an entire session Yeah. on. AI. Yeah. Definitely. Definitely. Yeah. Sean, I originally had one more question for you, but in in the. interest of time because we are approaching the end of our session, we are skipping that one, and the time really flies. And, Sean, before we are moving now to the to the audience q and a, let me ask you one final question. If a data leader was listening to us today and now wants to take away just one simple message from this conversation, what would you want that message to be? I think everyone wants to talk about AI and that an AI model is like the engine in the car. But but, really, at the end of the day, data is fuel. And you could have the most powerful engine in the world, but if you put diesel into a petrol car, you you got a problem. Or if your fuel is bit bit bad, you got a problem. You don't need to have perfect data before you start. That's like an impossible standard, but Mhmm. you do need to have trusted data in this specific area where AI is gonna influence those real decisions. I mean, start there, do that part right, and then because you you've gotta have the competency of the people, the capabilities, the data quality, get governance, all of that heavy lifting and capability. You gotta have that in place. And organizations that take, you know, just take a breath and, you know, figure. out important and invest in that, they'll they'll run faster than. their competitors. Alright. Okay. Cool. So, Sean, thank you very much for sharing these insights. And, before we wrap up, I would like to open the floor for some questions. Steve, we have two minutes left. Please be sure we are going to follow-up each of your questions afterwards. So nothing is going to get, lost here. So the q and a is open now. We are looking for your questions. There's one question already showing up here. Sean, where should organizations start if they have limited budget and limited resources? Well, that's a tough one, I believe. Well, yes and no. So I tell people all the time, I mean, we gotta find what that use case is. We gotta find, a use case where the impact is gonna be the greatest. Ideally sort of cross functional so we can get more people involved in the process, but where the complexity is relatively low. I would start that's kind of what I always look for. I mean, where I describe that go to market process, I wouldn't start there. Mhmm. So. so. we we help we can help clients, identify. various areas. where there's. a big end. Cool. Unfortunately, there's only just one minute left. So, Sean, thank you for joining us today. I think one of the most important takeaways of the day's session is that successful data programs are not built around technology. They are built around business value, accountability, and trusted data foundations. Thanks to everyone for joining us for this episode of data to value. talks. We hope you found the discussion valuable and practical. We look forward to seeing you again soon. And just a quick heads up, you will receive a short online survey about this webinar, and I'd like to ask all of you to take just five minutes to answer our questions around the content, and quality of our webcast and whether you wish to receive any additional information or further invitations. Have a great day or evening, everyone. Thank you very much. Thanks.