WEBVTT 00:00.490 --> 00:03.289 Welcome to an exploration of human 00:03.289 --> 00:05.610 machine teaming . A groundbreaking 00:05.610 --> 00:08.350 field that amplifies human intelligence 00:08.529 --> 00:10.810 with advanced machines to achieve new 00:10.810 --> 00:13.600 heights of efficiency , decision making , 00:13.890 --> 00:16.620 and operational excellence . Human 00:16.620 --> 00:20.049 machine teaming , or HMT for short , is 00:20.049 --> 00:22.569 a powerful force reshaping our defense 00:22.569 --> 00:24.579 where decisions that carry immense 00:24.579 --> 00:27.610 implications for global security and 00:27.610 --> 00:30.299 the safety of American forces often 00:30.299 --> 00:31.979 must be made in seconds . 00:37.549 --> 00:40.400 So , what exactly is human machine 00:40.400 --> 00:43.630 teaming ? In essence , HMT is about 00:43.630 --> 00:46.169 collaboration between humans and 00:46.169 --> 00:48.113 machines , where each brings their 00:48.113 --> 00:50.330 unique strengths to the table . While 00:50.330 --> 00:52.330 machines excel at processing vast 00:52.330 --> 00:54.689 amounts of data quickly , humans are 00:54.689 --> 00:56.490 irreplaceable for their ethical 00:56.490 --> 00:59.569 judgment , creativity , and ability to 00:59.569 --> 01:01.689 operate in uncertain environments . 01:01.869 --> 01:04.330 Together , humans and machines create 01:04.330 --> 01:07.169 teams that are smarter and faster than 01:07.169 --> 01:10.000 either could be alone . In my simple 01:10.000 --> 01:12.919 mind , it's about in an increasingly 01:12.919 --> 01:16.160 complex world marrying the strengths of 01:16.160 --> 01:18.720 humans with the strengths of machines . 01:18.879 --> 01:21.046 Humans have strengths and weaknesses . 01:21.046 --> 01:23.323 Machines have strengths and weaknesses , 01:23.323 --> 01:25.379 and I think that the marriage of the 01:25.379 --> 01:27.379 strengths and weaknesses of the two 01:27.379 --> 01:29.839 allow us to do that at a , at a , at a 01:29.839 --> 01:31.450 level that we , we need to , 01:31.450 --> 01:33.450 particularly in military operations 01:33.450 --> 01:35.617 which are , you know , very complex by 01:35.617 --> 01:37.506 nature . The real tenets of human 01:37.506 --> 01:39.339 machine teaming involve a lot of 01:39.339 --> 01:41.506 flexibility . The idea that humans and 01:41.506 --> 01:43.617 machines can work together jointly on 01:43.617 --> 01:45.672 really complex tasks , and the whole 01:45.672 --> 01:47.895 notion of the benefits of human machine 01:47.895 --> 01:49.728 teaming are that you could get a 01:49.728 --> 01:51.783 machine to start to work proactively 01:51.783 --> 01:53.783 with a person , right ? So , um , a 01:53.783 --> 01:55.783 human might be able to . Leverage a 01:55.783 --> 01:57.450 machine to do some breadth of 01:57.450 --> 01:59.617 information analysis or acquisition to 01:59.617 --> 02:01.228 allow the machines to filter 02:01.228 --> 02:03.395 information for us or to build courses 02:03.395 --> 02:04.950 of action analysis sorts of 02:04.950 --> 02:06.783 capabilities in a very rapid way 02:06.783 --> 02:08.672 because machines are great at the 02:08.672 --> 02:10.839 compute , humans are great at decision 02:10.839 --> 02:10.330 making , and so when you pair the two 02:10.330 --> 02:12.330 together , greatness is a potential 02:12.330 --> 02:14.497 there . So the way I think about human 02:14.497 --> 02:16.608 machine taming technology is really , 02:16.608 --> 02:18.386 the machine is a tool , and the 02:18.386 --> 02:20.441 question is what do we want it to do 02:20.441 --> 02:22.608 with what information we want it to do 02:22.608 --> 02:24.497 it with . The goal of the tool is 02:24.497 --> 02:24.330 really to help us have a relationship 02:24.330 --> 02:26.729 with knowledge at speed and scale . In 02:26.729 --> 02:29.610 practical terms , this means developing 02:29.610 --> 02:31.929 systems that augment human decision 02:31.929 --> 02:34.285 making . By providing machines the 02:34.285 --> 02:37.485 autonomy to perform repetitive or 02:37.485 --> 02:39.955 computationally intensive tasks , 02:40.524 --> 02:42.691 freeing up human operators to focus on 02:42.691 --> 02:45.285 strategy , ethics , and creative 02:45.285 --> 02:47.274 problem solving . The Air Force 02:47.274 --> 02:49.354 Research Laboratory plays a central 02:49.354 --> 02:51.845 role in advancing human machine teaming 02:51.845 --> 02:54.679 technologies . As the world becomes 02:54.679 --> 02:57.399 increasingly complicated with threats 02:57.399 --> 03:00.350 that are volatile , uncertain , complex , 03:00.479 --> 03:02.960 and ambiguous , or what's often 03:02.960 --> 03:06.309 referred to as Luca , the need for HMT 03:06.309 --> 03:09.699 is more critical than ever . AFRL aims 03:09.699 --> 03:12.179 to create systems that allow military 03:12.179 --> 03:14.580 personnel to make faster , more 03:14.580 --> 03:17.460 informed decisions . We've always at 03:17.460 --> 03:19.820 AFRL had a history of teeming with 03:19.820 --> 03:22.042 machines , whether those are the planes 03:22.042 --> 03:24.264 we put in the air , uh , you know , the 03:24.264 --> 03:26.699 unmanned vehicles , or whether that are 03:26.699 --> 03:29.339 the computers or other types of sensor 03:29.339 --> 03:31.500 technology . The reality is we always 03:31.500 --> 03:33.722 need to have an advantage when it comes 03:33.722 --> 03:35.889 to our relationship with information . 03:35.889 --> 03:38.835 and knowledge . So , at AFRL we define 03:38.835 --> 03:41.875 autonomy as giving some computer agent 03:42.154 --> 03:44.835 a delegated and bounded authority to 03:44.835 --> 03:47.154 take actions in space . So a lot of our 03:47.154 --> 03:49.098 work is , how do we make sure that 03:49.098 --> 03:51.235 humans can properly communicate what 03:51.235 --> 03:53.457 the delegated authority is that's given 03:53.457 --> 03:55.457 to that agent , and how do we build 03:55.457 --> 03:57.457 systems that are watchdogs that can 03:57.457 --> 03:59.624 monitor what this AI is going to do to 03:59.624 --> 04:01.568 make sure that the bounds that the 04:01.568 --> 04:03.679 humans give it are always held . We , 04:03.679 --> 04:05.735 of course , because we're an applied 04:05.735 --> 04:07.902 research lab , we develop technologies 04:07.902 --> 04:09.902 that support directly human machine 04:09.902 --> 04:12.068 teaming applications across the deaf . 04:12.169 --> 04:14.559 And so that involves working with 04:14.559 --> 04:16.503 programs like collaborative combat 04:16.503 --> 04:18.059 aircraft with ISR systems , 04:18.059 --> 04:19.837 intelligence systems , could be 04:19.837 --> 04:21.837 maintenance related systems . So we 04:21.837 --> 04:24.003 build actual technologies that support 04:24.003 --> 04:26.170 these programs and support these needs 04:26.170 --> 04:28.226 across theA and of course across the 04:28.226 --> 04:30.059 space force as well . So AFRL is 04:30.059 --> 04:32.003 investing in human machine teaming 04:32.003 --> 04:34.115 because we think this is an area that 04:34.115 --> 04:35.959 has the potential to deliver 04:35.959 --> 04:37.915 transformative technologies . For 04:38.274 --> 04:40.394 future war fighting missions in all 04:40.394 --> 04:42.674 domains , we hope that these 04:42.674 --> 04:45.595 technologies will expand the scope and 04:45.595 --> 04:47.954 capabilities of military operations by 04:47.954 --> 04:51.154 accelerating the decision cycle of the 04:51.154 --> 04:54.475 human operator while at the same time 04:54.475 --> 04:57.595 reducing the risk on the human by 04:57.595 --> 04:59.994 allowing them to remove themselves from 04:59.994 --> 05:02.755 the highest risk aspect of the missions . 05:03.589 --> 05:05.149 Human machine teaming will 05:05.149 --> 05:08.190 revolutionize military operations . 05:08.549 --> 05:10.493 Imagine a future battlefield where 05:10.493 --> 05:12.309 unmanned aircraft collaborate 05:12.309 --> 05:15.709 seamlessly with human pilots , or where 05:15.709 --> 05:17.670 autonomous systems help analyze 05:17.670 --> 05:19.549 enormous data streams to provide 05:19.549 --> 05:21.820 commanders with actionable intelligence 05:21.820 --> 05:25.510 in real time . We live in an 05:25.510 --> 05:29.299 increasingly uh technology rich world . 05:29.950 --> 05:32.117 I think if you look at the speculation 05:32.117 --> 05:34.309 of where military operations will go 05:34.309 --> 05:36.630 into the future and , and uh 05:36.630 --> 05:39.549 understanding that we need to maybe 05:39.549 --> 05:43.220 shift our thinking from few exquisite , 05:43.510 --> 05:47.339 very costly things to smaller , 05:47.600 --> 05:50.795 cheaper things , the , the battle . The 05:50.795 --> 05:53.195 field is going to be littered with more 05:53.195 --> 05:55.635 and more machines and therefore the 05:55.635 --> 05:57.635 ability of humans to interface with 05:57.635 --> 06:00.315 those machines in a synergistic and 06:00.315 --> 06:02.093 coherent way is going to become 06:02.093 --> 06:04.204 increasingly important . Machines are 06:04.204 --> 06:06.037 great at computes . Machines can 06:06.037 --> 06:08.259 process things that humans can't fathom 06:08.259 --> 06:10.426 in terms of speed and , and breadth of 06:10.426 --> 06:12.648 information analysis that they can do . 06:12.648 --> 06:14.593 So why not try to leverage that as 06:14.593 --> 06:16.926 humans ? We're great at decision making , 06:16.926 --> 06:16.709 we're great at pattern recognition . 06:16.890 --> 06:18.970 We're great at creativity . So the 06:18.970 --> 06:21.160 thing is , how can we get machines to 06:21.410 --> 06:23.489 play into that whole process ? So 06:23.489 --> 06:25.545 understanding what the humans do and 06:25.545 --> 06:27.267 use the machines as a means to 06:27.267 --> 06:29.489 accelerate what they're doing already . 06:29.489 --> 06:31.433 Human machine teaming is important 06:31.433 --> 06:33.433 because without it , we will lose . 06:33.649 --> 06:37.600 Without using the augmentation , the 06:37.600 --> 06:39.767 relationship with knowledge , and with 06:39.767 --> 06:41.933 the machines that we have at speed and 06:41.933 --> 06:44.450 scale , we will no longer maintain the 06:44.450 --> 06:46.649 dominance in the future battlescape or 06:46.649 --> 06:50.369 battlefield . So , it is not an if we 06:50.369 --> 06:52.410 do human machine teaming or we use 06:52.410 --> 06:54.859 artificial intelligence . It is a must , 06:55.130 --> 06:58.519 and we must use it better , faster , 06:58.609 --> 07:01.440 with more curiosity , more optionality , 07:01.529 --> 07:03.760 and more advantage than the adversary . 07:03.970 --> 07:06.929 It's incumbent upon us to be able to 07:06.929 --> 07:08.929 understand these new technologies , 07:08.929 --> 07:11.649 especially AI that is coming out , and 07:11.649 --> 07:14.720 be able to adopt and integrate them 07:14.929 --> 07:17.151 with our war fighting . Systems to make 07:17.151 --> 07:19.318 them better and the reason for that is 07:19.318 --> 07:21.429 that our adversaries are also working 07:21.429 --> 07:23.816 on it and our adversaries are 07:23.816 --> 07:26.038 developing technologies just as fast as 07:26.038 --> 07:28.094 we could . So for every bomb that we 07:28.094 --> 07:30.316 make , they have an equivalent bomb for 07:30.316 --> 07:32.316 every missile , every airplane they 07:32.316 --> 07:34.538 have . So our adversaries are achieving 07:34.538 --> 07:36.705 technological parity . So what will be 07:36.705 --> 07:38.872 the differentiator in a future war ? I 07:38.872 --> 07:40.927 think the differentiator will be the 07:40.927 --> 07:43.038 ability for us , for the war fighters 07:43.038 --> 07:45.038 who can better integrate with the . 07:45.038 --> 07:47.971 Machines and develop this truly unique 07:47.971 --> 07:50.772 symbiotic human machine teaming system 07:50.921 --> 07:53.462 that will be better than any weapons or 07:53.462 --> 07:56.062 any single warfighter and that can give 07:56.062 --> 07:58.062 us a decisive advantage over our 07:58.062 --> 08:00.173 adversaries . So that is why it is so 08:00.173 --> 08:02.502 important to invest and adapt and adopt 08:02.502 --> 08:05.622 these technologies now . But human 08:05.622 --> 08:07.511 machine teaming isn't without its 08:07.511 --> 08:09.742 challenges . One of the most crucial 08:09.742 --> 08:12.592 factors for success of HMT is trust . 08:13.250 --> 08:15.417 How can we ensure that operators trust 08:15.417 --> 08:17.472 the machines and can confidently use 08:17.472 --> 08:20.170 this capability ? Just like you need to 08:20.170 --> 08:22.392 have trust in your wingman or partner , 08:22.609 --> 08:24.553 we need to build the same level of 08:24.553 --> 08:26.720 trust with machines if we want them to 08:26.720 --> 08:28.890 help us win . One of our really big 08:28.890 --> 08:30.850 challenges in human AI teaming is 08:30.850 --> 08:32.739 making sure that we appropriately 08:32.739 --> 08:34.906 calibrate trust to the capabilities of 08:34.906 --> 08:37.128 the autonomy . So we don't want a human 08:37.128 --> 08:39.580 operator to overtrust AI and use it in 08:39.580 --> 08:41.858 situations that it wasn't designed for , 08:41.858 --> 08:44.080 but we also don't want it to undertrust 08:44.080 --> 08:45.969 and not use it when it was better 08:45.969 --> 08:48.080 suited to deal with that technology . 08:48.080 --> 08:50.080 We're really looking for this trust 08:50.080 --> 08:49.780 calibration where they appropriately 08:49.780 --> 08:52.020 trust it in the situations it was 08:52.020 --> 08:54.131 designed for . So first , let's think 08:54.131 --> 08:56.409 about how do we even define trust . So , 08:56.409 --> 08:58.464 when we're thinking about trust of a 08:58.464 --> 09:00.820 human , and autonomous or human AI team , 09:01.190 --> 09:03.023 we're thinking about the human's 09:03.023 --> 09:05.246 willingness to accept vulnerability and 09:05.246 --> 09:07.301 situations that are characterized by 09:07.301 --> 09:07.109 uncertainty because they believe that 09:07.190 --> 09:09.023 that autonomy is gonna help them 09:09.023 --> 09:11.079 achieve the mission that they need . 09:11.190 --> 09:13.469 Yeah , I mean , I think there's this 09:13.469 --> 09:16.030 concern that at some point things are 09:16.030 --> 09:18.849 gonna go what I would call sentient . I 09:18.849 --> 09:20.793 think that's the concern . I think 09:20.793 --> 09:22.960 that's a misplaced conception based on 09:22.960 --> 09:25.010 my understanding of technology . I 09:25.010 --> 09:28.809 certainly understand uh the fear , but 09:28.809 --> 09:32.450 we are gonna have the right . Risk 09:32.450 --> 09:34.561 posture for anything we develop based 09:34.561 --> 09:36.690 on uncertainty developed by test and 09:36.690 --> 09:38.746 engineer . I mean , it's going to be 09:38.746 --> 09:40.746 underpinned . We've really tried to 09:40.746 --> 09:43.023 push the idea of responsible use of AI . 09:43.023 --> 09:45.023 So across society , you've probably 09:45.023 --> 09:46.746 seen concerns about artificial 09:46.746 --> 09:48.912 intelligence and things like bias . In 09:48.912 --> 09:51.023 our view within the Air Force , we're 09:51.023 --> 09:53.134 trying to push the idea that machines 09:53.134 --> 09:55.190 don't really have ethics . When they 09:55.190 --> 09:57.357 can understand context , we might have 09:57.357 --> 09:59.523 a different conversation , but at this 09:59.523 --> 10:01.634 point in , in , in where the state of 10:01.634 --> 10:03.357 the art is , they can't really 10:03.357 --> 10:05.523 understand context all that well . And 10:05.523 --> 10:07.690 so in our view , it's hard for them to 10:07.690 --> 10:09.857 ingest ethics , right ? So the best we 10:09.857 --> 10:11.968 can do is try to push for responsible 10:11.968 --> 10:15.650 use of AI , but building . that trust 10:15.650 --> 10:19.570 factor into the operators , into , and 10:19.570 --> 10:21.848 I think this is where the lab can help , 10:21.848 --> 10:23.959 you know , demystify things . I think 10:23.959 --> 10:26.070 it's gonna be very , very important , 10:26.070 --> 10:28.014 but if our folks don't trust it to 10:28.014 --> 10:30.181 utilize it in an effective manner on a 10:30.181 --> 10:32.690 time scale of relevance , It really 10:32.690 --> 10:35.169 doesn't matter . Human centered design 10:35.169 --> 10:37.210 is another critical element in the 10:37.210 --> 10:40.289 development of H&T technologies . For 10:40.289 --> 10:42.690 these systems to be successful , they 10:42.690 --> 10:45.049 must be built with the human user in 10:45.049 --> 10:47.619 mind from the very beginning . Yes , so 10:47.619 --> 10:49.508 how important is the human in the 10:49.508 --> 10:51.508 human-machine teaming equation ? Of 10:51.508 --> 10:54.039 course , it's critical . And this is a 10:54.039 --> 10:56.200 point that if you , if you work in 10:56.200 --> 10:57.559 isolation outside of a 10:57.559 --> 11:00.039 multidisciplinary space , it's probably 11:00.039 --> 11:01.983 easy to forget the human if you're 11:01.983 --> 11:04.095 someone building hardware or building 11:04.095 --> 11:06.150 software . You're just trying to put 11:06.150 --> 11:08.095 out the best solution that meets a 11:08.095 --> 11:10.317 particular need , right ? But the human 11:10.317 --> 11:12.428 is critical because at any point , at 11:12.428 --> 11:14.428 some , at least at some point , the 11:14.428 --> 11:14.280 human is gonna have to use that 11:14.280 --> 11:16.391 technology . So I think there's often 11:16.391 --> 11:18.336 misconceptions about human machine 11:18.336 --> 11:20.558 teaming . I think the first one is that 11:20.558 --> 11:23.809 the machine somehow matters more . It 11:23.809 --> 11:25.920 doesn't , right ? Again , the machine 11:25.920 --> 11:27.976 just does what we tell it to do with 11:27.976 --> 11:30.031 what we tell it to do it with . So I 11:30.031 --> 11:32.031 think the most important thing that 11:32.031 --> 11:34.253 people should think about when we think 11:34.253 --> 11:36.365 about human machine teaming is how do 11:36.365 --> 11:38.198 we want to show up ? What is the 11:38.198 --> 11:40.198 humanity we're bringing to it ? And 11:40.198 --> 11:42.198 more importantly , are we coming in 11:42.198 --> 11:44.198 with that learning mentality , that 11:44.198 --> 11:46.031 consistent learning , you know , 11:46.270 --> 11:48.710 opportunity , and are we adapting as we 11:48.710 --> 11:50.710 learn ? I think that's gonna be the 11:50.710 --> 11:52.909 most interesting and most important 11:52.909 --> 11:54.965 part of human machine teaming in the 11:54.965 --> 11:57.390 future is really how do we show up . In 11:57.390 --> 11:59.223 addition , we're taking a lot of 11:59.223 --> 12:01.168 lessons learned from the Automatic 12:01.168 --> 12:03.001 collision avoidance Technologies 12:03.001 --> 12:04.834 program , which had 3 high Level 12:04.834 --> 12:06.946 requirements . The first was to do no 12:06.946 --> 12:09.168 harm . Second was to do not interfere , 12:09.168 --> 12:11.501 and the third was to prevent collisions . 12:11.501 --> 12:13.612 So , what our big lesson learned from 12:13.612 --> 12:13.580 that is that there's a lot more 12:13.580 --> 12:16.060 complexity to developing these human AI 12:16.060 --> 12:18.060 teams that just getting the mission 12:18.060 --> 12:20.171 done . We need to ensure that in , in 12:20.171 --> 12:22.227 this case for auto GAS auto ACA , it 12:22.227 --> 12:24.393 was preventing collisions . We need to 12:24.393 --> 12:26.449 make sure that in introducing that , 12:26.449 --> 12:26.411 we're not doing damage to the larger 12:26.411 --> 12:28.633 system and that we also are making sure 12:28.633 --> 12:30.744 that we're not interfering . With the 12:30.744 --> 12:30.692 human when they're trying to do 12:30.692 --> 12:32.803 something . I actually think in human 12:32.803 --> 12:35.091 machine teaming , the human is the most 12:35.091 --> 12:37.313 important , but more importantly , it's 12:37.313 --> 12:39.535 also the most unpredictable . So if you 12:39.535 --> 12:41.702 think about it , if I am going to do a 12:41.702 --> 12:44.281 query or use a particular technology or 12:44.281 --> 12:46.559 design a relationship with the machine , 12:46.559 --> 12:48.611 I'm still inherently influencing it 12:48.611 --> 12:50.692 from my experience and expertise . I 12:50.692 --> 12:52.812 like to joke that my husband wishes I 12:52.812 --> 12:54.868 had a predictable operating system , 12:54.971 --> 12:56.915 right ? That he could put the same 12:56.915 --> 12:59.027 thing in and get the same thing out . 12:59.027 --> 13:00.971 And so oftentimes people will talk 13:00.971 --> 13:02.693 about AI , um , and especially 13:02.693 --> 13:04.804 generative AI as an example and say , 13:04.804 --> 13:06.915 well , how do we get , you know , the 13:06.915 --> 13:08.915 exact same and repetitive and , and 13:08.915 --> 13:10.971 concrete answer ? And the reality is 13:10.971 --> 13:12.749 sometimes you won't because the 13:12.749 --> 13:12.682 knowledge base is changing , but more 13:12.682 --> 13:15.523 than that , you as a human change every 13:15.523 --> 13:17.763 day . If I have an experience , for 13:17.763 --> 13:19.985 example , or we're seeing an experience 13:19.985 --> 13:22.273 unfold in a Battlefield , you know , 13:22.513 --> 13:24.744 far away . We are learning every day . 13:24.953 --> 13:27.744 Our strategy changes every day . Our 13:27.744 --> 13:30.323 information flow changes every day . 13:30.414 --> 13:32.247 And so , in fact , that learning 13:32.247 --> 13:34.193 mentality , that curiosity , that 13:34.193 --> 13:37.874 desire to adapt , to curate at speed is 13:37.874 --> 13:40.713 really important . I think for the 13:40.713 --> 13:42.713 foreseeable future , I don't really 13:42.713 --> 13:44.914 imagine a time in which humans are 13:44.914 --> 13:47.081 going to be taken out of the process , 13:47.081 --> 13:49.414 especially in the Department of Defense . 13:49.414 --> 13:51.470 Humans and AI are always going to be 13:51.470 --> 13:53.636 teaming together in some way , shape , 13:53.636 --> 13:55.747 or form . They're completely critical 13:55.747 --> 13:57.803 to the decision making and enforcing 13:57.803 --> 14:00.424 our norms and our belief systems as , 14:00.465 --> 14:02.424 as a country into , into the 14:02.424 --> 14:04.664 technologies . I would repeat what 14:04.664 --> 14:07.344 Jonah Goldfein once mentioned in one of 14:07.344 --> 14:10.135 his speeches that the future wars will 14:10.135 --> 14:12.585 not be a war of attrition , but war of 14:12.585 --> 14:14.869 cognition . It's true , right ? Our 14:14.869 --> 14:17.549 adversaries are achieving almost a 14:17.549 --> 14:20.830 technological parity with us . Uh , so 14:20.830 --> 14:23.400 it will be the capability of our war 14:23.400 --> 14:25.750 fighters who will many times have to 14:25.750 --> 14:28.729 overcome the negative effect of stress , 14:28.919 --> 14:32.150 of fatigue , of lack of sleep , and 14:32.150 --> 14:34.710 still be asked to perform at their 14:34.710 --> 14:37.469 optimum level in the fog of war and . 14:37.565 --> 14:40.794 That's why investing in technologies 14:40.794 --> 14:43.914 that really integrate the human with 14:43.914 --> 14:46.674 the machine to extend their 14:46.674 --> 14:48.835 capabilities as well as improve the 14:48.835 --> 14:52.025 efficacy of the machines in turn is why 14:52.025 --> 14:54.195 the human element , keeping the human 14:54.195 --> 14:56.705 in the loop is so important and cannot 14:56.705 --> 14:59.515 be ignored because it's not the 14:59.515 --> 15:02.190 machines but human that fight wars . At 15:02.190 --> 15:04.390 the heart of human-machine teaming is 15:04.390 --> 15:06.940 the concept of decision superiority , 15:07.309 --> 15:09.420 being able to make the right decision 15:09.420 --> 15:12.489 faster than an adversary . In a future 15:12.489 --> 15:14.433 where decisions need to be made in 15:14.433 --> 15:17.039 milliseconds , the combination of human 15:17.039 --> 15:19.679 insight and machine speed will be key . 15:20.710 --> 15:23.090 So the Uta loop was created by Colonel 15:23.090 --> 15:25.201 John Boyd , and in essence , it was a 15:25.201 --> 15:27.368 framework that is familiar to a lot of 15:27.368 --> 15:29.590 people in Air Force , Space Force , and 15:29.590 --> 15:31.812 really in DOD generally . And it stands 15:31.812 --> 15:35.530 for observe , orient , decide , and 15:35.530 --> 15:37.752 act . So if you think about it , that's 15:37.752 --> 15:39.609 a very normal process that we go 15:39.609 --> 15:41.720 through to be able to understand what 15:41.720 --> 15:44.090 do we do next . Decision superiority is 15:44.090 --> 15:46.257 about getting ahead of our adversaries 15:46.257 --> 15:49.090 oo loops . So getting faster decision 15:49.090 --> 15:51.409 making , so accelerating our guardian , 15:51.609 --> 15:53.890 our airmen decision making processes 15:53.890 --> 15:55.946 without sacrificing accuracy . So we 15:55.946 --> 15:58.168 talk about the speed of relevance . The 15:58.168 --> 16:00.279 speed of relevance is gonna depend on 16:00.279 --> 16:02.390 what that particular mission set is . 16:02.390 --> 16:04.723 It could be seconds , it could be hours . 16:04.723 --> 16:06.946 We view human machine teaming as one of 16:06.946 --> 16:08.612 the key enablers for decision 16:08.612 --> 16:10.723 superiority because we recognize that 16:10.723 --> 16:12.390 machines bring to the table . 16:12.580 --> 16:14.747 Computational power that we just can't 16:14.747 --> 16:16.858 get as humans . And so we really have 16:16.858 --> 16:18.858 to start thinking about time like a 16:18.858 --> 16:20.913 weapons platform , right ? And , you 16:20.913 --> 16:23.024 know , oftentimes when we think about 16:23.024 --> 16:24.969 human machine teaming or AI , what 16:24.969 --> 16:27.024 we're really doing is wormholing the 16:27.024 --> 16:29.136 Ota loop , right ? We're saying , how 16:29.136 --> 16:31.358 can I have all of those options and how 16:31.358 --> 16:33.191 can I go , you know , from maybe 16:33.191 --> 16:35.191 Orientation to being able to make a 16:35.191 --> 16:37.984 decision faster . Looking ahead , the 16:37.984 --> 16:40.145 future of human-machine teaming is 16:40.145 --> 16:42.664 bright . We're moving towards systems 16:42.664 --> 16:45.145 that can learn and adapt alongside 16:45.145 --> 16:47.905 humans to create teams that can operate 16:47.905 --> 16:50.275 in highly complex environments with 16:50.275 --> 16:53.344 minimal supervision . Today we are 1 to 16:53.344 --> 16:56.224 1 , simplistically , one human to one 16:56.224 --> 16:58.784 jet , one human to 1 spacecraft . In 16:58.784 --> 17:01.006 the future , it's going to be 1 to 10 . 17:01.090 --> 17:04.800 1 to 100 , 1 to 1000 . And human 17:04.800 --> 17:07.319 machine teaming underpins us being able 17:07.319 --> 17:11.050 to effectively operate at speed to be 17:11.050 --> 17:13.217 able to make decisions on a time scale 17:13.217 --> 17:14.939 of relevance . Absolutely , it 17:14.939 --> 17:17.161 underpins all of that . So , one of the 17:17.161 --> 17:19.383 things that I often think about when it 17:19.383 --> 17:21.217 comes to optionality is how does 17:21.217 --> 17:23.439 optionality exist in our world now ? So 17:23.439 --> 17:25.383 if you think about it , if we were 17:25.383 --> 17:27.383 playing tic tac toe , you and I are 17:27.383 --> 17:29.550 both considering about 9 moves that we 17:29.550 --> 17:31.772 can make . If we were playing chess , I 17:31.772 --> 17:33.606 think it's about 36 . If we were 17:33.606 --> 17:35.717 playing AlphaGo , we'd have about 360 17:35.717 --> 17:37.939 different moves that we could make . So 17:37.939 --> 17:40.217 if you think about it , the more moves , 17:40.217 --> 17:39.689 the more complex , you know , the 17:39.689 --> 17:41.745 harder , but again , we're playing a 17:41.745 --> 17:43.839 game . So in some cases , that game 17:43.839 --> 17:45.969 really matters about playing it at 17:45.969 --> 17:48.500 speed . So when I look at a situation 17:48.500 --> 17:50.333 where we may have an adversarial 17:50.333 --> 17:52.667 context , the question for me is , well , 17:52.667 --> 17:55.060 do I want to be able to process 9 17:55.060 --> 17:57.500 potential outcomes or moves , or do I 17:57.500 --> 18:00.310 want to be able to process 360 ? Quite 18:00.310 --> 18:02.477 frankly , I want to be able to process 18:02.477 --> 18:05.339 3000 , right ? Because by being able to 18:05.339 --> 18:07.660 look at all 3000 , what I'm really 18:07.660 --> 18:09.859 doing is in essence saying , where is 18:09.859 --> 18:12.189 my advantage ? And if I can do that . 18:12.322 --> 18:14.661 Rapidly , faster than my adversary . It 18:14.661 --> 18:17.241 also means that I can move faster . I 18:17.241 --> 18:19.391 can maintain first mover dominance , 18:19.562 --> 18:21.442 and that's critical . And that 18:21.442 --> 18:23.553 optionality also hits home for me and 18:23.553 --> 18:25.720 the idea of human-machine teaming in a 18:25.720 --> 18:27.722 very powerful way . And that is the 18:27.722 --> 18:30.521 best options also mean potentially the 18:30.521 --> 18:33.842 lowest loss of life . The future is all 18:33.842 --> 18:36.511 about greater synchrony , um , greater 18:37.052 --> 18:39.904 longitude . learning over time . So at 18:39.904 --> 18:41.904 what point do we get tools that can 18:41.904 --> 18:44.071 start to learn our preferences that we 18:44.071 --> 18:46.237 can maybe set some of those thresholds 18:46.237 --> 18:48.348 for the learning processes themselves 18:48.348 --> 18:50.348 and get them better tuned to us and 18:50.348 --> 18:52.460 more in sync with us as individuals , 18:52.460 --> 18:54.293 right ? Do more work in terms of 18:54.293 --> 18:56.460 getting those interfaces right so that 18:56.460 --> 18:58.404 we can set those bounded delegated 18:58.404 --> 19:00.460 authorities in a flexible fashion so 19:00.460 --> 19:02.515 that the machines are working for us 19:02.515 --> 19:04.460 and not against us . The future of 19:04.460 --> 19:06.682 humanity . Machine teaming is one where 19:06.682 --> 19:08.737 the role of machine is complementary 19:08.737 --> 19:11.071 and not redundant to those of the human . 19:11.086 --> 19:13.676 So in an ideal human machine team 19:14.586 --> 19:17.005 technology , it would combine the the 19:17.005 --> 19:19.395 strength of the human such as reasoning , 19:19.645 --> 19:22.845 perception , contextual adaptation with 19:22.845 --> 19:24.901 the strength of the machine which is 19:24.901 --> 19:27.005 fast processing , unbiased decision 19:27.005 --> 19:28.894 making , while at the same time . 19:29.228 --> 19:31.547 Overcoming the weaknesses of the human , 19:31.628 --> 19:34.427 such as fatigue or bias . And so in the 19:34.427 --> 19:36.628 future I see the human machine team as 19:36.628 --> 19:39.108 the man and the machine come in a truly 19:39.108 --> 19:42.787 symbiotic fashion where the man a human 19:42.787 --> 19:45.828 learn to trust the machine , its 19:45.828 --> 19:48.147 intelligent and decision making 19:48.147 --> 19:50.897 capabilities , and the machine in turn 19:51.287 --> 19:54.890 learn how to understand . And 19:54.890 --> 19:57.300 respond to the human state whether it's 19:57.300 --> 20:00.890 physical or cognitive . And understand 20:01.079 --> 20:03.520 the context and adapt to it , but 20:03.520 --> 20:05.800 perhaps more importantly , understand 20:05.800 --> 20:08.839 our values . Human machine teaming is 20:08.839 --> 20:11.189 not just a technological innovation , 20:11.479 --> 20:13.800 it's a revolution in how we think about 20:13.800 --> 20:16.790 human potential and machine capability . 20:17.319 --> 20:19.520 As we push forward into this exciting 20:19.520 --> 20:22.060 frontier . The collaboration between 20:22.060 --> 20:24.420 humans and machines will unlock new 20:24.420 --> 20:27.400 possibilities in every sector , from 20:27.400 --> 20:30.250 defense to healthcare to everyday life . 20:30.579 --> 20:32.939 Stay tuned , because the future is 20:32.939 --> 20:35.819 coming fast , and it's powered by human 20:35.819 --> 20:36.819 machine teaming .