Latest / Digital Leaders Club By Ingeno / Matthew Jacobs, Chief Product Officer at Scrum Inc. | Defense Innovation & Organizational Change
Transcript
- Ingeno: Hi and welcome to Digital Leaders Club. I'm Guillaume Chenou from Ingenno. show is built for the leaders running real-world operations, and today that means the people working inside one of the most significant ⁓ modernization waves the sector has seen in a generation. I'm joined by Matthew Jacobs, Chief Product Officer of Consulting at Scrum Inc., the firm founded by one of the co-creators of Scrum, Dr. Jeff Sutherland. Matt, welcome to the show. Matt Jacobs: Thank you very much for having me. Excited to be here. Ingeno: Alright, alright. So before we get into because you work a lot with defense right? So before we jump into that, how you end up ⁓ doing with defense in general in in a let's say agile consulting company like yours? Matt Jacobs: Yeah, it's a really interesting question. So I'll talk a little bit about the history of Agile and defense. then I'll talk a little bit of how we ended up playing kind of a large position within that. So one of the first things that's like really interesting is Agile was really kind of born within defense, a lot of the concepts. So Dr. Jeff Sutherland, our founder, was an F four phantom pilot in Vietnam, a West Point graduate. So a lot of the early ideas that started to formulate in Scrum, and being a fighter pilot, John Boyd goes back into his history, who is one of the greatest fighter pilots of all time, who defined things called the OODA loop, which was observe, orient, decide, and act. And one of the things Boyd decided or determined it wasn't the best pilot with the best machine that would win in a dogfight, was a person who could make decisions faster than the enemy could react. And then they could drive the course of the engagement. You hear this all the time as a sports analogy of you want to play your game, not the other person's game. That's an example of being inside of someone's OODA loop. As he kind of moved into industry, he took a lot of those thinkings from defense, combined it with his study of microbiology and his medical research background, and then was actually working on the original. ATM network rollouts, which actually has a very symbiotic relationship to how a cancer cell would spread in a human body. How do you think about network theory? So all they did is they were working on these complicated topics, is spend a lot of time looking at the research of what makes a really effective delivery, bringing in their own experiences, such as Jeff's being a pilot. And then in each time box, because a sprint didn't exist because they hadn't invented Scrum yet, how could they get better? And these ideas started to build on themselves and were really research based from the very beginning. Today, now if you look at kind of Agile and Scrum in Defense, there's thousands of US Scrum teams really focused kind of at the individual team level. We were invited to Ingeno: Hmm. Matt Jacobs: Kind of the UK to run a workshop to look at how could they write policy in a much more agile way? That little workshop. opened up a huge opportunity because they wrote that policy in a really different way. So instead of sitting there and trying to write thousands of pages and hiding kind of the defense strategy from everyone until it was unveiled, they actually wrote a framework for it. Like what would this thing even be? And they started shopping around with customers, what you like, what what jives and getting feedback. Then they started building out the individual pieces, constantly getting feedback from within their organization. from the perspective customers. So by the time this thing was written, it was immediately well received and accepted because everyone already knew what was going to be in it. It already had the customer's perspective built in. because they built it from a framework to the pieces out, getting constant feedback along the way, it wasn't like they dropped the entire thing, got feedback and then had to rewrite it. They were able to adapt and evolve it with much less effort. Ingeno: Hmm. Matt Jacobs: Over the entire course, and like most strategic reviews where teams spend months kind of working on it and then spend four weeks crammed into a dark room in a small team trying to get it done because like the timeline's approaching, they were able to work on this actually in more of a flow-based manner and a continuous level of effort. That got the Navy thinking, the British Navy at this point in time, how would this apply to other types of work? So that kicked off actually a larger kind of agile transformation. Within the British Royal Navy. One of the things that I think is really interesting as a non-defense focused business defense itself is very much a network because of the staff rotations. And you didn't really need like a go-to-market commercial strategy. People who had positive experiences working in a different environment. due to their staff rotations, would come to a new environment and see the immediate applicability and want to bring it with them. So you actually got this very natural kind of expansion of Agile within the UK Ministry of Defense. Ingeno: So it ⁓ sounds like s ⁓ firm was kind of born in defense ⁓ An accidental with firm that was in defense and then you grew up there. It seems like it was ⁓ in the beginning of of the the firm, right? Matt Jacobs: Yeah, and a lot of the ideas if we continue to expand on kind of like agile and defense that are core components, like small cro multidisciplinary teams, like that is a very defense way of operating. If you look at every special forces team, command intent, which is I'm gonna give you an outcome, you figure out the how and you need to be enabled to do that because the complexity and involving situation kind of in a battle space is Ingeno: Mm. Matt Jacobs: So complexity, I can never tell you exactly how to get something done. You need to trade space to adapt as you go. And the entire idea of servant leadership also comes to defense. And the entire and the idea of mission command of what can I do as command to enable you to do your job? These are all very defense-focused concepts. What I think is really interesting is a lot of these concepts are really embedded into the normal ops rhythm of operations. But not actually how they survive and operate kind of on base or on the business side of defense. And that's where we see kind of the biggest piece of opportunity. But for years, we didn't play very much in the defense space. And kind of defense was, I think you could argue to use your own terminologies, calling us back home because there's such a emotional kind of connection at that level. Because a lot of people who are used and really enjoyed the way. Ingeno: Hmm. Matt Jacobs: They would operate on operations and we're trying to recreate that feeling and how do they do b defense. So they saw Agile and were like, Wait, that actually feels really natural to me. Ingeno: Hmm, nice. so ⁓ tell me now ⁓ our listeners too ⁓ about Scrum Inc. ⁓ your role at the company. What do you do exactly? ⁓ your website ⁓ it a boutique boutique consulting firm focused on end-to-end transformation. ⁓ So that ⁓ what that mean ⁓ from day-to-day perspective ⁓ and that ⁓ how it serve the the bigger mission? Matt Jacobs: Yeah, so we were founded originally to help people work with Jeff Sutherland to kind of go back to the roots of like really what was Scrum. There's a lot of bad Scrum information out there. When sometimes I say work for Scrum Inc., I always pause for a second to see how the person they either react really excitingly, like, I've been on a Scrum team, I love that, or my god, don't talk to me about Scrum. There's just Ingeno: Ha ha ha. Matt Jacobs: And I totally get it. Like if you just follow sheepishly all the processes, or worse, like forty percent of the processes with no idea of the outcome, it can have a really negative effect on the team. That doesn't mean there's something wrong with Scrum, because there's a big difference between strategy and execution. ⁓ a lot of times I would say the issue is actually not the strategy being the issue, the execution of how it's applied is the issue. Ingeno: Mm-hmm. Matt Jacobs: But if we look at kind of Scrum Inc. though, it evolved very much to be actually back to the routes of like what Jeff was doing in the beginning, which wasn't trying to make Scrum teams. He was trying to deliver effective product. So as an organization, we're really focused on creating the world's best delivery engine for your organizational strategy. Scrum, agile concepts, user-centered design, it doesn't matter. Those are tools in our quiver. They're never really the point. Ingeno: Mm. Matt Jacobs: No organization wakes up one morning and says, We want to be the most agile organization in the world, and that's our goal. Like, no, they want to Yeah, it's a it's a Yeah. And I think in a lot of these failed transformations, it became the end point in the way people were talking, and then it ended up becoming the end point, and people totally lost track of Ingeno: That's a means to an end, right? It's a means to an end, it's not the end itself. Matt Jacobs: What was their original why? Why do they care about this? What they were trying to do? So we work with a lot of organizations to deliver their strategy. And when we're working with everyone, we spend a lot of time coming back to will this thing help us deliver? Or do we think this thing will help us deliver? To keep reminding people, the goal of your transformation isn't the transformation. The goal is to be able to do something. And I think the same issues happen every day in digital transformations as well. like, ⁓ the goal is to Use AI more. That's not the goal. Ingeno: Nah, that's not a goal. I agree, I agree. So Matt, tell me, the part of your work right now that ⁓ ⁓ most proud of? ⁓ Something ⁓ team has built or some you've delivered with your customers. So tell me about that. ⁓ Matt Jacobs: Yeah, so I think one of the things that we've really been looking at and defining as we've been working with organizations on transformations, we realized one of the reasons why we were more successful, and this wasn't necessarily intentional, it was just based on our training, is we took a really agile approach to the way we do transformation. We're not gonna pre-plan the entire organization. try to move the strategy around and then maybe at the end even look back to see what we accomplished. No, we're gonna try to take a very experimental like human beings are complex creatures. Then you add the complication and system dynamics of lots of human beings working together. You cannot simulate that. We can actually come up with good concepts, but we don't know until we do something. So how do we actually take the transformation and deliver it In incremental bits where we're learning and adjusting bases we go. This led to the kind of the idea of the continuous transformation. If you look at a lot of the agile, especially scaling frameworks, they always have this built-in continuous feedback loop built into it. If we're doing that really well, we get into a cons a state of constant evolution instead of going from transformation program that was partially implemented at best five years later, ⁓ upheaval. transformation, why don't we get into a state where actually bottoms or edge out feedback is getting fed back to the center of the organization. So the organization is continuously evolving. This has led to I think a concept that's really been interesting is all right, what is allowing us to approach the transformation in an agile way? It's actually this further step in logic, which is your organization itself is a product. Ingeno: Hmm. Matt Jacobs: So who's in charge of that product? How do we use the leading product thinking to design our products? And a lot of times we're helping an organization do what I would call a full stack transformation. And what that means is let's think about this from kind of goal down. So like what is the organizational strategy? If I cannot, if that's not well defined, I can't design an organizational transformation about how we operate, because I'm designing how I operate to lead to some sort of outcome. So the first piece you gotta really nail down is like why does the organization exist? Ingeno: Yeah. Yeah. Matt Jacobs: Now I can actually build a product structure of like these are the products and then map an organizational structure that mimics the products we're trying to build. So like taking that Conway's view, but into the organizational design up front. That's my hardware layer. And we're drawing a lot more organizations like system schematic diagrams because actually they start to map really nicely on top of each other. Now I've got to lay a software layer over, which is really like like governance and process and how do I maintain the minimum viable amount of that. Because the real power is now where the edge compute is, which is actually the ways of working at the team level and the individual level. Ingeno: Hmm. Matt Jacobs: Then finally, underneath that, I've got I need enabling technology and culture. And what's interesting is if I have an issue at any layer within that continuum, I should look one layer up for what the root cause is. If I have an issue at culture, I shouldn't try to change culture. I think that's a fool's errand. It's like pushing against a rope. It will keep bending and shifting. I can't tell people to be more collaborative. What I can do is look at, all right, what's in the system that's driving that behavior? Ingeno: Mm-hmm. Matt Jacobs: And then adjust the system to get the culture that I want. So I think this idea of the full stack transformation and treating your organization like a product has actually a lot of levers that we haven't fully even pulled on or fully discovered yet. But I think there's a lot of power in getting organizations to realize that that their organization is a product and someone needs to own it. And then they can apply a lot of these leading thinking practices to their own organization. Ingeno: That's that's super interesting. you know typical ⁓ after for me and you can sur ⁓ surface it, but what's the part of eating transformation, especially in defense sector. You know in the US, ⁓ we're in Canada, so in Canada what we see is that ⁓ ⁓ sector is super behind in terms of technology, modern technology adoption adoption and AI. Maybe can tell us ⁓ about ⁓ on the south part of border. but you know so what's the hardest part ⁓ when you are front of ⁓ maybe let's say ⁓ more conservative organizations terms of technology adoption. ⁓ Matt Jacobs: Well, I think the hardest part is the question, like, well, how do you know? Bring me more data, bring me more scenarios, bring me more support. They want a level of definition and proof that everything you're going to do is going to work. What I find ironic about that point of view is they fundamentally already agree with what they're doing does not work. So the threshold is actually quite low. It's like, do we think this could be better? And what is the safest level test we can do to see if it's better? So I think the hard part is dealing with the uncertainty. Ingeno: Mm. Matt Jacobs: When you talk about technology adoption, one of the things I find very ironic, and I know this to be true kind of in Canada as well, there's like pockets of extraordinarily advanced things going on. And like the government has some like amazing technology doing totally edge breaking stuff. Yet to like get on a base, like someone is like hand scrolling through a thousand line Excel trying to look people up. So like Ingeno: Mm-hmm. Matt Jacobs: There's a paradoxical problem that exists that I'm not actually fully sure of what the root cause is, but I have a feeling a lot of it has to do with this like demanding to know and be comfortable up front with the accountability standpoint of it's public funds. In a business, you've got a revenue line and a cost line, and I can tell you, like, if a Ingeno: Mm-hmm. Yeah. Matt Jacobs: Product line area wanted to make this investment, and they said in two years that they think it would do X. I know that for sure. One of the problems in government, and I think especially in defense, if you're not actively in a war, is how did you really know you increase the outcome that I've increased government Canada's as an apparatus? It's very, very hard to do. So you get this very status quo bias. Ingeno: Mm. Yeah. Matt Jacobs: Because you also cannot get fired for maintaining the status quo. Ingeno: Yeah the the KPI to measure outcome is hard to it's not just it's not dollars, right? It's something else. Right? Yeah. So yeah, yeah, yeah, exactly. Matt Jacobs: Yes. And dollars are very easy. Cost is very easy. Measuring total defense, very hard. Ingeno: Absolutely, absolutely. So the US, in Canada at our our own scale, so investment ⁓ in defense is Like billions and billions are now injected in defense. so from you sit, what genuinely changing inside the defense Matt Jacobs: So both in the UK, where I spent a lot of time in the US, they're very much aligned and starting to make this transition that industry started making probably in earnest ten years ago, and it's actually still accelerating to today. This like idea of transitioning from project type thinking to product type thinking. So if you look, the US just kicked off the warfighter acquisition system transformation last year. Ingeno: Mm-hmm. Matt Jacobs: Which is to collapse a lot of that value stream of capability development together. Stop funding huge programs that may deliver in 10 years, but like how do you fund the next piece and then the piece after that to field capability quicker? And both governments are talking a lot about speed. Need to get speed of capability to the warfighters' hands so we know that this stuff is working. The problem is you're pushing against 50 plus years of conservatism. Where the answer is I'd rather deliver something big once in 10 years and make potentially a massive risk at the end instead of taking lots of micro risks throughout. So I think that's kind of the big push of like how do I move from project to product or capability type thinking? Which then starts to open other doors. Both the US and the UK are very interested in the idea of a portfolio. The second I go from thinking about Ingeno: Mm. Matt Jacobs: individual programs to a portfolio of programs and capabilities is I could invest in three things that do the same thing very intentionally and then choose the one that works best. Or I can allocate to all right, where's the biggest need now? Instead of having every program individually treated like that is the program in isolation that needs to be funded to be able to get to the end. So even this like Portfolio level thinking gives you a lot more options to be like, actually, there may be multiple ways to solve from getting quite literally from point A to point B in a contested environment. I could fly, I could drive, I could barrel underground, maybe I could teleport. But if I actually own that portfolio of moo troop movement, I have the ability to flex up and down based on what we're learning. If I treat all of those like independent things from each other. I may actually be invest continuing to invest in path B, C and D that are just no longer needed. Ingeno: So you mean by that, like ⁓ more on the outcome rather than on the work to be done? ⁓ is that kinda ⁓ Matt Jacobs: Yeah, very much so. Like why deliver and there's like failed technology investment after failed technology investment in the UK and the US and I assume Canada, these big programs that didn't deliver or they delivered exactly what they said they were gonna deliver, probably laid in over budget, but we'll ignore that. But then like it hit the warfighter and they're like, I don't want this. Or I wanted this ten years ago, I no longer need this. So thinking much more of like how do I get to speed, how do I get what we need now? Well, keeping an eye kind of out on the future, and what's what's the problem we're trying to solve? So was a tank that's written about in the press, like it had a kind of a defined mission set, but then they tried to define every requirement. This thing cost billions and billions of dollars, some cost fallacy, we're gonna keep investing in it. And by the time this thing set market, they're already unwinding it. It didn't actually solve a need that mattered anymore. And actually they hit the requirements like speed, maneuverability, et cetera, but it actually didn't fill the capability gap that they were aiming at. Ingeno: Makes sense, makes sense. the human level. So getting people genuinely productive inside defense program that is outcome oriented all the know ⁓ compliance, security reviews, ⁓ approval chains and all the constraints that defense bring. what does it look like? ⁓ inside the organizations you work with. Matt Jacobs: I think it's getting people to focus on the outcome. Work together instead of treating this thing like in its assembly line where I do this step, you do the next step, then you do that next step. That actually breaks people from actually concentrating on what the overall goal is. Like what are we collectively trying to deliver next for this program and bringing that outcome-oriented thinking? Also, I think in defense, because there are a lot of very strong individuals, the question is always, how can I make that person more effective? The thing that's slowing that person down is the broader system. We need to be creating a system that allows them to be effective towards a goal that's defined, which is not a task or a process step. It's actually what we're trying to deliver. So it's actually rethinking the organizations that these people operate in and the system to allow them the freedom to act. I think on top of that, once you start creating a system that can evolve, it's helping the people, because they've been in the system where They're getting rewarded because so-and-so knows how to work around the system. If I get a system that's working, the system should be working for them. That's that's having anyone who's rewarded for working around the system lets you know your system doesn't work. The inverse though is once I've got a system that evolves, I need to like remind people that the system can change. We're seeing this right now where actually the governments are actually ahead on the policy standpoint. But people are scared to use it, they don't know it exists, or try to fit the old way of working into the new policy that gives them much more flexibility because they're nervous or they're not used to the system actually changing. So getting them to realize that the world is changing and they have the ability to change the system to enable what they're actually trying to accomplish. So I think it's first you've got to change the system, but you've got to do it based on feedback from the individuals. Ingeno: Hmm. Matt Jacobs: And then you've got to help the individual realize they're not in this fixed mindset constrained environment that they have some flexibility, agency, and trade space to really focus on the outcome because they've been trained about to really focus on your piece, your individual task, don't worry about the outcome. Well, now we want them to focus on the outcome. We need to work with them to get them comfortable and show, hey, what are our tools and levers in that area now? Ingeno: And how hard is it people to switch their brains are wired ⁓ to ⁓ outcome Matt Jacobs: Well, I think everybody shows up at work. No one joined a defense prime or the government to be a compliance officer and just move through pre seted steps and like suck their brain out from individual thinking. Everyone wants to be outcome oriented. They've it's been trained out of them over time. they got so tired from fighting the system that they've got their little ways that they ensure that. They help towards the outcome, but they don't get fired in the meantime. So it's a learned behavior over time. It's not what an individual wants. So I think the first step is like reminding them of that. Like, what are you really here for? What do you want to do? And then showing them that there are new tools and then reinforcing it. And then showing them that it's real. Because the other thing is they've all been part of 10, 15, 20 failed transformations over time that. This is going to be great for you. We're going to make you so much more efficient. And it was all about kind of putting something on them. It was never like what anyone was going to do for them. You've got to show them that this time is going to be different. And that takes building trust between the individual and the organization, the transformation in the organization and the individual, and capturing those wins and vignettes and building momentum. This isn't a one-time event. Ingeno: Mm. Matt Jacobs: Again back to capability and outcome thinking. I should be thinking my transformation the same way. Ingeno: So interesting. ⁓ do you see as the biggest opportunity for defense organizations right now? mean how they ⁓ leverage First maybe ⁓ let first ask you this question. ⁓ How let's say ⁓ modern and AI adoption ⁓ going in the in the US for let's the government and and the ⁓ let's say the military aspect of it, but also with in let's say the the the big primes and maybe other subcontractors. ⁓ is it ⁓ as now? ⁓ Matt Jacobs: So I so I think this question needs to be broken into two very distinct parts. And when we're working with private organizations, we also break it always into these two parts. How is AI being incorporated into the things that you actually do? So if I'm building a cybersecurity product, how much AI is in that product? Separate question from how am I using AI to build that? Ingeno: Right. Matt Jacobs: So there's a lot of AI like in the field, in the technology that is actually being delivered to the warfighter. I think there's opportunity to do significantly more and continue to accelerate it, but I don't think that's where the biggest gap is. I think the real accelerant is all right, how do we change what we're doing with AI? I'd say on the US government side, internally. Yeah, yeah. Ingeno: Mm. You mean you mean internally? You mean yourself as an organization? Okay. Matt Jacobs: And if you look at the US government, they're really doing a good job of starting to push it out and making the different tools for the individual available. I think now it's focusing on right, helping people not learn how to use it. It's actually one of the most user friendly systems ever created by humankind. It's literally a brain screen and you can ask it to do whatever you whatever you want. It's showing them how they can use it in their individual role. Ingeno: Mm-hmm. Exactly. Matt Jacobs: And showing them use cases that are context perspective so they get comfortable. The other thing is though, what you don't want everybody doing is automating a bunch of systems and processes that shouldn't exist in the first place. There's an organization that we've done a bunch of work with where as we stepped in and looked at their AI adoption, the first process piece that they've actually really automated leveraging AI. I would say shouldn't exist in the first place, but let's ignore that. It is a compliance-based activity that fundamentally should not be there. And I'm almost positive the rules and regulations actually don't specifically say you have to do it this way. But let's put that aside. There's a lot of AI going up until the approval process. What they have done is made the bottleneck worse because they're producing a lot more compliance artifacts, and then there's still a human approver kind of in the loop. So I actually didn't get system flow, I did was accelerate into the next choke point. And now there's more of it sitting on those individuals. I've got to redesign the processes to be built with speed. I also, and in Agile Land, people talk a lot about velocity, not speed. And that's not just like a turn of phrase. I think it's a really important intentional word choice from Jeff Sutherland. Velocity means speed in a direction. Ingeno: Mm-hmm. Matt Jacobs: I can't go really fast and there's lots of organizations where people feel busy as hell and you look at them and say they're like look at healthcare, like extraordinarily busy people and no one would say the system's really efficient because what they have is speed, not velocity. I need to get people moving in the right direction and with continuous flow. So I need to change the system that those people work in to enable that flow based delivery. Ingeno: Mm-hmm. Mm. Matt Jacobs: And I think a lot of that then is all right, how do I remove handoffs? Ingeno: So let's say I'm a company in defense right now and I ⁓ knock to your door and I say ⁓ please help me adopt AI. Help me use AI ⁓ our internal productivity. Where do you start? ⁓ Matt Jacobs: My first question would be why? And obviously they want to be more productive. let's step back. Like, where is the organization, what's working really well today? Where do we have issues? Let's use the AI to focus on kind of where we have issues. And then I think we need to step back. And there's a large company we're working with right now who originally called us and was like, Should we be investing in agile, AI, or lean? And my answer was like, these aren't competitive ideas from each other. Ingeno: B Yeah. Ha ha ha. Matt Jacobs: To actually leverage AI, I need to be in a very agile organization who can adjust. And my processes, I should be trying to lean out and then using AI to accelerate through that leaned out process. I don't want to accelerate a non and automate a process that's already broken, because then I just do the bad thing faster. That's not the point. So for any of them, and we're working with a large defense prime at the moment, it's First, identifying kind of what are my actual products that I'm providing? How do I need to organize around it? How do I create human-based flow? How do then I help the teams, if we're not already organized in teams, adopt AI and a human machine pairing to go fast to execute the organizational strategy? Which then means I need a way to test cascade what we'd call the golden thread. which is the organization's strategy and decompose that so every individual knows how their action affects that strategy and they have the trade space to then figure out the how. Ingeno: Tell me the typical ⁓ bad whys ⁓ AI adoption. ⁓ you you you said I to you, I wanna adopt AI, I want to transform with AI, and you said ⁓ I ask you first ⁓ why you want to do that? So what do you what are you hearing typically? Matt Jacobs: So the two answers that make me want to kind of step back and work with them that I think are red herrings to me is I want to be more efficient. I think most organizations don't have huge efficiency problems. They have effectiveness problems. So like especially if you're doing knowledge based work, like usually the issue if we even if we just look at coding is not how many lines of code they can write a minute. It's actually that they're working, they're empowered, and it's moving towards like the general strategy. It's not how many people like if you were writing poetry, like the efficiency of writing poetry is like a dumb concept. Like efficiency and knowledge work, like I should only worry about efficiency if I'm not being effective. And the only reason I'm not being effective is I'm not getting enough work through my really effective system. Now I can worry about efficiency. So I think my first thing to is to push them from efficiency thinking to effectiveness. The second is it's because I want to get rid of a lot of individuals. Ingeno: Yeah. Matt Jacobs: Usually organizations today, especially good ones that are growing, they have more that they want to do than they're capable of doing. It's actually, no, how can I reposition people to be able to do those other things? Like the second you're immediately jumping to I want to reduce headcount, saying there's actually not that much for my organization to do. If we could just do what we're doing today with less people, that's the answer. And let's me say you're actually not that valued of a company or in a very growth type. setup or you're missing that person is not there to see kind of that broader opportunity, we need to make sure we see that broader opportunity. I don't mean that never would that reduce headcount or change the type of person in my organization. But my first question is should be how can I do more? What else can I be doing? Because if your customers are not perfectly satisfied today, why are you rushing to rip out cost instead of provide more value to your customer? Ingeno: Mm. Yeah. If you could fix thing ⁓ how defense sector ⁓ digitally what would it be? ⁓ Matt Jacobs: to me is just an enablement piece. I think getting where I would focus digital is getting rid of as much reporting as possible so humans can spend more time talking about the actual work instead of reporting. I heard an expression that I had never heard the other day and that like it kind of made me feel bad. In some jobs you do reporting to show that you're making progress so you can continuously doing the work. Some jobs you do reporting so you can create space to do the work. There's a lot of people, and we hear over and over again, what percent of your work goes to doing work versus talking about the work you could be doing or reporting? We hear over and over again 80% of my effort goes to talking about the work. reporting on the work and twenty percent goes into value add activities. Especially as you move up in the organization, that number gets worse and worse and probably in the middle it maxes out at that 80 20 is talking about the work and briefing about the work versus actually moving anything forward. So if we can t leverage digital footprints to get to shared data, shared understanding, to be able to provide more context to push down decisions, I think that can really accelerate things. But I should not be just creating data so I could push up more information so someone further from the work can make the decision. Instead of actually solving the real problem, which is just allowing the person closer to the work to have the context to be able to make an effective right decision. Ingeno: Alright, Matt, we're almost at time. So before I let you go, lightning round. just first thing that comes mind, no overthinking, just how it goes, so the one technology or capability you genuinely think will change a sector in the next ⁓ few years. You cannot say AI. Matt Jacobs: Yep. Well, I don't think anyone understands what the next five years really looks like if you look at kind of the way Ukraine's operating what we're actually seeing right now in the Persian Gulf. I think it's not about choosing the winner, it's about deploying as many options as possible and seeing what sticks and actually evolves. Like human evolution and evolution doesn't work by the species deciding ⁓ do you know what it would be great if we grew wings? Like Ingeno: Mm. Matt Jacobs: No, someone grew wings and it started to working and evolve. So I actually think the real technology is how do we get more pole based or market based experimentation into this digital technology? Because there's gonna be more and more of it. How do I suss out what's working and what's valuable faster? Ingeno: David. I love that. best example you've seen of a defense organization executing well on a transformation. Matt Jacobs: I think right now because the pace of change and some of the transformation both in the US and the UK are so high, it's forcing people to step back and question how they do transformation and going through structured processes to organize to kind of minimize flow to like build products. So I'm not gonna name anything specific, but I think actually if you look at the top end strategies of where a lot of the governments are going now, if they can execute 30% of what they're saying they want to do, they're on the right path. Now they need to put the resources and realizing it's not strategy. That's a trick, it's the execution. So how do I put as much rigor into executing what I've spent a lot of time deciding I was gonna do? Ingeno: Mm. Matt Jacobs: So I'll I'll leave it at that. Ingeno: Alright, alright. ⁓ was a super valuable conversation. Really appreciate how thoughtful were and and how candid you were. it was a of fun for me. I hope it was also for you. ⁓ This is exactly this show is about. Matt Jacobs: Can I ask one follow up lightning round question to you? Ingeno: Absolutely. Go ahead. Matt Jacobs: What is your one big kind of takeaway from this conversation that you may think about later today? Ingeno: I would say being let's say becoming outcome based, right? Instead of thinking about what work should I do is more like what's is the end goal I'm treading ⁓ That's I I think that's one of the ⁓ main you you you today. ⁓ Alright, ⁓ you ⁓ Matt Jacobs: Perfect. Thank you very much for that. All right, thank you. Bye.