Latest / Extropy on AIR: Finance Transformation, AP Automation & AI in Finance / Fragmentation, Silos, and Drift: Where Entropy Comes From
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. Appreciate you guys joining us. We are really excited about this episode. We're going to be continuing with a series we've been working on for the last four weeks. In our last episode, we talked a lot about how to diagnose entropy within an organization. We walk through the signals, the exception to dependencies, the shadow systems, the escalations, metric conflict, hero dependency, all the things that we've talked about to date. We made a point to stop short of something intentionally. We didn't answer where these systems come from. Because today that's going to be the focus for us. Where does entropy originate inside of an organization? Why does it show up even in companies that are traditionally well run, well intentioned and actively investing in transformation? To make this real, I wanted to bring in someone who's experienced it from both sides of the equation. That's why I'm excited to have Steve Ramirez joining us today. Steve is part of our delivery team, of our senior managers here at Xtropy. But before that, he was actually on the client side. He was leading through these exact challenges, including a P2P transformation journey that we were involved in. Steve, really glad to have you on the ⁓ episode today. Thanks for being here with us. speaker-1: Yeah, glad to be here. And I'll say right up front, right? Everything you've been talking about in this series, I've lived it. At the time, I wouldn't have called it entropy. I would have said, this is just how our business works. And I think that's part of the problem. speaker-0: Yeah. And you wouldn't be the only one to not call it entropy. I know that's concept we're introducing to a lot of the listeners. Maybe why don't we hop in, Steve, and let's start with this concept of silos within companies. Because they're usually talked about like they're a leadership failure or some cultural issue within a company. I would say in reality, they form pretty naturally. So maybe from your experience, if you could kind of walk us through how you see silos actually showing up within your organization. speaker-1: Yeah, they don't start as silos. They start as solutions. Team has a problem, they fix it. They improve their process. They implement a tool. They define how they're going to measure success. And it works for that team. speaker-0: Yeah, that's actually an interesting point. what you're saying here, silos, they're often a result of success within a company, right? speaker-1: Exactly, exactly. Nobody steps back at that point and says, okay, how does this impact the rest of the organization? Because in the moment, you're solving a real problem. speaker-0: You're, you're, truly doing the right thing for the company, right? speaker-1: Right, right. But then another team does the same thing and another. And over time, those decisions, they start to diverge. Processes don't line up anymore. Data definitions aren't consistent. Systems don't integrate cleanly. And eventually, you don't have one operating model anymore. have multiple. speaker-0: Yeah, and that's the problem. And that's really when things start to feel a lot harder within these organizations. It's not because any one piece is necessarily broken. It's because the pieces just aren't fitting together quite right. speaker-1: Exactly. It's not one big issue. It's lot of small misalignment. speaker-0: And it seems to be that way for a lot of problems. Maybe what we can do is let's dive in just a little bit deeper because silos, they don't just form structurally. They're typically reinforced by some type of incentive within an organization. How did that show up in your experience working in industry? speaker-1: Incentives are probably one of the biggest drivers. Every function is measured differently. Procurement, you know, they're focused on cost savings. AP focused on efficiency. Finance focused on accuracy and control. And those are not bad goals, but they're not always aligned. speaker-0: Yeah. And when you, when you have that, I mean, you could actually have a situation where everyone is succeeding, but they're succeeding just individually, right? speaker-1: Yeah, but the system is underperforming. Exactly. I remember situations where procurement would negotiate terms that made perfect sense from a cost perspective, but those terms, they might've created complexity downstream in AP. And then AP had to build these workarounds to be able to deal with it. speaker-0: Yeah, that's, that's interesting. Those cost savings upstream, they end up almost creating some friction downstream in the process. Right. speaker-1: Right, and nobody was wrong, right? That's the important part. These weren't bad decisions, they were uncoordinated decisions, I'd say. speaker-0: And I'm glad you mentioned that because that's a really key distinction. mean, entropy isn't driven by poor execution all the time. It's driven typically by, how do want to phrase it? Misaligned success. speaker-1: Yeah, that's exactly how it feels when you're inside of it, right? You're doing what you're supposed to do, but the outcomes, they don't quite line up. speaker-0: Yeah. know, one concept I wanted to get into is this whole idea of drift versus kind of deliberate change. So let's maybe spend a couple minutes talking about that. I wanted to start with drift first, if we could, because I think this is one of probably the least obvious, maybe the most important concepts in all of this. Kind of in your words, can you walk us through the difference between kind of that drift versus deliberate change concept? speaker-1: Yeah, deliberate change is planned. You define a future state, you align people around it, you implement something new. Drift is what happens in between those moments. It's the accumulation of small decisions that aren't coordinated. speaker-0: Okay. So it's so that drift, it's not a recurring theme, but it is kind of happening all the time, right? speaker-1: All the time, yeah. And the problem is most organizations don't manage drift, right? They manage projects. So you have these moments of intentional change and then these long periods where the system is just evolving on speaker-0: Yeah. And I would imagine during those periods, mean, things really start to diverge at that point, right? speaker-1: Exactly. Yeah. Processes start to get adjusted locally, know, workarounds get introduced, new requirements get layered in, and none of it, again, is necessarily wrong, but over time, the system moves away from whatever it was originally designed to be. speaker-0: Okay. So I would say then by the time you start to see the symptoms that we talked about in our last episode when Mike and I were talking about exceptions and shadow systems and escalations and things like that. I mean, the drift, it's probably already happened at that point, right? speaker-1: Yeah, yeah, you're reacting to something that's been building for quite some time. speaker-0: Yeah. Well, one of the things I like to do for our listeners is try to bring a little bit of a real world into this. So if we could, let's make it real just a little bit for them. So when you were on the client side before working at Xtropy, what did this actually feel like day to day as you were living it at the time? speaker-1: Um, it, actually felt like things were getting heavier, you know, not, not overnight, just gradually. Processes took a little bit longer, more exceptions showed up, more people needed to be involved in decisions. And you don't immediately connect that to a system design, but you think just need to tweak this, you know, out of step, out of control, you know, add a report. speaker-0: Yeah, that sounds like you're solving things very locally at that point then, right? speaker-1: Exactly, exactly. every fix makes sense in isolation, but collectively you're adding complexity and eventually you reach a point where everything just starts feeling harder. speaker-0: I got to imagine there's some listeners that are feeling that today as they kind of go through their daily life. So what I'd like to do if I could, Steve, just want to pause here for a second because to our listeners, if this starts to really sound and feel familiar for you, it's because it's incredibly common. I mean, this is exactly where we spend time with organizations that extropeat advisors, helping leadership teams really step back and see how fragmentation. incentives and drift or shaping their overall operating model. So I would encourage you all, if you are listening and you get a few minutes, go to getextrapeed.com. You'll find examples and real world perspectives that can maybe help you start identifying where some of these patterns exist within your own organization. If this conversation is resonating with you, make sure to subscribe, share this podcast with others on your team. Again, each episode that we do is designed to build on the last and we certainly love having you here with us. Wanted to just take a quick break and remind all of our listeners of that. With that Steve, let's go ahead and hop in. I wanted to talk about a little bit different concept. So once you see fragmentation starting to set in within an organization, the natural instinct is centralized. We've got to centralize, standardize everything, pull control back to the center. But that doesn't always work. speaker-1: Now because centralization solves for consistency, but it can create rigidity. And if you over-correct, you end up slowing things down in a completely different way. speaker-0: Yeah. ultimately you could trade one type of friction for another type of friction in that instance. speaker-1: Exactly. What you actually want is coherence, right? Which is different. It's not about making everything the same. It's about making everything work together. speaker-0: Yeah. And that's a really important distinction. And I love that word. Obviously it's one of the big concepts of the series here. I think the answer really is alignment. You've done great hitting on some of that already. speaker-1: You need to be very intentional about where consistency matters and where flexibility is actually valuable. And that requires understanding the system as a whole. speaker-0: Yeah. And that whole concept of coherence, really is a choice. So let's kind of bring this back to that bigger idea. know, entropy comes from fragmentation and misaligned incentives and the drift that we talked about. Then extra P must come from something else. And I'm not talking extra P advisors here. I'm talking the term extra P. has to come from something else, right? speaker-1: Yeah, yeah, it comes from intentional alignment, right? From actually designing how decisions connect, how information flows, how teams interact. And I'll say this from experience, that's not something that just happens, right? You have to choose it. speaker-0: Yeah. And really that needs to be the takeaway. I coherence, it is a choice. It doesn't emerge naturally as organizations grow. It has to be designed. And more importantly, it has to be reinforced. speaker-1: Yeah, and once you start looking at the organization that way, everything changes. You stop solving problems in isolation and you start asking how everything fits together. speaker-0: So from your perspective, Steve, if we were to make this kind of practical, if someone's listening to this and recognizing these patterns within our own organization, what advice would you have for them? What should they be thinking about next? speaker-1: I would say first look for where your organization has evolved independently. Where have teams made changes without coordinating across the system? Second, look at incentives, right? Where are teams being rewarded for outcomes that create friction elsewhere? speaker-0: Yeah, we talked about it already. mean, third, they need to identify that drift as well. Where does your current state differ from what was originally designed, right? Yeah. speaker-1: Exactly. And fourth, resist the urge to immediately centralize everything, right? Focus on understanding the system before you try to fix it. speaker-0: Yeah. Now that this has been great, Steve, I certainly appreciate your insight in this. Just wanted to bring this together again for the listeners. Entropy doesn't come from one big failure. It does come from fragmentation. It comes from the misaligned incentives that you talked about. It's drift over time. You know, quite frankly, these forces are present in every single organization that we've seen. speaker-1: Yeah, but coherence is possible, right? If you're intentional about how the system is designed and how it evolves. speaker-0: Yeah, I think that's great. Steve, again, thank you so much for joining us, taking some time out of your day from helping our customers in their day-to-day journeys to share a little bit with the audience here. This is going to be a great lead into our next episode. I'm going to have Mike Jasper join me again next week, and we're going to take a look at the next step. We'll move from understanding where entropy comes from to what it actually looks like to design for coherence across core, what I call financial processes within your organization. Because once you understand the source, you can really start designing that solution. speaker-1: Yeah, and that's where things really start to change. speaker-0: Yeah, couldn't agree more. Well again, Steve, thanks so much for the time. Appreciate it. To our listeners, appreciate you sticking in with us ⁓ this week. We'll look forward to catching you next time. We'll see you around on Xtropy on Air. 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.