Latest / Extropy on AIR: Finance Transformation, AP Automation & AI in Finance / The Digital Transformation Myth: Why Technology Is the Least Important Part
Transcript
- speaker-0: Welcome to Extropy On Air, the podcast from Extropy Advisors, where we dive into the world of AI, digital transformation, and the future of business. Each episode will bring you perspective from leaders, innovators, and experts across industries, all focused on helping organizations, and more importantly, people, thrive in a changing world. Let's get started. Welcome back to Extropy On Air. Glad you all were joining us again today. I'm Kevin Zirkel with Xtropy Advisors and happy to have with me Mike Jasper, the Vice President here at Xtropy. Mike, I'm excited about this discussion. If you guys have been listening, the first two episodes that we started in the series we've kicked off introduced a different way of thinking about transformation. We talked a little bit in that first episode about the concept of entropy or corporate entropy, which is a natural drift towards disorder within an organization. We came back in the second episode, we introduced the concept of extrapy. And that's really the deliberate design of ⁓ coherence that turns complexity into advantage for organizations. So today, we're actually going to challenge something that sits right at the center of how most organizations think about transformation. It's a word that's been around for a long time, but it's that classic buzzword, digital. Most enterprises, digital transformation has really become synonymous with technology, I think. It's about new platforms or new tools or new capabilities. But Mike, I want to get into this episode, and I'm going to hit you with a bit of an uncomfortable truth. I'm going to make the assumption, or I'm going to make the statement that says, technology is often the least important part of transformation. What do you think about that? speaker-1: Kevin, we've always looked at it as people process purpose. And that's really a departure for a lot of people where they're used to hearing people process technology. But we switch the technology for purpose. And every time we say that to a leadership team, there's a pause in the room. That's usually because on the surface, it sounds very counterintuitive, especially when you've invested hundreds of thousands or millions of dollars into platforms, AI tools, automation, analytics. But when you start unpacking that experience, the customer's gone live. They've rolled these systems out and yet still things feel harder than they should feel. speaker-0: Yeah, ⁓ that's a pretty common phrase. hear it all too often that that whole shouldn't be this hard, right? speaker-1: Exactly, and that's usually the first signal that the issue isn't technology, it's the structure. Because good technology rarely makes things harder, but it does make existing problems way more visible. speaker-0: And it actually ends up making them faster too. You get that old adage of being able to do the wrong things faster than you were ever able to do them. And that's not a comfortable place for folks. speaker-1: Exactly. And that's the discomfort that leaders are feeling. It isn't because technology failed. It's because the system is sitting in a way that it wasn't designed to be supported. You know, we've automated bad practices. We haven't optimized our process. speaker-0: Yeah. And that's kind of what I want to get in and really unpack today because if we can break the myth that technology is really the center of every transformation, we can start focusing on what actually drives change for the client. So if we could, let's start with how we got here and this whole concept of why did digital become the centerpiece of transformation? What are your thoughts on that, Mike? speaker-1: I mean, part's pretty simple, Kevin. Technology gives leaders something concrete to anchor their project to. You can budget it. You can put a timeline on it. You can assign owners to the product. It feels controllable. It's one of the knowns in a project. But there's also something else going on. Technology can help organizations avoid some of those harder conversations that should be happening. speaker-0: Yeah, you're exactly right. Because honestly, once you move beyond technology, you start getting into the real questions. mean, these questions are, you know, who actually owns this process end to end? That's difficult for some companies. You get into things like, you know, why do we have three definitions of the same metric? We hear that one a lot. And then, you know, why did two teams make the same decision differently? Those are really uncomfortable questions when you get in and start asking those of organizations and really them asking themselves some of these questions. speaker-1: Yeah, nine times out of 10, they don't have clean answers for those. know, instead organizations focus on what they can control. They buy platforms, they implement workflows, they institute dashboards, and it all creates this feeling of progress in the organization. speaker-0: Yeah, and actually let's stay on that for a second, that feeling of progress. Because I think honestly that's one of the most dangerous dynamics that we see in digital transformation. know, there's this moment in almost every transformation where somebody in leadership feels like things are moving in the right direction. You know, the system is live, the dashboards are active, the reports look a little bit cleaner maybe than they used to, but underneath of that, nothing fundamental has really changed within the organization. speaker-1: It's almost like there's visible progress with invisible stagnation. You can see activity, you can measure some outputs, but the underlying process hasn't improved. Decisions are still slow, expectations are still high, people are still relying on those Excel spreadsheets, tribal knowledge. There's still that work around going on in the organization. speaker-0: That's what's tricky. mean, is that most executive reporting, it reinforces the illusion, if you will. So because you're measuring implementation metrics, things like adoption rates or number of transactions you might process, what your cycle times look like, but you're really not measuring that concept of coherence that we talked about a little bit earlier. speaker-1: Exactly. You're not asking, did this project reduce friction across the system? You're asking, how well are we using the tool? And those are very different questions. speaker-0: Yeah, without a doubt. Actually, it kind of leads me to one example. I know we worked with a finance organization that had fully implemented an AP automation platform. And on paper, it was successful. I mean, quite honestly, but there were high automation rates, there was strong throughput. But as we started to look closer, the team had really built an entire shadow process to manage exceptions. yeah, invoices were flowing through the system. But the complexity really just moves somewhere else in the organization. speaker-1: Kevin, that's a perfect example. The system looked very efficient. All the dashboards were green, but the organization itself really didn't see any efficiency gains. There was no time save. The team was still working overtime. They're still asking for more headcount to be added. And that can be the illusion of digital. You know, it can make systems look clean while it's actually making more work or more fragmented work on the backend. speaker-0: Yeah, and I'd love to get a little bit more from that particular topic. So let's kind of go back to that core idea that we talked about first. I'd kind of love to get your thoughts on why you think that technology is really the least important part of the transformation project. speaker-1: Yeah, I think it's, I look at technology as the final layer. It's not the foundation. You know, maybe back when we had, you know, ERP software was new, that was a different story. But really today, technology should sit on top of decisions that have already been made about how the organization and how the process should be optimized. If those decisions are inconsistent, technology won't scale consistently. It'll be very inconsistent as well. If those decisions are unclear, it's going to create confusion when you start scaling that rollout, that process, that people aspect, that purpose are going to be the foundation that the technology is going to enable. speaker-0: Yeah. Yeah. And I think that's a good point. And honestly, that's why sometimes we see organizations going through all these upgrades of their platforms that they have, but they never really see proportional value that was associated with the investment. I think part of that reason is they're really just changing the surface. They're not truly redesigning the system that sits underneath. speaker-1: Exactly. And there's another layer to this too. You know, got to remember technology is finite. It has defined capabilities. know, organizational behavior is dynamic. It evolves, it adapts, it creates these workarounds in the organization. And if the system isn't designed to account for that behavior, technology is always going to lag behind reality. speaker-0: Yeah, that's a really important point because that transformation, like you mentioned, it's not just technical, it's behavioral. And behavioral is always going to find a way. mean, that's reason we do so much shelf order out there, right? So let's go back and kind of revisit the framework that we had introduced previously, Mike. You remember that concept of structure, system, technology all put together? ⁓ I think this is where things really start to click for people, right? speaker-1: Every single time. Yeah, absolutely. think, you know, structure defines how decisions are made and who owns each piece. The system defines how things flow, how the information moves. Technology then enables that and scales it at system. Most, most organizations are inverting this. They start with technology, then they try to retrofit their system and their structure around the technology. Yeah. speaker-0: almost backwards and I know some of our some of our builder clients might appreciate this. It's kind of like trying to build that house but starting with the roof instead of the foundation, right? speaker-1: Exactly. When you do that, everything underneath becomes reactive and you're constantly adjusting processes to fit the tool instead of designing the tool to support the process. speaker-0: And that's the end of the day, that's where you're going to see your friction really show up. mean, people saying things like, yeah, this system won't let me do that. Or, you know, we have to work around this step. I I think anytime you hear something like that within your organization, you know that, I mean, these are signals that technology is dictating behavior instead of enabling it, right? speaker-1: Yeah, and over time, those workarounds are going to accumulate, which brings us right back to our entropy. speaker-0: Yeah. And speaking of entropy, we spent a lot of time on that one in the first episode in here. And if I could, I just got to pause for a second because for our listeners out there, if you're listening to this and you're thinking we've invested heavily in technology, but something still feels off. Like so many concepts we discuss in this podcast, you're not alone if you're feeling that way. This is exactly where we spend a lot of time with leadership teams at Extropy Advisors. So if you would like. I encourage you all to go check out getextropy.com. You can learn a little bit more about how they can help you assess where your transformation might be breaking down, whether it's at the structural level or the system level, not just the technology layer. And if this conversation is resonating, please make sure to subscribe, share this podcast with others on your team. Each episode we do, we try to build it on the last ones. Appreciate you guys listening. Let's talk about kind of failure patterns, if you will. Where do you see organizations consistently go wrong? when they center transformation around the technology. speaker-1: I think one is one that we've already hinted on already. I call it the tool first thinking. They start with a solution and they go looking for problem that can solve. speaker-0: instead of starting with the system they're trying to design. speaker-1: Yep, exactly. Another one is fragmentation through success. ⁓ And what I mean there is different teams successfully implement different tools, but no one's responsible for how those tools work together. So the success is at a local level. It creates complexity at the enterprise level. Each group is working fine, but the company itself isn't seeing those benefits due to extra work between departments. speaker-0: I like the way you put that. think it's a great way to say it. Fragmentation through success. mean, nobody feels like they're failing, but the organization as a whole, it just becomes a lot harder to operate in those scenarios. speaker-1: Yeah. And I think the third is over-reliance on the integration is a fix. Leaders assume that just because systems are connected, coherence will follow. But, know, integration connects data. It doesn't align decisions. If you're working with one set of data, completely different, with different use cases than in another system, it's going to create complexity all over again. Yeah. speaker-0: and actually hit on one of our key words there in that last phrase. I'll set you up with a softball here. If technology isn't at the center of that transformation, Mike, what is? speaker-1: It's the coherence, the purpose. think that's really what needs to be at the center. Transformation should be centered on how decisions are made, how the information flows, how accountability is structured. Everything else should support that. speaker-0: Yeah, and I think this is really where that shift happens. mean, you get from thinking about transformation as something you implement to thinking about transformation. It really is something that you design. speaker-1: Yeah, and you maintain, you know, because coherence isn't a one-time achievement, you know. It's something you reinforce continuously. Like we said, business changes, processes change, regulations change, mergers and acquisitions happen. We have to be adaptive as we go through and really vigilant around our coherence. speaker-0: Yeah. And just to bring us back to now, extropy, kind of that episode too, if you were listening earlier in the series, because extropic organizations don't just improve. mean, they improve in a way that makes future improvement easier. I mean, it really is a compounding effect when you think of it that way. speaker-1: And once you, once you actually experience that, it's so hard to go back to the old way. speaker-0: Yeah, without a doubt. So maybe what we can do, Mike, I know you try to do this in most episodes, but let's try to make it a little bit actionable for our listeners here. You know, if you're a leader listening to this, what do you do differently kind of starting next week if you're finding yourself in one of these transformational stages within your own organization? speaker-1: Yeah, the first thing is take a pause before the next technology decision. Ask yourself what system are we trying to create here? Take that information. Second, identify where your organization is compensating for weak structure. Where are we putting band-aids on things? Where are we expecting technology to fix something that's, you know, process-based? I'd say third, map out decision friction. Where do decisions slow down? You know, where do things get escalated unnecessarily? What produces inconsistent outcomes? Fourth, redefine success metrics. This is something we talk about at XTP all the time. Start measuring clarity, alignment, coherence, and do so in a quantitative and qualitative way. speaker-0: Yeah, I think that's great advice. So, you know, maybe what we'll do is let's just kind of bring it all together. Some of the things that we've been talking about, you know, digital transformation, it has been framed as a technology journey, but at the end of the day, technology is not the driver. It's really just the amplifier and it's what's amplifying lacks coherence. The outcome is always, always going to fall short in those types of scenarios. speaker-1: Yeah, the real work is in system design, defining how the organization operates, how decisions are made, how information flows. Technology supports that. It doesn't replace that. speaker-0: Well said, and I think this is great, Mike. I appreciate you hopping on with me. You know, we've got a lot built up and we've got some plans as we move forward in this series. I think in our next episode, we're going to try to make things very real for some of you finance leaders out there. We're going to walk through how entropy shows up inside finance operating models. We're going to look across not only accounts payable, but we can also look across accounts receivable, procurement, treasury. mean, where it hides, how it manifests. and how to start diagnosing it. Because once you move beyond the myth of digital, you really can start seeing the system clarity. speaker-1: Once you see it, Kevin, you can actually start designing with it too. speaker-0: Well, without a doubt, that's the shift, quite frankly. Well, I think that's been great. Appreciate you hopping on with me today, Mike. All of you folks out there listening, certainly, be sure you hit that subscribe button. Love to see you at the next episode. Thanks for joining us. Y'all have a great day. speaker-1: Thanks guys. speaker-0: Thanks for listening to Xtropy OnAir. We hope you found today's conversation insightful and inspiring. Be sure to follow or subscribe so you never miss an episode and connect with us at Xtropy Advisors to continue the conversation on AI and digital transformation. Until next time, I'm Kevin Zirkel and this has been Xtropy OnAir.