Latest / Extropy on AIR: Finance Transformation, AP Automation & AI in Finance / Is Your System Breaking Down? 5 Signals You Can't Afford to Miss
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 again to another episode of Xtrippy On Air. We're certainly happy to have you with us today. If you recall, in our last episode, we challenged one of the biggest assumptions in transformation, and that was the idea that digital transformation is primarily about technology. We talked about how technology is actually the least important part, that it actually amplifies whatever systems it's placed into for better or worse. And we introduced the simple way to think about transformation. It was the concept of structure, system, and technology. If you didn't have an opportunity to listen to it, I certainly encourage you to go back and have a listen to that episode. This one's going to build on it because today we're actually going to move a little bit more from theory into something much more practical. Because once you understand that transformation is really about system design, the next question becomes, how do you know when your system is breaking down? And more importantly, how do you see it before? it turns into a crisis. Have Mike Jasper joining me again today as we continue to walk through this series. So welcome, welcome. Good to have you on board today, Mike. speaker-1: to be here, Kevin. And yeah, that's an interesting question that you posed because most organizations don't think they have a problem until something really visible happens. I've seen this take many different forms. It can be a failed implementation. It could be a delayed financial close period. I've seen major audit issues spark this realization. Even something like a major customer or supplier escalation. that starts getting executive attention. Those tend to be some of the signs that we've run into that entropic process we talked about before. speaker-0: And that's going to be the key for today. mean, entropy doesn't show up all at once. It does show up in patterns. And once you know how to recognize those patterns, you can start to see it break down before it starts to hit your own organization. Maybe what we do, Mike, let's start here. If entropy leaves signals, why do most organizations miss them? speaker-1: Most of the time these don't look like problems. They look like day to day work. A lot of times these signals can look like your team is being resourceful or just trying to figure things out. speaker-0: And honestly, I think that's what makes this so tricky. know, entropy, doesn't feel like failure. It does feel like effort. mean, people are busy. They're solving issues. They're getting things done. But the system itself is getting harder to operate. speaker-1: Exactly. That's where a lot of this gets hidden is that organizations want their people to be busy. And a lot of times teams tend to want to hide that friction from leadership. That means that leadership typically sees the outcome, but they don't necessarily see all that friction that's happening to get to that outcome. They see the transactions are being processed. They see that reports are getting delivered, deadlines are being met. At the surface, everything seems fine. What they don't see is how much manual intervention it takes to make all that happen. speaker-0: that gap, that invisible effort, if you will. It's where entropy lives within these organizations, right? speaker-1: Right. And most organizations either can't or don't measure it. They, they focus on measuring the outcomes, things like throughput, cycle time, cost. What they're not measuring is how much rework went into that deliverable. They can't really measure how much time was spent on exceptions. They might be able to see how many exceptions there were, but getting down to how much time did the team take, that takes a whole different way of looking at it. And they also don't measure that decision friction. speaker-0: Yeah. Or, or trust. mean, which is a big one because once trust in the system starts to erode, people start creating all their own versions of reality, right? Let's kind of make this really tangible, if you will. If I'm a leader listening to this inside of an organization out there today, what should I actually look for? What are the most consistent signals that entropy is already present within my own organization? speaker-1: Yeah, that's a good question, Kevin. I see five signals that I typically look for. The first is what I call exception dependency. So what this means is on paper, the process is automated. In practice, the actual process is much more complex than what was actually documented or automated to begin with. That means the automation only works in ideal conditions or the processes that were defined on that paper. Anything outside of that standard flow requires manual intervention. speaker-0: Yeah. So the system works until it doesn't work. speaker-1: Exactly. And over time, those exceptions become the real process. know, things evolve and the process doesn't meet those additional exceptions. And so you start seeing, you know, you start seeing that become larger and larger of an issue until it finally rears its head. I think that the second sign I look for is shadow systems. You know, if organizations have invested a lot of money in doing a transformation, And then you start seeing additional systems or spreadsheets and things pop up. That's usually a red flag for me. And that really means that the team doesn't fully trust the system of record or the system of record doesn't follow their process that they need to do in that scenario. So they start building parallel processes and parallel tracking, know, spreadsheets, side reports, offline workflows, emails, team Slack. groups, all those are signs that something's broken in your transformation. speaker-0: Yeah, and we've both seen those in real organizations where real process, it still lives in Excel. It's not that platform that they may have invested millions implementing. It's kind of comical in some instances. speaker-1: You know, and that's, that's one of the things I do when I go talk to a new company for the first time is I just start looking at how many spreadsheets that they, that they actually keep, you know, by user, by group, by location. It's a lot more common than you think. It's a lot harder to identify because that offline process is using a new system. It utilizes some or all of the automated process. So it's, it kind of hides itself in plain sight. ⁓ It's not. because people want to work that way. It's because the system doesn't reflect how work actually happens. The third signal I usually look for is decision escalation. And this one, one can be a big tell of how the process is really working in your transformation. If you start seeing decisions that should happen at one level, but they're consistently being pushed upward. people don't feel comfortable making a decision, they want their manager to sign off on something. It's not because those leaders want to be involved in those decisions. It's because people are hesitant to take ownership. It's either because the decision's not clear or the data is not trusted, but that tends to pop up more often these days. speaker-0: Yeah, I think in that scenario, your leaders then, really are just becoming an integration layer in the process. speaker-1: That's a great way to look at it. And that's not scalable. So the fourth signal I look for is metric conflict. So this one, you've got different parts of the organization who are optimizing different things and those metrics aren't aligned. So in some cases, they even conflict directly. speaker-0: Yeah. And we see that way too often. You get situations where one team is technically very successful in what they're trying to measure, but the overall outcome, it's actually worse for the company as a whole. speaker-1: Right. And if you watch it at a macro level, you see quarter over quarter, one department's KPI is improved, the other's a decline. And then you focus on the ones that declined and improve those, the other department declines. That means that something's not aligned. The fifth signal I look for is hero dependency. And this one's tougher because every organization has their rock stars. We can't live without them. They're invaluable to our organizations. The system works because certain people know how to navigate it. They know all the workarounds. They know who to call when something's wrong. The issue though is that tribal knowledge tends to decay over years and that's through team turnover, promotions, people transferring, people coming and going from the organization. That leads to a slow loss in that knowledge. Eventually things start breaking as that knowledge deprecates. speaker-0: Yeah. And again, we see that all too often and you know, any listeners, you're sitting in an organization today and you've got that one person that you're afraid to let them go on vacation or they happen to be out sick because every time they do something breaks down. What that really means is your system isn't working. It's a couple key people that are working and that's, that's not going to be sustainable for you. Let's go a level deeper here, Mike, because It's easy to hear these and think, yeah, we have some of that, but not fully appreciate what they're signaling. So take shadow systems, for example. I mean, what's really happening when teams start building their own tracking systems or metric systems outside of whatever the core system happens to be. speaker-1: Yeah, typically they're compensating for a gap in the system or in the process. So either the system doesn't reflect reality or the data is not reliant. ⁓ It could also be the process doesn't support how all the decisions actually get made. You know, we may have tried to follow the 80-20 rule and actually came out to the 60-40 rule where, you know, we've got a good amount of automation, but we also have a lot of areas where things aren't being automated. The other root cause there might be that the process is unnecessarily complex. So, you know, we've tried to over-engineer things to get the 100 % scenarios. So people create their own version of it for control. speaker-0: Yeah. And we all know once that happens, you've effectively lost that, that single source of truth that hopefully you would have within the organization, but ultimately end up not. speaker-1: Yes, you have. And the issue is that cascades because now different teams are making decisions based on different goals, different datasets. And that's where the alignment starts breaking down. speaker-0: What about the exception dependency? Because that one does tend to get normalized a lot of times in companies. speaker-1: Yeah, organizations get used to it. They say, well, of course there's exceptions and they're right, but when exceptions become a significant percentage of the workload, they stop being an edge case. That's the system telling you it wasn't designed for real world visibility. speaker-0: And that's, that's every organization. So let me pause here real quick, Mike, and just remind some of our viewers. If you're listening to this and recognizing some of these patterns, that's actually a really important step. And it means that you're starting to see your systems a little bit more clearly. If you've been following this series of episodes, we encourage you to share this with some others. And also remember at Xtropy Advisors, this is exactly where we spend a lot of time. We help leadership teams identify these signals early. We help them understand what what they're pointing to. So certainly encourage you to go take a look at getextrapy.com. Learn how we can help you assess some of these systems in a very structured way. We can help you start pinpointing where your operating model may be losing some of that coherence. As I mentioned, if this is resonating, subscribe to the channel here, share this podcast with some of your coworkers. Again, as we continue through this, you're going to find Each episode that we do is really going to build onto the next. We hope you're going to get some meaningful insight from it. With that, maybe let's hop into diagnosing how some symptoms really get misinterpreted sometimes within companies. Here's something that I see all the time. Organizations might recognize these symptoms, but they interpret them incorrectly. They see exceptions and think, man, we need some more automation. Or they see some of these side shadow systems that they start to develop and think, man, we just need some better reporting. Why does all of this tend to happen within companies? speaker-1: I think it's because the symptoms typically feel like isolated problems. When something feels isolated, the instinct is to try to put a targeted fix on it. But in reality, these aren't isolated issues. And we may see one at a time, but really there's five, six other symptoms underlying that we're not seeing initially. And those are all signals of something deeper. speaker-0: Yeah. Instead of then reducing the entropy that obviously they're trying to do, they really just end up redistributing it to another part of the organization. speaker-1: Exactly. They solve for one symptom locally, but the system as a whole becomes more complex and over time that complexity compounds. speaker-0: Let's figure out what we can do next. What does a better approach look like, Mike? How should leaders be thinking about diagnosing entropy within their own firm? speaker-1: first thing to do is make a conscious shift from problem solving to pattern recognition. Don't just ask, how do we fix this issue? Start asking internally, where else do we see this pattern? speaker-0: I think that's going to be a big shift for a lot of companies because it forces you to look across the system and not just within a single function, which I think too many leaders, particularly today, start to look at things functions by functions instead of across the entire ecosystem. speaker-1: I think the second thing is to treat these symptoms as signals, not just inconveniences or tactical issues. Every workaround, every escalation, every shadow system, they're telling you something about how the system is designed. speaker-0: just add a third to your points here. You really need to resist the urge to just jump straight to the solution as well. Because until you truly understand where these symptoms coming from, you do risk reinforcing the problem if you just try to deploy automation or technology on top of whatever currently is sitting there today. speaker-1: think that's the key, Kevin, is you want to do a thorough diagnosis before you ever start designing. speaker-0: I know one of the things we've been doing in this series is trying to keep it as practical as we could, you know, talking about what can I do as a leader sitting in my seat today that's going to help my business next week. So as we've talked about some of these topics today, what should leaders look to do starting tomorrow or next week within their own organization? speaker-1: I think the biggest key is to start simple. Take one process that can be in your accounts payable, accounts receivable, procurement. It doesn't really matter. Just pick one process within those groups. Ask the team, ask everybody that touches that process three questions. Where are we relying on exceptions? Where are people working outside the system? Where do decisions get escalated unnecessarily? speaker-0: Well, I would say after you asked them to don't fix anything yet. I mean, just observe, figure out what your answers are to those questions, because the goal at this stage is really just the visibility. speaker-1: Exactly. It's that pattern recognition, you know, understanding what's the real root cause of these issues. Once you can understand those patterns, you're in a completely different position. speaker-0: Yeah. So that ought to be a good lesson for anyone listening here. Again, we've asked you to do absolutely nothing. This should be the easiest takeaway from any episode that we have. It's just observed. Let's bring this together if we could. I entropy doesn't show up as a single event that we've talked about. It shows up as patterns. It's those exceptions, the workarounds, the escalations, the misalignment, the hero dependency on those hero individuals that you mentioned. And over time, those patterns compound into breakdown for organizations. speaker-1: They do. And if you know what to look for, you can start to see it early. And that's where transformation really begins and where transformation and success is ensured. speaker-0: Yeah, without a doubt. Well, one of the things we're actually excited to bring to you guys in our next episode, we're going to answer the question we've intentionally held back on today, and that is, where does this actually come from? We talked about a lot of the symptoms, but we didn't talk about where it actually came from. These symptoms, they don't just appear randomly. They come from specific structural conditions that exist inside the organization. It's fragmentation, it's silos, it's the concept of drift. And what we're going to do to make this real, we're actually bringing in someone who's lived this from both sides. This is actually someone's on Mike's team. A gentleman by name of Steve Ramirez is going to be joining us. He's one of the senior leaders on our delivery team who's actually experienced this as a client before he worked at Extrapiece. We're really excited to bring Steve into the mix next week, Mike. speaker-1: That's going be a really great perspective for us and for the audience because his experience isn't theoretical. It's day to day. speaker-0: He's been through what organizations are dealing with every single day. So we're excited. I hope you guys will tune in for that episode until then again, Mike, thanks sir. Thanks for joining me today. Again, certainly appreciate all the listeners. Don't forget to that subscribe button. We'll look forward to seeing you next time on XTP OnAir. Thanks for joining us. 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.