Latest / Extropy on AIR: Finance Transformation, AP Automation & AI in Finance / The Speed Trap: How Growth Without Structure Accelerates Decay
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. I hope you're having a wonderful day wherever in the world you happen to be listening. I hope that y'all have been enjoying the series we kicked off several weeks ago where we were exploring the concept of corporate entropy and how to move toward more of a corporate extropy environment. Over the last few episodes, we've built the foundation. I mean, we defined entropy as really the natural drift toward disorder inside an organization. We talked about how to diagnose it. And that's going to be when you start seeing things like exceptions and identifying shadow systems and seeing escalations. And I thought it was great in our last episode, we invited Steve Ramirez to help us unpack really where it actually comes from. And that was around those concepts of fragmentation and misaligned incentives within your organization and. something we defined as corporate drift. Today I'm excited to have Mike Jasper back with us. Mike again is the vice president here at Xtropy and he's gonna be joining me as we start to talk about something that every leadership team I've ever talked about are always chasing within their own organizations. That's concept of speed. It's growth, acceleration, scaling the business, know, all those typical buzzwords that you hear quite often. Here's the tension that we wanna explore in this episode, Mike. I mean that... That same speed that often drives growth for organizations, which is so important, is the one thing that leads to corporate entropy. speaker-1: This is a kevinick where things get tricky because most organizations, they're rewarding speed and the same thing as growth, momentum. Rarely do people get praised for slowing things down. But what you see over and over again is that organizations don't always fail because they move too slowly. A lot of times they struggle because they scale faster than their system or their processes can support. speaker-0: Yeah, without a doubt. see that a lot. And that really is the idea behind this episode. We'll call it, let's call it the speed trap, if you will. It's really where growth without structure, it doesn't just create inefficiency with the organization. I'd argue that it actually accelerates decay within an organization. So maybe what we can do, Mike, is let's start here. What does growth, in your opinion, why does growth really create entropy? Because You know, when you think about growth on the surface, it should be a positive signal for a company, right? speaker-1: Yeah. I mean, growth is positive, but it also increases complexity. You know, every, every new customer, every new business line, every ⁓ &A activity, you know, these things all introduce variation to a process that, you know, has been in place for quite a while. And if your system isn't designed, if your processes aren't designed to absorb that variation, that complexity starts turning into fragmentation, which we've talked a lot about in our previous episodes, Kevin. speaker-0: Yeah, without a doubt. that growth, I mean, it doesn't create entropy on its own. Really what it does is it exposes where your system just can't handle the complexity that your, that growth is associated with it, right? speaker-1: Exactly. Most organizations grow into that complexity before they design for it. They don't feel it happening. They don't realize the scale of the, of the complexity as it continues to escalate. So they start layering processes, controls, tools, all these things on top in a very reactive manner. So instead of intentionally designing how everything should scale, they're band-aiding things as they grow that complexity. speaker-0: Yeah, and that's why things start to feel harder for lot of organizations as they do grow. It's not because their business is failing in some way, it's just that extreme strain that that growth puts their systems under. speaker-1: That's where you start seeing all the symptoms we've been talking about through the series. The more exceptions, more escalations, more reliance on those specific individuals or superheroes in the organization. More work happening outside of the standard systems, more Excel sheets, know, all those different things that a lot of our viewers are probably very familiar with. speaker-0: There's a concept, or maybe let's talk if we could about a pattern that I know we see quite frequently here on the XRP team. It's this concept of scaling before stabilizing. You we see that in our projects all the time. So what does that look like in your mind? speaker-1: To me, it looks like expanding processes that aren't fully defined. Rolling out a system globally before they're working in a local region. Adding volume to workflows that already require manual intervention. speaker-0: Yeah, so you're just scaling instability at that point. speaker-1: Exactly. And once that starts to happen, everything gets so much harder to fix because now the problem's not just in one place, it's all across the organization. speaker-0: One of the big places we see that showing up quite a lot is in a lot of the private equity backed environments that we see organizations fitting into today. mean, there's pressure to grow so quickly and they have to expand their footprint and increase their throughput. But the operating model, it just hasn't caught up yet. speaker-1: Right. And you know, the instinct is to keep moving. We'll fix it later. We'll stabilize the next phase, but in reality that rarely comes. People, you know, they go through a process and then they get back to their daily job and they just don't, they don't have the time or the energy to go back and do that stabilization. That growth keeps adding pressure to the system. speaker-0: Yeah, without a doubt. you know, over that time, I mean, that organization really becomes dependent on workarounds that they might create to try to figure out a way to just to maintain the momentum they're seeing. And that, that obviously is not, not a great recipe for success. speaker-1: No, think as we hammered home multiple times, that's the definition of entropy. speaker-0: Yeah, without a doubt. let's, maybe if we could, Mike, let's challenge one thing, and that is speed isn't inherently bad. So where does speed actually help an organization? speaker-1: think speed is a competitive advantage when your system is coherent. When the decision paths are clear, when data is reliable, when the processes are truly aligned, speed then amplifies your performance and you can move a lot faster and scale a lot bigger without breaking things. speaker-0: So speed becomes your multiplier then when you do all those things that you just mentioned. speaker-1: Exactly. the same time, if your system is fragmented, the speed multiplies that fragmentation. You get faster escalations, faster error propagation, faster breakdown in your process. Speed is really catalyst to both good and bad things in the organization. speaker-0: Yeah, and that same lever produces opposite outcomes really depending on the system in some respects. speaker-1: Right. And this is where leadership judgment becomes so critical in organizations. Because if you know when to push for speed and when to step back and reinforce the actual structure and stabilization, you're going to be a lot more successful in your goals. speaker-0: there. And, you know, quite frankly, I mean, that's that's not always intuitive for companies. mean, especially in these environments where that speed often gets tied to performance and how people are evaluated. speaker-1: Yeah, some, you know, a lot of times slowing down can feel like you're falling behind, but in reality, it's often the way that allows you to move faster later in the process. speaker-0: Yeah, without a doubt. Now this has been great so far, Mike. I just want to pause for a second though, because again, if you're listening to this and thinking, and we're growing, but yeah, you're right, things are getting harder. mean, just know that you guys are not alone in this. I mean, this is exactly where we work with organizations at Xtropy Advisors. We help leadership teams understand where their system is designed to scale or just being pushed to scale. If you could do me a favor. Go check out getextropy.com. Just go visit us on the web. You'll find a bunch of the real world perspectives that we have available on the site there that we use to help assess whether growth is reinforcing coherence or it's really accelerating entropy for these customers. you know, if this conversation is resonating for you, make sure you subscribe and share the podcast with others on your team. Each episode that we do, again, it's intended to kind of build on the last. Again, appreciate your time and attention to that. Why don't we go ahead and hop back in here real quick, Mike, as we finish off this episode. But, you know, if speed could either help or hurt, I think the real question probably becomes, how do you design for sustainable speed or velocity? What does that look like? speaker-1: Yeah, in my opinion, it all starts with a structure. You have to define how decisions are made and do that as the organization scales, not just as a point in time. Who owns that? How does information flow? What could standardize versus what stays flexible in that process? speaker-0: Yeah, so you really do need to design the system before you start pushing the system out into the user community. speaker-1: Exactly. And the second part in, in just as critical, if not more is making sure you stabilize before you scale. go through a transformation, we have a new process. We need to make sure it works consistently before we start expanding it. And that doesn't mean perfection. That just means predictability. There's always going to be the odd thing out, the exception out there, but you want to make sure the exceptions aren't the norm. speaker-0: Right. Yeah. And you mentioned that being the second, I mean, there's, there's gotta be a third following that, right? speaker-1: As you're designing, you have to build for adaptability because growth will always introduce new variables. Those could be compliance changes. That could be a whole new business line. You know, we've talked about a lot of these variables that come up in businesses and it happens more and more every day in our business environments. The goal isn't to eliminate change. It's to be able to absorb that without breaking the coherence. speaker-0: And that gets us into this whole concept of extrope and where it comes from. So great way to stay on topic as we get into this session, because know, extropic systems, don't just handle growth. They truly do improve it, right? speaker-1: Exactly. They turn complexity into a competitive advantage. speaker-0: Yeah, without a doubt. let's ground this in what we see, again, in our community. So when organizations get this right, what typically is different or what feels different? speaker-1: Well, you can see they actually move. There's some of the fastest movers out there, but the movement feels controlled. They're not having decision bottlenecks. They're not having unreliable data. There's no question about the data quality. The processes don't require constant intervention. And there's just sort of a sense of flow. This is, it almost becomes the culture of the organization. speaker-0: Yeah, it actually, it actually feels good then, right? And then conversely, what happens when they get it wrong? speaker-1: Well, everything's urgent. know, leaders are constantly involved in operational decisions. Teams are reacting instead of executing and growth just feels more like pressure instead of momentum. speaker-0: That's a great point. It's a powerful distinction right there. mean, that growth is a momentum versus growth is pressure for companies. So let's make this a little more practical for some of the listeners today. If someone's heading or leading a fast growing organization, they're trying to figure out where they're heading. What should they do? speaker-1: The first thing is have some honest conversations internally, know, off the record, no, no expectations and really try to assess whether the current system can handle more volume without increasing friction. If the answer is no, then don't scale it yet. Secondly, identify where the growth, know, growth has already introduced variability. You know, where are those exceptions increasing? What decisions are slowing down? I'd go there. speaker-0: Yeah. Well, I'd add a third thing too, is you have to make sure that you align your incentives across your organization. Steve talked about this with us last week, is you have to make sure that your teams aren't being rewarded for outcomes that are creating downstream complexity. That's a big issue there for a third. speaker-1: No, I think that's a, that's a really important point, Kevin. That's, that goes back to sort of culture and how we do this and allowing people to understand that we need to be able to stabilize before we scale. If you build that culture, it's, it's really going to grow within, within the organization. think the fourth thing is give, give yourself and give your team permission to slow down strategically. Not slow down because they're busy, not slow down because they're, they're scared, but To slow down to take a strategic pause. We're not reducing the momentum. We're just trying to take the opportunities we need to reinforce the structure. speaker-0: Great, great point. So maybe what we'll do is we kind of close out this particular episode, Mike, let's try to bring it together again for our listeners. It's good to first start with speed is not the enemy, but speed without structure is the enemy. Growth doesn't just create opportunity. It creates pressure on the system. And if your system isn't designed to absorb that pressure, entropy is absolutely going to escalate within that organization. speaker-1: Right, and when the system is coherent on the other side, speed becomes an advantage. It amplifies performance instead of amplifying breakdown. speaker-0: Yeah. And that's, that really is the huge takeaway. I sometimes the fastest way forward is to slow down long enough to design the system properly. Because once it's in place, everything else compounds, whether it's good or bad. This has been great, Mike. I appreciate you, you hop it on with us and sharing some of this insight with our listeners. again, for everybody out there, we encourage you to, Make sure you're subscribed. Make sure you know what every new episode comes out. In our next episode, we're actually going to explore why strategy dies in execution and how entropy kills it. I mean, this will help finish off what I'll call this first phase of the series, which was really intended to set the foundation and provide awareness around how entropy can rear its ugly head within your organization. Now following that episode, actually going to start into phase two of the series. We're excited about this one because now we're going to start to reframe transformation. And I know that's a big topic on a lot of folks radar right now. This will start us into shifting from reactive change to intentional design. We're going to have some more guests join us in phase two. And as always, we're grateful to have you with us along for the ride. Till then, Mike, thanks again for hopping on. ⁓ guys have a great rest of your day. speaker-1: Thanks everyone. 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.