Pod Insights Gradient Dissent: Conversations on AI AI, autonomy, and the future of naval warfare with Captain Jon Haase, United States Navy About this episode In this episode of Gradient Dissent, host Lukas Biewald speaks with Captain Jon Haase, United States Navy about real-world applications of AI and autonomy in defense. From underwater mine detection with autonomous vehicles to the ethics of lethal AI systems, this conversation dives into how the U. S. military is integrating AI into mission-critical operations — and why humans will always be at the center of warfighting.
They explore the challenges of underwater autonomy, multi-agent collaboration, cybersecurity, and the growing role of large language models like Gemini and Claude in the defense space.
Essential listening for anyone curious about military AI, defense tech, and the future of autonomous systems.
✅ *Subscribe to Weights & Biases* → https://bit.ly/45BCkYz
🎙 Get our podcasts on these platforms:
Apple Podcasts: http://wandb.me/apple-podcasts
Spotify: http://wandb.me/spotify
Google: http://wandb.me/gd_google
YouTube: http://wandb.me/youtube
Follow Weights & Biases:
https://twitter.com/weights_biases
https://www.linkedin.com/company/wandb
Join the Weights & Biases Discord Server:
https://discord.gg/CkZKRNnaf3
Transcript 12,118 words · 2 speakers
Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.
0:02 Lukas Biewald? You're listening to Gradient Dissent, a show about making machine learning work in the real world, and I'm your host, Lukas Biewald. Today, we're joined by Navy Captain John Haase. We've worked with John for quite a while on a specific use case around underwater unmanned vehicles, which we talk about, but John is actually the program manager for Navy's Expeditionary Warfare Division, and so he has a really broad purview into how AI and warfare interact. And this is a really interesting conversation, which isn't happening enough in Silicon Valley. I hope you enjoy it.
0:40 Lukas Biewald? So I guess, first of all, I want to, I want to start with, can you tell me about some of the AI applications that you've recently been involved with and how they work? Because I think you're in a domain that a lot of people listening to this podcast wouldn't, wouldn't know well.
0:57 Speaker 01 Yeah, the applications. So one of the applications that's really at the heart of what we do is automated target recognition. And so I got to back up a little bit to talk about the hardware instantiation of where we run these models from, because it's really important to understand the unique challenges and the way that that automatic target recognition is done. But the automated target recognition runs on unmanned underwater vehicles. And these are underwater robotic systems that are pre-programmed to run missions to search the water for mines. And then based on what they find, either to cue autonomous behavior by other vehicles or to simply bring that data back and allow human operators to be involved in decision making about what to do next with these mines and the naval operations that are happening.
1:42 Speaker 01 So the AI component to this for the automated target recognition is that this is actually an ensemble of deep learners that we put together over a number of years with a number of third parties who are able to integrate and then onboard into, you know, Nvidia processor that runs on this unmanned underwater vehicle that's able to, you know, deliver inference runtime in order to cue where we found targets. And it also runs on laptops so that it helps human operators who are reviewing all this data that's generated from the missions to more reliably and faster review that data and determine where the mines would be. So it's queuing, it's targeting, it's bounding boxes. It's the stuff that you might expect. And it also involves bringing that data back then from new missions and then
2:27 Speaker 01 fine tuning all of the various components to that automated target recognition. And again, figuring out how to wait and ensemble those things and rapidly redeploy them to those vehicles. So really, the big application that we work on is AI to detect mines on these autonomous underwater vehicles, which uses, strangely, a number of different techniques that work together really well when ensembled and are power efficient enough now and good enough at runtime with latency to be relevant. And there's enough metadata on the vehicles that it provides a really rich environment for us to extract that metadata as well as the data generated. So that's really the heart and soul of what we do is automated target recognition for underwater operations to detect mines so that we can conduct operations.
3:09 Speaker 01 We're also looking, and this is a little bit less mature, at some pilot programs about how we can make interacting with these vehicles easier for the sailors who use them. And so looking to replace PDFs and interactive tech manuals with things like intelligent agents that could be trained on all the specifics and answer questions, help with field maintenance, even plan missions better and be involved with that. And then sort of zooming out just a little bit more than that, which I think is pretty common with other folks, looking at how AI can help the workforce developing these products to generate the documents more effectively, understand our requirements better, and act as just an intelligent assistant to the process. So kind of looking at those three things. But the one that we've had the most engagement with and that we've been most involved with and has the most
3:54 Speaker 01 operational impact is the automated target recognition that allows us to spot mines underwater with those vehicles.
4:00 Lukas Biewald? Now, just underwater autonomous vehicles, is that a fancy way of saying a submarine? They look like submarines from my perspective. Can you describe what this is?
4:10 Speaker 01 In some ways, they do look like submarines. In some ways, they don't. And so think about a cylinder that there's no need for life support. And that's really the big deal about autonomous underwater vehicles, is that you don't need to have any of the services that a human would need. So oxygen purification, generation, atmospheric controls, eating.
4:29 Speaker 01 You know, discharges that would be required from in to out. It's just batteries and systems. And what that allows you to do is make much smaller systems than you could otherwise do, like the kind of things that a human being could never fit into. And so I have experience with the smaller and medium versions of it. So anything from, you know, about the size of a normal dining room table to, you know, two tables essentially put together would be the sort of scope that we do. I'm thinking about a long cylindrical tube with one propeller at the back of it to power it and a couple of control surfaces and fins. And then for sensors, we have some sensors that would look forward to detect things directly in front of, below or above that unmanned underwater vehicle. And then we have sonars that are looking downward from the sides and that are able to search the bottom.
5:14 Speaker 01 And so we load this thing up with sensors, we load it with batteries. Recently, we've put onboard compute on these as well. And then we have, you know, navigation autonomy software that we put on and then preprogram the missions. And then we're.
5:28 Lukas Biewald? And, and I guess one thing that might not be obvious to people is underwater, I think you can't, it's harder to communicate, right? So you actually really need total autonomy, right? Or how much contact do you have with the UAV?
5:45 Speaker 01 You know, Luke, I'm glad you mentioned that. That's like one of the things that's hardest for people to appreciate who haven't had to operate underwater is underwater is so hard. I mean, the fluid that you're in is like a thousand times more dense than the air to start with, so speed, resistance, control surfaces, right? You have to adjust for altitude at this point also. And you can't use GPS. Communication underwater is really challenging. And so, you know, just communicating between vehicles, you have to use sound waves that have to travel through the water. And, you know, there's a lot of background acoustic noise that's generated from marine life, as an example, or sound channels that are created because of temperature gradients. And so even delivering the sound energy between the vehicles becomes challenging.
6:27 Speaker 01 And then you have encryption issues that you have to work through and delivering that of just communicating between the vehicles becomes, you know, really hard to do in addition to a number of other things.
6:37 Lukas Biewald? Is the underwater autonomy also an AI system? Or is that is that simple? Because there's not really a thing to crash into underwater like you. Do you just sort of aim it? Or or does it also have to navigate and use sensors?
6:51 Speaker 01 Yeah, so there are a couple of things to unpack there. The first is there are things to crash into underwater and we have. So, you know, if the chance is not zero and given enough time, all things will happen. And we've done it. And so, you know, there's steep banks. And when you preprogram missions, these steep banks and gradients, because you know, you have to maintain a relatively cross proximity to the bottom in order to generate a lot of the targeting data that we would use the sensor data that we're generating. And so if you have a real steep cliff, you can inadvertently run into it if you're not looking forward while you're looking down. And so you actually can run into things underwater. But the autonomy is preprogrammed. It's deterministic right now, but it is connected to our AI systems. And this is why having it onboard and being able to perform inference at runtime on
7:36 Speaker 01 the vehicle with low latency is really important for us in a power efficient way. Because what happens is if we think we have seen a mine, we're able to dynamically adjust the mission in a preprogrammed way to essentially bring in a branch to the original plan and to search that area more extensively while the mission continues. And what that avoids is having to bring these vehicles to the surface and to evaluate the data and then reacquire that object of interest and run a whole second mission set. And so while the autonomy is deterministic and not generated by AI at this point, it does rely on AI and is integrated with it so that we can change that autonomy in preprogrammed ways to speed the mission up.
8:16 Lukas Biewald? And I guess I wouldn't naively think maybe you'd want to put an underwater mine kind of close to the surface, right? Why does the UAV run close to the ground?
8:28 Speaker 01 So there's mines that are on the bottom, there are mines that are in the water column, and there are mines that are very close to the surface as well. It's all just dependent on the specific design of the mine and how it's designed to function. So some are designed to and function very efficiently from the bottom.
8:42 Lukas Biewald? Oh, wow. And are mines a big, a big problem? Like, are there lots of mines out there? I read, this is way outside my wheelhouse, but like, like, is this a, is this like a real thing that you really need to solve? Or is it more of like a proof of concept for the, the technique?
8:59 Speaker 01 They've been used in the past, and they can shut down fleets in the middle of operations. They are incredibly dangerous when they're out there, and they're fairly low cost. So they're sort of an asymmetric threat in a lot of ways. They're also very difficult to detect. And so this is the reason this capability is so important. It's not a theoretical threat. The Navy has run into these in the past. We've got plenty of case studies about where and how that's happened. And it's a, it's not a problem until it is. And when it is, it becomes a really big problem. I mean, all the way back to the Civil War, 1864, Battle of Mobile Bay. David Glasgow-Ferragut was going into Mobile Bay with Ironsides and wooden ships together. I mean, damn the torpedoes, full speed ahead is when the lead
9:41 Speaker 01 ship in his formation, the Tecumseh, one of the first Ironsides, hit a mine. And it was so disruptive to the operation that the entire fleet stopped. The Battle of Mobile Bay stopped because of mines back in 1864. And David Glasgow-Ferragut, the admiral in charge, was on the Hartford, the second in formation, the first ship in formation on the wooden column, stopped because they were so afraid to hit mines. And he ordered his ship ahead full speed, and right into the minefield, and progressed with the fight. And that's where that, you know, famous expression came from, damn the torpedoes, full speed ahead, was this assault on Mobile Bay in the Civil War in 1864, where mines became a critical
10:23 Speaker 01 factor. And the only reason that we survived that attack from mines that we were in the middle of was by luck, not because we had done mine countermeasures and understood the threat, avoided or mitigated it sufficiently. And so... You know, the interesting thing is back then ships cost in today's dollars about 17 million. You know, today it's billions of dollars and so it's just not something we could ever do again. And so, yeah, it's not a theoretical threat. They're out there inactive.
10:48 Lukas Biewald? It says the idea that that someone on a boat would would put these into the water and they'd go out ahead and look for mines? Or how how would this actually be used in practice?
10:57 Speaker 01 For the vehicles, you're saying in order to find and clear a minefield. Right. So there's a lot of things that would have to play into how we might suspect there's an area to be cleared. It could be the geography that we're going to navigate. It could be the threats that we know about. It could be a number of other things that are available to fleet commanders that would say, hey, this is worth investigating. These are areas that need to be risks that we would need to mitigate further. I mean, obviously, the ocean is much too big a place for us to do this everywhere. And so it has to be sort of strategically done in points that matter at the right time, in the right place, for the right ships to transit through. And, you know, that's all really situationally dependent sort of stuff.
11:34 Lukas Biewald? I mean, so this seems like a really good example of kind of putting intelligence into objects in a really useful way. And I think it's probably a really good example from a like a PR perspective, right? Because mines just seem like kind of a horrible way to, you know, it seems like it could kill civilians. It seems really, really dangerous. But it seems like there's kind of a spectrum here of different like levels of autonomy that you could give lethal devices. I mean, this is like purely defensive, but do you have a framework for thinking about? Like, or is there a place where you would draw the line? Like, it seems like you definitely wouldn't want like an AI system deciding to launch nuclear weapons. Like, that would that would definitely be an extreme. I think no one would, no one in their right mind would support that.
12:19 Lukas Biewald? But it seems like there's a lot of, a lot of stuff in between. Like, how do you think about that?
12:26 Speaker 01 I appreciate you highlighting that. There's certainly a broad spectrum of applications for the Department of Defense for using AI. Our portfolio has been doing this for some time. And as you highlight, it's a great mission for us to have because it's defensive and it clears these threats and obstacles. So that not only do the US Navy ships not hit these should they become an issue, right? We're available to help clear these so that civilian mariners or others are protected and they're safe. And so it's really an easy mission to sort of get behind in that way. And there's no ethical questions about using AI to clear these hazards, right? It's on the protective side, which makes it really, from the ethical question you're asking, much simpler. I've never had to wrestle in terms of my job policy or larger
13:06 Speaker 01 issues about where AI and autonomy could be used for more offensive operations. And so I haven't had to really wrestle through that or think through what a program would look like or fail safes or the other things necessary to do that. I think my thoughts on that are that the taking of human life is such an incredibly impactful thing that I could not imagine offloading that to AI or autonomous systems in any sort of meaningful way moving forward without humans like directly and specifically involved so that all the ethical concerns and considerations would be like fully met in that regard. And so there's a spectrum in between about like gathering information and it's very use
13:49 Speaker 01 case specific. So I think the best way to approach a subject like that is just with extreme regard for human life and safety and explainability. This is an irreversible thing that could only be done like under the most responsible and ways with the best oversight possible to ensure no collateral civilian or innocent lives are lost and just approaching it with that sort of framework and realizing that the tools that the military have should allow us to do our mission better, but never put that ethical high ground that we have so proudly maintained and do still ever at risk.
14:21 Lukas Biewald? Although it seems like that's kind of a comfortable position you might have when you don't feel under threat. Like I noticed in Silicon Valley, I think people were really against maybe any kind of like AI military applications. But then I think for a lot of people, kind of seeing the war in Ukraine reminded people that, wow, you know, there's bad actors out there and, you know, they're probably, you know, using, presumably like we would have enemies that maybe wouldn't hold to such a high ethical standard and, you know, might build autonomous weapons at any degree of autonomy. And, you know, you might lose a conflict if you weren't willing to be a little more aggressive, right?
15:06 Lukas Biewald? Or do you think it's possible to really hold that standard of like never integrating AI to anything offensive?
15:13 Speaker 01 Well, I don't think I'd say never to integrate things, AI into things that are offensive. Certainly, you would need and want to. And as the pace of conflict advances and as adversaries build these capabilities as well, you need to keep pacing in front of them. You also mentioned, I heard, being aggressive and victorious and sort of being warriors that could prevail in the face of conflict. And what I'd say there is, I think it's a and, or I think it's a, an and, and not an or. So I think you can be aggressive. I think you can be warriors. I think you can go and prevail in conflict and maintain the moral high ground. I think the way that you would integrate AI autonomy and advanced technology into that operational scheme, again, are really dependent. A strategic
15:54 Speaker 01 comparative, though, is that through all of this, we would never want to give up the ethical and moral high ground. We would never want to alienate our allies and those that would come with us into these conflicts in the future. And so I think those are things that are just bedrocks of the American military and have been for a long time. And I don't think that you can't enable and integrate technology, AI and autonomy, and still maintain the moral high ground and the respect and dignity of low collateral, no collateral damage to innocent civilians while prosecuting wars. And so I think those things are totally synchronous and can be done at the same time. And I think we've got some incredibly talented
16:37 Speaker 01 people working on those issues. And I'm confident that, you know, in the moment where we would need to come to a decision, we would handle that appropriately.
16:45 Lukas Biewald? I'm curious what it's been like for you working with Silicon Valley companies. Like I have, I've noticed in the last couple of years, I think it seems like defense has, there's been a lot more collaboration, I think, between Silicon Valley and US military. I think when I go back a few years, I remember, I think Google Cloud decided to stop supporting certain military applications, no matter how bad that made, you know, people I knew in kind of military applications feel, and I felt like that like created a lot of like animosity, you know, at the time. Do you feel like that's been kind of, you know, worked through and forgotten, or do you think there's maybe still some talking past each
17:28 Lukas Biewald? other, or kind of like resentment on your side of the fence?
17:34 Speaker 01 Oh, on the military side, no, I don't think there's any issues on our side. I think we've always just wanted the best tools, the best capabilities, so that we could be the strongest military ever and maintain that position of strength, so that we can prevail in any conflict. So I think whatever the tools are and whoever makes them, we'll gladly use them. We just want to win. You know, that's really the only rule to warfare is win. And I think, you know, however and wherever we do that, you know, given all those constraints about protection of life and the moral high ground that we maintain, and our allies and partners and all those things, but yeah, win it all, win. And America is just amazing at that. We were as good as we've ever been. And so I think when it comes to, you know, because there's a couple of things to unpack there. You mentioned
18:17 Speaker 01 Google specifically, and sort of the transition that they had had, and some of the stories that I had seen in the press, you know, recently, I understand they've got their impact level five approval for use in the government now. So where they were versus where they are now, they're offering services to the Department of Defense, they're in compliance with some of our security concerns there for cloud computing and cloud usage, and they've entered that marketplace, you know, I think with a big contract recently, along with Amazon and Microsoft. And so they're, they're one of the offerings. I think more largely, though, if I could kind of maybe address, I think what's kind of fundamental to that question is the partnership between tech companies and the military in general. And I think that there's actually a great relationship between technology companies
19:01 Speaker 01 and the military, one that's to everybody's benefit.
19:05 Speaker 01 So that we see younger companies that are really bringing a lot of tech and forward-leaning processes and moving really aggressively and quickly to develop useful capability that are entering the scene now and challenging the status quo from a tech mindset. There are also VC-backed and tech companies in the defense tech space. We're seeing more entrants there as well. And we're also seeing more partnerships with larger tech companies so that if you look at what, say, Microsoft is doing with OpenAI and offering some of those connected services, there's some examples of some really big tech companies that are supporting defense and government in general through partnerships. So I think what I've seen based on all that is that tech companies are trying to understand defense better,
19:47 Speaker 01 trying to serve us as one of their customers. And I think we're just grateful to have all that technology coming in, giving us more fighting power and making our military more effective. And so there's certainly, and you highlighted another thing there about cultural differences, there's certainly cultural differences, right? I mean, just having some exposure to what a tech company is like and how you treat your employees and what the demands are and the sort of tech and talent that you recruit, that's obviously a totally different culture than the military. And I think what's important is to understand and to communicate between customer and client in that case so that tech companies understand what we would need, the reliability required to operate in the military environment so that we could be used in conflict and combat. And then for
20:29 Speaker 01 us to also understand the capabilities, the limitations, sort of the financial structures and incentives and make the process of working with the government a bit easier for tech companies. So I think there's some understanding and outreach on both sides, but it's to everybody's benefit. And I think generally, things have gotten better. And I see a future in which those relationships get stronger and more defense tech companies founded by simply tech folks who have done successful startups before or worked at large companies are just going to increase over time. I think there's a lot of capital going into that as well. So I think that marketplace is really rich and robust right now. And I think that's, again, to our benefit.
21:06 Lukas Biewald? What do you think? One of the things you mentioned to me before recording this is, is people really underestimate the gap between software applied to civilian use case and then software applied to one of your use cases and how much work goes into kind of hardening the technology to make it, to make it work for you. Could you talk a little about that or tell us some stories, you know, maybe from the work that you did on what needs to change? Like, you know, in some sense, when I just zoom way out, you know, autonomously operating a car like we have in San Francisco and a lot of our customers do and autonomously operating submarine, like, okay, it's sonar instead of LiDAR and the cameras don't work as well, but it does seem, you know, both are, you know, a submarine and a car is a
21:51 Lukas Biewald? lethal weapon if you, you know, if you operate it badly. Like, what's the difference when, when you try to take technology not designed for you and make it work?
22:04 Speaker 01 Yeah, I think at a very high level, the biggest difference is that I am not convinced that autonomous vehicle companies are considering adversarial attacks and that adversaries are actively looking at those as attack surfaces and that there are regularly repeated, expected and by design attacks on those autonomous vehicles to disrupt their operation or to make them intentionally unsafe and not function as operated, or even worse, to compromise them in a way that is unknown to the operators at the time. So this fleet of vehicles turn out to be a proxy for someone who is not supposed to have access to them. So I think that's the-
22:41 Lukas Biewald? Although they probably should, right? I mean, actually, that's, as you say it, maybe they should be considering that, but you're right, they, they probably are not considering that scenario. But that does seem not impossible. I'm sorry, go ahead.
22:56 Speaker 01 No, I'm, I am, right, there is, right, okay. So yes, that is, that is a thing, but that's not considered by the manufacturers of those vehicles. And there's a reason for that is because nobody likes, here's the hard truth, nobody likes cybersecurity. When you cyber harden something, an object-
23:15 Speaker 01 It makes it harder to use, slower to operate, longer to boot up, and more difficult to access from a login perspective. Right? So when you go to single sign in to MFA, right? You've just made the login process harder. Now, imagining adequately cyber hardening a vehicle so that all those attack surfaces are mitigated and a dedicated and professional actor couldn't access that vehicle under any conditions. Now you're talking about you would have three keys to the vehicle. You would have a password once you got in. You would need to make it larger and slower because there's more software that would have to, hardware and software that would have to go on it. The entire comms bus would have to be changed. The messaging internally would be encrypted. Everything would work worse.
23:58 Speaker 01 So here's the reason people don't like hardening things so that adversaries can't get to them is because they're more difficult to use. And so that is one of the most significant challenges and something that we've personally had to deal with with our programs is that we've taken a commercial robotic system that works great. And we were the first to go through this process for these unmanned underwater vehicles. And we cyber hardened it in accordance with the Navy standards are. And we thought that we were making like a 10% change because all we had to do was, you know, add these additional modules.
24:34 Speaker 01 But it was like a 90% change because what we quickly realized is we changed the communication structure. We changed the comms bus, the physical architecture, the software layers associated with it, even the way it communicated were different. I mean, just to give you an example of the complexity that we didn't appreciate before we began as a first of for the Navy here. The length of signals that the underwater acoustic channels had to send increased because they were encrypted now. So in addition to the signal, you had to send the encryption packets. That allowed one of the transistors to stay open, the DSP to stay open longer to transmit the signal. That then applied more voltage for a longer period of time across the circuit, which caused it to overheat, which caused this circuit card to fail, which again, like, we're adjusting now the physical architecture of this vehicle to account
25:19 Speaker 01 for a communications challenges that was related to a signal processing thing so that we could get the communication packets through. That's just one example, right? And so this is where, when defense tech companies or others come to me, my programs with, you know, things that work, they never actually work. And what would seem simple turns out to be really, really complicated. So your initial question about, hey, autonomous vehicles, why can't we just do this with underwater vehicles? So first of all, the challenges underwater are significantly harder, I think, than operating on the road, even though those are not trivial also. But then it's this requirement for reliability and for robustness of cybersecurity that becomes really, really challenging, right?
26:03 Speaker 01 And so we have to tackle and deal with those. And that becomes really difficult because we're, I think, at the forefront of cyberhardening and making these robotic systems robust so that adversaries don't, it can't access these tax surfaces. And that has all sorts of technical implications that were difficult to foresee before we did it. And so, you know, working prototypes that aren't fully hardened and meeting our requirements turn out to be really difficult to fully, you know, harden.
26:29 Lukas Biewald? Does your organization do its own AI research? Or does it outsource the AI research? And what, what, what parts do you feel are core? Like, a company would think, okay, maybe there's certain parts here that's sort of like, things that we really need to know how to do ourselves. And there's parts that we need to, it's okay for us to like, outsource to third parties who are going to do it better than us. Like, how do you think about that?
26:55 Speaker 01 Yeah, so unpack that. We do do some of our own research. So the government does have technical centers of excellence that are capable of doing some of this work. And we do leverage them to do some of this work as well. However, we find that a partnership for our particular programs with industry is also necessary. So we go through some big defense primes who are able to provide, you know, some of the AI services that we need to do this. And that's on the bespoke side of things. So when we need specific things built just for us, like the automated target recognition as an example, you know, there's no civilian equivalent that we can access something that's commercially available. And so you asked how we think through the process. And so the first thing would be to do a market survey and to see what's available
27:38 Speaker 01 and to reach out to the government warfare centers. Because the first question that we're going to ask is, has this been done before? Has anyone done this as well? Is there information? Are there architectures? Is there models or the data repositories? Is there a workflow that we could use? Is there even a schema that we should be using for commonality between our data sources? So we'll do a broad survey and in some cases we'll find things, in some cases we won't. You know, the next part of this would be to really scope the requirement and think through it smartly so that we can then go out to industry. And there's a number of ways that we can do that to find the best available commercial partners who can develop these algorithms for us. And increasingly, with the pace of innovation speeding, with some of the novel models that are happening and some of the open source opportunities that are available, you know,
28:23 Speaker 01 open source has really allowed many of our providers that have experience and understand the mission to leverage some of these open source models in a way that's just really catapulting and advancing our capabilities by taking advantage of what's available in open source and being able to, you know, sort of ensure the safety reliability of that, bring it into our system and work on it. And so we think about it in terms of the requirement, what's already been done and what's available, and then a contracting strategy that lets us get to the best available workforce that'll do that for us. That's on the bespoke side. On the, you know, we have a large, say like a LLM requirement in order to, you know, perform some function, we'll just certainly do a commercial landscape there first to understand what's available.
29:07 Speaker 01 And if there's a pre-built solution, we are really better off changing our requirement to meet what's built at scale than we are to try to create a bespoke solution to meet our need, if there's anything that's even close. So the really important thing there for me and my team is to really adjust our expectations to take advantage of what's commercially available and work on policy to use that appropriately within our programs. Because there's just things happening right now that we would never, I mean, if you look at the amount that goes into training LLMs and the research and the investments that are made commercially, we would be foolish not to take advantage of that as it is and not modify it because that just increases your costs exponentially.
29:49 Lukas Biewald? Okay, so I was wondering, again, this is maybe putting like a business hat on for me and then wondering how it applies to you. Like, I was wondering how you think about your competitors. Like, I was really excited to hear you say that, you know, where America is like the best in the world at winning. That seems very reassuring. Are there, you know, like, I have competitors that keep me up at night. Do you feel similarly about like other countries' military? Like, do you think about like, okay, are they, are they doing something better than us? Or they figure out things that we don't know? Is that, is that something you think about a lot? And are there aspects of what they're doing that you think we could learn from?
30:29 Speaker 01 Well, there's a lot in there. We can learn from everybody. I learn from my kids, right? So we can certainly learn from other militaries. There's things we should be watching.
30:37 Lukas Biewald? Or do you not even consider other militaries competitors? Is that the wrong analogy?
30:43 Speaker 01 Yeah.
30:45 Speaker 01 Yeah, so I'm afraid of no one. There's no country that keeps me up at night. We are America. I am not afraid of what that means. I work with people who are not afraid of what that means. And I've been in combat. I know what that looks like, and I'm not afraid. And the rest of the folks who are with me right now are not afraid of what that means either. We will go toe to toe with anybody, and we fear no one. Now, we respect everyone, and war is a terrible thing to be a part of.
31:20 Speaker 01 In some ways, nobody wins. And so we should have an attitude where we respect everyone out there. Everyone can put up an amazing fight. And you can look back through history to see just examples of great powers that struggled with smaller opponents. You can get the stiffest resistance from folks you didn't expect it from. You have to respect your adversary in combat. But at the same time, We don't, we're not afraid of what that means and we're not afraid of moving forward to defend our country and our nation. And I'm really proud of all the work that we've done. In front of me, I've seen people who weren't afraid and went into combat and were victorious. And I see people coming behind me as I get ready to retire who are going
32:04 Speaker 01 to take that torch and who aren't afraid of what that means either. So I think that we don't fear other countries. I think we respect them and what that might mean for us to be in a position in the future where, you know, we might be competing with them in that way. And I think that we have to be humble enough to learn from everything that's happening, realize that technology has for a long time shaped what it means to go into conflict and that technology is changing more and more rapidly, which is why the relationship you highlighted earlier between technology companies and the Navy is critically, in the military is critically important, right? We need to be aware of what's happening to use it most effectively, to remain the strongest fighting force that the world has ever seen. I'm so proud of what we've done.
32:48 Lukas Biewald? It does seem like maintaining a technology advantage, though, is incredibly important for, for staying safe and, and, and winning wars, right? Like, and it seems like as the technology moves faster and faster, maybe that becomes even, even more important. I don't know if that's a good, you know, tech executive bias here, but it just sort of seems like, like the idea of another country having AI technology that's a few years ahead of ours, seems really scary when you think about like what, especially when you think about like what military applications that might have, no matter how fearless we are.
33:26 Speaker 01 Software has never won a war.
33:30 Lukas Biewald? Interesting.
33:31 Speaker 01 Software has never won a war. That just isn't how it's done. And that's not going to be what decides the next war either. John Boyd was famous in the Air Force and Marine Corps during his time in and after active duty. The Americans with planes that were not as good were able to best Russian pilots in the air. Because our planes had hydraulics and theirs didn't, so we could maneuver faster, but their planes were actually better technically, their pilots just couldn't operate them effectively. That's an area where the Russian planes were technologically, had better tech than ours, and had better performance specs, but because of the human factors necessary to do that, our pilots were able to be better in the air because they could make better adjustments in the planes they were using. So it's not just about the tech specs.
34:14 Speaker 01 I've not seen one conflict or combat so far where software has been the deciding advantage over that. It's an enabler, but nothing will ever replace the fighting spirit of the folks who use those tools. So while it might be terrifying to see the battle about tech go back and forth and who has the advantage in any particular moment, that I don't think will ever be the deciding factor. There's a margin that as long as you're within that margin and you still can compete with the necessary technology that we have. There's something magical about America and I think anyone who tries to test that is going to be really disappointed with the outcome in the future. And so tech is going to be an important part of that.
34:56 Speaker 01 We're going to use that tech as best we can, but I don't think, so I'm pushing back a little bit on like, hey, what happens if we slip a year or two behind?
35:03 Lukas Biewald? Yeah, yeah.
35:04 Speaker 01 Yeah, it's just not how, it's just not how we win wars. Like, software is not going to march into the capital of another country and declare victory, right? This is not how it's ever been done and I would be shocked if it ever is done that way. Autonomy is going to be important, AI is going to be important, but that's one component of how we would operate and that's not the only component. So, you know, there's other areas that you could look at. Energetics inside of explosives, as an example. You could say like, hey, if we have better energetics and are like, the energy per pound of explosives delivered is higher for one country than another, wouldn't that mean we're going to win? And the answer is that's one factor, right? But like, so much goes into it that at the heart of it, warfare has always been about people.
35:48 Speaker 01 I think we have the best and the best warriors that the world has ever seen and the strongest military ever. I think we've stitched together all these capabilities in a way that's incredibly impressive. Software is part of it, but isn't the only part of it. So as the defense tech community comes and rallies behind and partners with the military, it's also important for us to realize that it's not the only part of it.
36:09 Lukas Biewald? It seems like...
36:12 Lukas Biewald? Software could also play a role in in training people and choosing people. Couldn't I mean, if that's the most important thing, that seems like maybe a really good place to try to to use more software than.
36:24 Speaker 01 Absolutely. AR VR, any way that you can make humans that are involved in the activities the military do more effective. This is where that automated target recognition we were talking about becomes so important. This is where enabling decision advantage becomes so important. How do you lift the cognitive burden off people so they can focus on the right thing at the right time so that they're not overwhelmed by irrelevant information, but they clearly see the signal through the noise, they make the right decision about combat operations in the right moment, and they can most effectively move forward with the most important things that need to be done. You can look back through the history of warfare and find all sorts of, I mean, just as an example, in World War II, Nimitz sent a message to Halsey, two famous admirals,
37:07 Speaker 01 and Nimitz meant for Halsey to attack a Japanese battle group that was going through a vulnerable spot. Halsey got the message and thought it meant be ready to attack. So he never attacked. And so we had better technology, we had better intelligence, we had better positioning, we had the element of surprise, and it didn't matter. And so that's an example where there's like so many factors that go into these operations that you have to sort of cut through all that and get to the best decision making, best situational awareness, best capability, but like they all have to come together in kind of a magic moment.
37:42 Lukas Biewald? What do you think changes in the next like five to 10 years with these AI applications exploding like like it does sort of seem like what we think of as war probably looks a lot different, doesn't it? Probably a lot more unmanned things going around like like you see in in the news in Ukraine, you see a lot more, you know, drones and things like that. Is that am I off on that or what's your what's your view?
38:10 Speaker 01 I don't think so. I think that's a trend that will certainly not go away. I don't think that we've seen.
38:19 Speaker 01 A nation state put all its resources behind conflict operations that has the sort of tech scope and background that America has right now to know what that would fully mean. That's a, that again is one of the factors that would go into it, but there I think are going to be a lot of things that go into it. And so, yeah, I think technology will play a big role. I think unmanned will play a big role. I think the future of warfare is going to be enabled more and more by technology. I do think we will see more of these robotic systems on the battlefield. How they interact together between systems, how they generate information and how humans process and use that on the battlefield is going to change a lot. And I think there are, you know, a lot of tailwinds that we have in terms of that technology
39:04 Speaker 01 developing in the commercial sector. So I think what we'll see is that humans will be enabled more and more to do more and more operations in various locations remotely. I think that we'll see that we have better information and more real time information. I think that we'll see that we have a more connected battlefield where information is flowing between robotic systems, humans, AI agents that are helping with decision making. And I think that we're going to see the pace of operations speeding up more and more. But the other thing I know is that every time we've gone into a conflict in history where technology played a decisive role, whether it be the advent of aviation, rifling that was, you know, introduced into firearms, gunpowder, whatever it was, we were always surprised by it on the battlefield.
39:49 Speaker 01 And so I think that there'll be some surprises that nobody's anticipating. I think it's a reasonable project, current trends into the future, but leave about 30% for something we just don't see yet.
40:00 Lukas Biewald? Interesting. What about LLMs? I feel like we've been mostly talking about autonomy here, but I was kind of excited when we were talking earlier, you talked about using, I think Gemini, your daily job and your wife using Cursor as a developer. I mean, that seemed pretty exciting, it seemed pretty modern. Like what, what LLM applications are you seeing right now?
40:18 Speaker 01 Yeah, so the Department of Defense is really trying to figure out how to do this. They know it's important, and so the Air Force has done some great work. And it's a policy issue for us right now. We've never had to sort of bring intelligent agents into the DOD before. And what that means in terms of our information protection, in terms of policy compliance, ethical considerations, and all those things. So, you know, really taken a measured and cautious and diligent approach to all that. What's happening, though, is there's some limited instances that are starting to get piloted right now, where it's Gemini, there is Anthropic, I've seen them recently come out with, the Air Force come out with some applications that are able to use to access that, and Microsoft making some of those available at different impact levels, so
41:02 Speaker 01 that everybody who would have access to these systems now has access to the LLMs. And what that means is that we can expect things to move more rapidly, we can expect a higher quality on the first go, we can expect reviews, intelligent assistance, these complicated processes to become more easy to understand and to navigate through, cycle times to be increased, developers to be more productive. I think it's a really exciting time for us to be onboarding this capability. And I think there's an incredible opportunity, because some of the things that are happening inside of the DOD with these LLMs are going to be so unique to what's happening outside of the DOD, that there's probably some space that's not being adequately served there,
41:43 Speaker 01 about how an LLM could be, you know, specifically tailored to meet the needs that are inside of the Department of Defense, as an example.
41:50 Lukas Biewald? Could you be a little more, like, at all more specific about what that might be? Like, what would be different? Because it's all, you know, kind of humans trying to solve problems at a high level, I think, right?
42:01 Speaker 01 Yeah. So there's some guardrails, I think, that are on large language models about, you know, things that you could query and policy things that you generally wouldn't want people to be discussing or talking about, that would be part and parcel to what it means to be in the DOD and conducting combat operations. And so... You know, somehow figuring out a way to enable people that are doing mission planning or looking at warfare or making sort of plans or reviewing plans, processing data from the battlefield, having to deal with casualties in combat operations, right? Those might be triggering some policies and guardrails that would sort of generate the, hey, this violates our policy and we can't serve this at inference, right? And so I think there is a requirement there so that a little bit more interaction about
42:46 Speaker 01 like lethal operations in terms of what the DOD does, what we would want to plan for and how to process that information. And again, we haven't had to do this at scale during combat operations yet, but I would foresee that there'd be some policy issues there, both on our ability to use the large language models, but then also on the folks who are creating these where you wouldn't want normal people talking about how to conduct an assault on a position, right? But in the DOD, those are things that we're planning for and we would want to enable. And so I think there is something there to figure out, right? And we haven't had to see what those policy issues and problems are yet, but certainly the DOD would have some more limited applications if those aren't addressed. And, you know, right now, we're just trying to figure out how to, you know, use these
43:30 Speaker 01 LLMs and these AI agents to sort of do the day job and do the paperwork and run, you know, low threat processes a little bit faster to process awards, do HR stuff. But when we get into more core business of the military and should we be looking to use these more in the future, you know, I think there has to be a closer partnership about some of the policy and guardrails that are associated with LLMs.
43:51 Lukas Biewald? One of the things that people worry about with LLMs is the idea that, you know, for example, like an individual could learn how to create a bioweapon and then actually, you know, build it, or that, you know, people could, could learn, you know, on their own how to create really like lethal, you know, weapons or, or big problems. Is that something that, that you think about or that, does that like kind of change any of the ways that, that you think about security?
44:20 Speaker 01 It creates some new problems, for sure, and ones that aren't new, to be honest, that information can be found in various places, right? And if you look back through some of the events that have happened, that is the genesis of where people have found these things. So the information is there, it makes it a little bit easier to get to. And again, this isn't something that the DOD or the military controls, what companies are able to serve, or how their policies allow you to interface, or jailbreak things, or how they clamp down that information. Because again, we don't know how these models have been trained, so we don't have the data provenance to know what it was exposed to, and what it knows, and what it could figure out. Increasingly, if you have more and more intelligent agents, could you have it do one part of
45:04 Speaker 01 that planning over here in one chat window, and then stitch together a number of chat windows? These are questions I don't have answers to, but are something that I think the trust and safety teams at these tech companies need to be taken seriously. And I'm really encouraged to see a lot of these companies think about trust and safety, and put up policy guardrails to try to prevent this. And I think it's something that they need to continue to monitor, and to take an active role in, to ensure the security of these intelligent agents don't put people, needless to say, at risk because of policy problems and guardrails that they didn't put in place.
45:38 Lukas Biewald? So one of the things that really affected my world recently, and actually the stock market quite a bit, was the surprising launch of DeepSeek and R1 and R1.0. I'm curious if you noticed that, and if it changed your views at all on LLMs and how they might work.
46:01 Speaker 01 Certainly. So we did notice that. That was obviously a big development that captured everybody's collective intelligence and attention still now. And so that was a big surprise, hard not to notice it. I think less concerned in terms of military application, in terms of what we're working on, what that might mean, because you know, we're still trying to figure out end-to-process policy issues, use cases, applications on how to use existing US sort of AI systems that are already kind of being on-boarded into the Department of Defense to do our mission more effectively. I think there's so much to work out there. It's a bit like running a race in this way. So if you're running a race, right, do you focus on running your race and hitting your marks and finishing on time and pacing yourself?
46:46 Speaker 01 Or, you know, are you looking at your competition the whole time? And I think in this case, there's so much work to be done and so much value to be garnered from the technology that exists within the US sector right now. You know, we're really focusing on the opportunities that we have and what we can do as opposed to things outside of our control. And I think, again, it's one of these factors. And the best LLM will never replace a good soldier, sailor, airman, or marine. And having, you know, people who are brave, courageous warriors willing to go out and be part of a team to do this is so much more important than a 10, 20% competitive advantage between large language models right now, that, you know, I think we're best off focusing on what we have and making the most of it. And, you
47:29 Speaker 01 know, I think there's, again, there's so much ground to be gained by doing that, that I don't think we need to be overly concerned about what capabilities exist from other countries right now. Because I don't think anybody has really fully and completely garnered the value that is available from technology like this yet. So I think the people that will be best off are the ones who integrate it best, train with it best, and teach people how to use it best, do their jobs, as opposed to a 20% performance improvement on an ARC, you know, baseline.
47:57 Lukas Biewald? I think one of the things that you mentioned to me earlier was also that you, I think you said you wrote out like a white paper on getting people to use AI better, or something like that. That actually, we didn't find that in our, in our research on you, but that seemed really interesting. Could you describe a little bit of what that was? And maybe is there a pointer to that that we could find and put in the show notes if it's, if it's publicly available?
48:20 Speaker 01 Yeah, thanks. I appreciate that. It's a paper that's under review right now, under Academic publication. I like to do some academic publications with some colleagues in the Navy. And so that's a work that's that's still happening now. So it's probably why you didn't notice it. I did have a publication in technologies earlier about using AI metrics and in continuous improvement and to take a look at where we're at and to make advances there. And there's an upcoming publication in IEEE about an agility readiness level using AI and contracting approaches and organizational agility to get the correct contracting approach. But the one that you're referring to, I'm really excited about, which is leadership behaviors that will enable organizations to adopt AI and technology better.
49:03 Speaker 01 And it really happened because we started bringing in some early pilot programs into our particular team. And adoption was at first slow. And what was happening is that my teammates were concerned that it would be negatively perceived if they were using AI to do or help do their job better. And so there was an adoption problem that I recognized early on.
49:33 Speaker 01 Now, I've seen the research that does something like a 25% improvement through consultants that use AI tools to do their job. And these are highly trained, really intelligent people that are getting, you know, double-digit boosts in productivity by doing it. So I knew it was important for us to do. And so I started just asking the question as a leader, what can I do to improve the adoption of AI throughout my organization? And as funny as it would sound, the most effective thing I found, I like to interface with people one-on-one or with groups in my office in person or over teams. And if there was a question that would come up or something that I didn't know, I used to ask the people in the office, hey, what is this thing? Like, we would talk about it and they would bring me up to speed on a particular aspect. I started just asking our AI assistants for that instead.
50:16 Speaker 01 But I wouldn't do it in a way where I would obscure the fact that I was asking these questions to my tutor, assistant, AI agent that I would interface with. I would turn the screen towards my team in the middle of the meeting. I typed the question in some cases while the conversation is still happening. I would generate the response and then I would say, hey, there's these things that we hadn't considered. And they would like read it with me and and all of a sudden, within a week or two of starting this like very simple behavior. My other senior leaders who were in these meetings with me started doing the same thing with their teams, started sending me products that were better organized, that were better structured, that had better review and thought behind them. And I would ask them about it and they said, oh, we just started using the same tools you did. And what they realized is that instead of me negatively looking down on them as teammates
51:00 Speaker 01 and leaders for using AI, I was encouraging them to do it. And I wanted to see the output of it, right? Again, they're responsible for their work. They can use the tools as they want. They have to cover all the right policy things. But it just started me asking the question, what are the leadership tools that we can do and use and demonstrate as leaders so that our teams feel safe and have the psychological safety and are backing so that they can adopt these tools? So there's actually one of the AI researchers, she's at Georgetown and she's at AWS right now. We're co-authoring a paper that we hope to present in Switzerland on these leadership behaviors. It's under review right now. When it's published, we'll send you a link to it. Hopefully it gets accepted for publication. But it's really around the human aspects of adopting AI in teams and incentivizing people to do that in a way that they're still accountable. And so we're continuing
51:44 Speaker 01 to explore kind of behaviors, whether they be training sessions for everybody to understand what the capabilities are, rolling out new tools and expressing excitement and enthusiasm about that, demonstrating leadership behaviors where we're using these tools and encouraging our teams to see us using these tools, integrating them into existing workflows. You know, this is going to seem silly because probably most people are doing this already. But I would ask everybody to make a transcript of every team's call that we had so we could download the text. Now we have NLP. And my thought was if we ever did need to build a repository and perform RAG, we wouldn't have to download all of our program documents. We just pull our transcripts and it would have our conversations and maybe it would know us. And now we could interface with agents who had access to everything that we had said in these transcripts that we controlled. And the compression of information is so amazing when you go from
52:29 Speaker 01 spoken language and video into a text transcript that like this is just another one of these leadership behaviors where you say like, hey, where's the transcript? Where do they go into the repository? How do we, you know, structure our file folders so that we can, you know, get to these and so that an agent can make sense of what program we're talking about based on just where we put the transcript? And so all of these were things that I started kind of unpacking as a team. And I've seen some positive responses. So, you know, if you've got some best practices there, maybe partner on that paper together in the future.
52:57 Lukas Biewald? I mean, it sounds like I could learn from you. I don't know. That that seems fantastic and really interesting and and cool that you have space to both. Innovate in your leadership in that way and then also space to, you know, publish research about it so that people can can learn from that.
53:14 Speaker 01 I'm really, I'm really fortunate. I have a medical in my, my part of my portfolio is medical. So I have these PhDs in physiology that are part of my team that work for me. And so one of them was really big into AI. And when I started talking about publishing peer reviewed journal, this is eyes lit up. And so we would sort of come up with these topics and we would submit these for publication. We partner with academic institutions that would go through the review that the Navy had done. And I've actually published more academic papers and I'm going to get into IEEE, which I'm super thrilled about. But I published more now, you know, 20 years out of grad school than I did when I was getting my master's degree. So I'm kind of like, you know, really proud of that.
53:47 Lukas Biewald? That's really, really cool. And it's, it's amazing, the breadth of topics, right? From like LMS and leadership to, to contracting to, I think we've, they have a paper on the, the the underwater mine finding also, right?
54:06 Speaker 01 For sure.
54:07 Lukas Biewald? Yeah.
54:07 Speaker 01 Yeah, absolutely. And so it's, I love this job because it's so broad in application. We get to look at so many things. And you know, it's funny, I swim in this every day. So I understand how it works in the government to put things on contract, to test things, to structure a contract, to award mods and options, to work with the Defense Innovation Unit, to evaluate commercial solutions. I'm like, yeah, of course, everybody knows this, like, I want to learn the tech part of it. So I turned out to be like more technical than most PMs. And when I talk to technical people, they're like, oh, my gosh, you understand how the process works. And so I'm in this really great space where I can draw in experts from these different domains and make a contribution to, you know, whether it be academic work or advancing technologies within the system. And I just sort of let my creativity sort of guide me there and
54:50 Speaker 01 find interested partners who are willing to put in some work with me. And it's, it scratches a lot of itches. And honestly, like, one of the things I'm most nervous about in retirement when that would come is that I don't get to have such a broad breadth and explore things as freely as I do now because I love it.
55:03 Lukas Biewald? I mean, it sounds like you could spin out a company that uses AI and help contract with the government that I think would be wildly successful. You could, you could sign me up first. So.
55:12 Speaker 01 I'm ready when you are, Lucas.
55:15 Lukas Biewald? I guess as a final question, is there any other, are there other topics in AI that you're interested in exploring? Like, is there any kind of research that's like percolating in your mind that you'd want to talk about or applications that you think are coming that you're looking into that you haven't had a chance to publish?
55:32 Speaker 01 Multi-agent collaborative autonomy, to me, is such an interesting topic that's so underserved that I would love to take a look at how information interchangeability and interoperability could work with robotic systems on the battlefield. And so, you know, I think about all these robots that are going to come and all these sensors who are all in different file formats, who are generating streams and streams of information that we're generally not paying attention to. How do you sift through that, find the signal from the noise? And then how do you build the right agents at the right levels to perform the right functions with interoperability between the agents, with data interoperability also? Which, again, like, I'm so fascinated by this idea, because in my mind, I picture
56:17 Speaker 01 a four-person team that's out on a boat that's going to use these vehicles to run a mission, right? They have to plan the mission. That's just done by hand by now, by entering a bunch of data points in, it's pre-programmed and it runs. But like, what if the data that's being generated in the mission dynamically with like an AI agent helps the human being re-task and replan that mission more effectively, right? And then that data percolates up to the next level in the chain of command, who's making decisions about those missions across many ships. And the data interoperability allows that to seamlessly flow in, be compressed properly, and the agents can now talk to each other. So the next agent understands what's happening at the individual missions and what it means to the larger operation. And that just keeps flowing up to agents who can communicate and interoperate with each
57:01 Speaker 01 other, interoperability. And they're tuned to the right level of the chain of command that they would have to support, so that the agent who's trying to figure out if the thing you're looking at is a mine or a rock. Shares the same data, but does a different function than the agent that says, here's where we need to put all the ships that are across the entire battlefield right now. And so I think it's so interesting to look at multi-agent collaborative autonomy, where the agents have interoperability of the data and the information, perform different tasks, but can feed into each other's decision-making process in a dynamic, real-time, connected way. That would just be amazing to explore and pack and cover and develop. That's the first.
57:42 Speaker 01 The second would be like an LLM specifically designed to support the use cases within sort of these operations and tailored to do just that. That's that would. So that example of Nimitz to Halsey, that was a message. Those were words that were improperly written, that were improperly understood, and the mission never happened. Imagine if that could never, it would never happen again, because these intelligent assistants would be like perfectly tuned to how to do that. And the person who receives the message could ask exactly what was happening to the agent. And that was the same agent that wrote the mission on one end, right? The data compression happened at the agent level, not in the communication of the words itself. And so I think those two things are kind of what's on my mind right now, and I would love to explore those more.
58:27 Lukas Biewald? You know, I think you really bring an interesting lens to that, because it seems like you're very oriented towards the way kind of humans collaborate and work together. And you view that as more important than the technology, clearly. But then I feel like you're sort of applying that focus on communication to technology and kind of getting agents to collaborate well and work together as a team. And then also kind of focus on like message passing with clarity. It seems like it's a real thread.
58:54 Speaker 01 It's the fog of war. It is, and it's the fog, it's like the Von Costerwitz thing. The fog of war is so difficult to get through. You're tired, you're exhausted, the adrenaline is pumping. It's broken messages, data is sparse. You're trying to make sense of that on the battlefield, like how much progress we could make by solving that problem. And it's, everything is a human problem at the end of the day, right? And so that's why technology is meant to enable and empower humans, not replace us, particularly on the battlefield, no matter how good it gets. And so making that more efficient, faster and easier is like, is super interesting to me and outsized returns from doing that, just completely outsized returns based, you know, when you compare that to, you know, Mach whatever on an airplane,
59:38 Speaker 01 like it's not even close to the benefits you would get.
59:41 Lukas Biewald? You know, I have to ask you, I feel like a lot of my, my friend entrepreneurs, CEOs that have never been anywhere near a battlefield and don't know anything about it, love, there's like a quote, I think that's a, I think it's a general said that like amateurs talk strategy and professionals talk logistics. Is that a real quote? Is that something that, do you think, does that ring true to you in your field?
1:00:02 Speaker 01 It's used all the time, whether it's an actual quote or not, that's a truism that's used all the time. That's absolutely the case. So in my world, I develop capability and then I field capability out to the, the Navy, right? And so what I would say is the sort of analogy that I make is amateurs get excited about working prototypes.
1:00:21 Lukas Biewald? Nice.
1:00:21 Speaker 01 Like, oh my gosh, we found this thing that works. It's like, hey, stop, like, everything works at some point. It doesn't work well enough for us. It's not hardened yet. Like, that's 5% of the problem is like something that works. And so that is so true that amateurs get excited about like, oh, hey, there's this thing. Should I turn left or right? Like, the tactic that's involved. And the professionals are like, we have an army to resupply. How do we get enough food so we don't starve? Like, questions that you just wouldn't think about if you're so excited about the tactical part. And the way that translates into my world is, hey, tech that might work, might not work for us. And understanding that that difference is a huge gap. And the skill set to close that is really difficult to get and takes a lot of time and energy and effort to do. And so professionals ask about sustainment,
1:01:06 Speaker 01 fielding, cybersecurity, policy compliance, and not just about how effective the system is. Effective systems are table stakes. But it doesn't get you there.
1:01:16 Lukas Biewald? Awesome. And right there, that's a great, great one to end on. Thanks, John.
1:01:20 Speaker 01 Thanks, Lucas.
1:01:20 Lukas Biewald? That was fantastic.
1:01:21 Speaker 01 Appreciate it.
1:01:21 Lukas Biewald? Really appreciate it. Thanks so much for listening to this episode of Grading Descent. Please stay tuned for future episodes.
Previous The rise of AI agents Next Inside the Dark Web, AI and Cybersecurity with Christopher Ahlberg CEO of Recorded Future Page updated November 3, 2026 · transcript and summary are machine-generated
