 Welcome to one of the world's premier institutions. And one of the things that no doubt you've heard this past week that makes Stanford so great is the purposeful engagement opportunities and experiences that Stanford makes available to students. And one of the really interesting ways that Stanford does this is through project-based courses, much like ETC that you just heard about, but also through hacking for defense. So there are 10 experiential based project-based courses on campus, and two of them, ETC and hacking for defense, relate specifically to energy. Hacking for defense looks at a wide swath of national security issues, but there's a specific subset that we dial into that looks at securing and protecting the U.S. energy network. Now I just want to begin to tell you a little bit about hacking for defense by telling you a story about a previous project. SEAL Team 1 sponsored a project and they came to Stanford and Stanford Hacking for Defense and said, hey, we've got this pretty big problem. Our divers spend too much time underwater and have adverse health consequences because of it. So what we'd like you, Stanford Hacking for Defense team, is to create a wearable or a fit bit so that we can monitor vital signs like blood pressure, core temperature, and depth. And so the student team said, yeah, sure, no problem, we can do that. But what the student team didn't know when they accepted this problem was that in order for you to be successful in the hacking for defense classroom, a requirement is for you to get off campus and start talking to real people and understand what the problem really is. And that's exactly what the team did. In this case, the team went out and spoke with commercial divers, military divers, as well as people involved in the commercial diving industry. And what they learned the first week was pretty frustrating for them. They have learned that military divers will not wear a fit bit or a wearable. And the team was really interested in this and said, why, why wouldn't you do this wearable? The SEAL team told us that we, our problem sponsors said that we needed to build this. And they said, let me tell you something, I've worked my butt off to be a SEAL diver and someone seeing that my blood pressure is a little higher, my core temperature is a little low, isn't going to be taking me off the mission. I'm dedicated to the mission. So hat in hand, the team went back to their problem sponsors and said, hey, look, you wanted us to build a wearable, we can build a wearable, but we've just found out that the divers won't wear it. But we have spoken with some other people in industry and we've realized that the real problem is that they're spending too much time under water and they're spending too much time under water because they can't see where the heck they're going. Where it makes a lot of sense from going from point A to point B on land, it's pretty easy. When you're under water and you can't really see very well and you can't get a GPS lock unless you spend about five to 10 minutes going to the surface to poke your antenna out of the water, get that GPS lock, spend five more minutes re-submerging and then moving on to the mission. Well, we think that if we heck and solve the navigation problem, we can solve the problem you have with mitigating health consequences. So the SEAL team one gave them a big thumbs up and said, okay, let's see how this pans out. And what ended up happening was the team built a GPS beacon or buoy whereby the SEALs at depth could just release it. The buoy would give them a GPS lock. They could bring it back down and then move on with the mission and they would save them approximately 20 minutes of underwater time, which is substantial. They built this prototype in the product realization lab here at Stanford and they tested it at the Stanford swimming pool. And the SEALs loved it and they began to implement it. So this is just one example from the Hacking for Defense projects that had this meaningful and interesting impact. Now I want to do a 180 here. So I told you a little bit about what Hacking for Defense is. Now I just want to bust some myths because with the name Hacking for Defense, a lot of baggage comes with that. So just to be clear, you're not going to be issued a pretty sweet custom ski mask in this course. You won't learn how to hack into your computer or someone else's files. But what you will do, the hacking you will do, much like the example I just gave, is be able to hack through all of the noise that's involved with the problem. Hack through what the government thinks are the solution. And 90% of the time when it thinks the solution is what it needs to solve a problem, it's 90% of the time it's wrong. So hacking through that. Another misconception is when I talk about hacking for defense, usually with guys, their eyes get really big, like I get to build weapon systems. First of all, if you can build a weapon system in 10 weeks, Tony Stark doesn't have anything on you. But we don't do anything offensively related. We don't build weapon systems. We do nothing. None of our projects involves, projects involve offensive capabilities. Instead, what we focus on, very acutely, are solving the problems that men and women in uniform face, making their lives better by protecting them, or potentially by, excuse me, by helping them do their jobs. This thing's moving faster than I can speak. Third thing is a lot of people, especially now on campus, think, well, let's go back here. All right. They think, well, I don't, I can't take hacking for defense. I don't agree with this administration or that administration. I'm not, I don't want to work for the Democrats or I don't want to work for the Republicans. But the fact of the matter is, our problems, again, focus on the men and women in uniform. And those don't change from one administration to the next. The data display problems that someone had during the Obama administration are the exact same problems that, that they have under the Trump administration. And so we're politically agnostic, and we're just really hyper focused on objectively solving problems using the lean startup methodology, methodology. So you've gotten a little bit to know an example of what the class is, and now what the class wasn't and busted some myths. The core goal here, and probably some, a reoccurring theme that you've heard through the week is, we're really focused on giving students an experience and giving them the opportunity to make a profound impact off campus. And we do this through the, the national security space. And there are three core things that we teach our students, how to solve the right problem, and then how to innovate at speed, and then how to deploy or deliver that solution and all using lean methodology. We do it in 10 weeks, the quarter system. So we throw a really gnarly problem at you and say go, and you've got 10 weeks to solve it. And many students report that it's like a startup type atmosphere, which it certainly is. We really dial up the heat and you having interaction with real men and women in uniform helps to bring that to the fore. But you're not left alone. You know, the Stanford, the hacking for defense ecosystem is substantial. First of all, you've got four members of the teaching team, one of which is Steve blank, who many of you have probably heard of. He's the known as the father of modern entrepreneurship. We have a technologist well versed in the space, someone that used that ran DoD innovation in the Pentagon for 30 years. And myself, I've got a special operations background and did some policy work in DC as well. Student teams, one of the great things that you hear about hacking for defense in these classes on campus is its multidisciplinary scope. And the best teams that we have are definitely multidisciplinary. So each course, it just runs in spring. And we have between six and eight teams of four people. Those four people, as I said, the best teams are multidisciplinary, usually have some component of a business school student, another of an engineering student, and maybe a policy or law student as well as a CS student. And the reason is is because and the reason the reason for having a multidisciplinary team and why that's so important is because engineers are really good at building things and they'll just get out and build something. For the case that I gave you initially, they may have built the best wearable on the planet, but it wouldn't have solved the problem. By contrast, policy and business students are really good at discovering the needs and getting to the root of problems, but they may not have the technical expertise to actually build something. And so we're looking for that sweet spot dream team with our teams. Each team works on one problem. Everyone in no problem, no team works on the same problem. So we have six to eight problems per course. And these problems come from all over the Department of Defense. Our problems have ranged from all four services, Army, Navy, Air Force, and the Marine Corps. We've got some interagency problem sponsors, as well as we had the CIA and an NSA problem as well. So lots of gnarly, sexy problems enter our class if you could say defense is sexy. But real learning experiences. Teams also get two mentors, one from the commercial space and one from the defense space. And we hand select our mentors so that they are well versed in lean startups. So this is what they do on a day-to-day basis. And they help our teams walk through the lean methodology and apply that to solving a mission critical task. They also open up their Rolodex and can help point people and introduce team members to people that could help them actually solve the problem, maybe leverage technology in a very interesting way. Our military mentors come from the Hoover Institution, they're senior military fellows, and they help in two ways. They help translate Pentagon speak to civilian speak and back again so that students understand what people are telling them and also understand how to communicate to the community as effectively as possible. They too open up their Rolodex and say, hey, have you talked to Bob or Sally? They would be perfect people for you to speak to to understand this problem a little bit better. So you take this entire ecosystem and you combine it into one and student teams are responsible for doing 10 to 15 interviews a week. So 100 to 150 interviews in a quarter to really understand what the problem is and what solution would align with that problem. The way the class is structured, it's a three hour class once a week and students get to present for between eight to 12 minutes and they present in four things. One is what their hypotheses were about the solution and the problem space going into the week. Two, how they tested those hypotheses by who they spoke with or who they spoke with and how they tested. Three, what they've learned and four, what they're doing moving forward. And Steve, Steve, Pete and I help to provide guidance to help these students problem solve and get to the core of a solution. So it's been a long week. If you take nothing away from what I've just said, just remember three things, please. Hacking for Defense puts real life national security challenges in your lap and allows you and connects you with people experiencing them in government so that you can solve something very meaningfully. In doing so, you'll learn, you'll have skills and experiences that will translate not just to careers in defense, but also the industry side as well, which will in turn help to make strong real world impacts. Just over the summer, one of my former student from the spring quarter got in contact with me and said, hey Jeff, H4D helped me land a job at Google. And I was like, oh, that's cool. How did that happen? And they said, well, I nailed the interview. Sorry. First of all, I got the interview based off of a connection that I've made during one of the interviews in the commercial sector. And second of all, I nailed the interview because they asked me the age old question that interviews commonly asked described me a time where you've dealt with team challenges. And they had a ready made example with with hacking for defense. And the other question of described me a time where you've used what you learned in the classroom in the real world, and they they're able to talk about this as well. So lots of skills you can cultivate here from network building to also be able to cut through bureaucracy and deploy a solution, be it on the commercial side or the defense side. Spring class, lots of things happen before the class. The problems go live. And at the beginning of January, so you can select which problems you think you might be interested in. And then you apply to the class to work on those problems. Lots of things to remember up here. But just go to our website, hackingfordefense.stanford.edu for the number four and sign up put your name down and your email address and we will we won't spam you. We'll we'll send you notifications for when problem statements have gone live. When the applications might be due when we're holding an information session and how you might be able to get in touch with other students interested in the course. I think I'm out of time now. But as Uncle Sam says, we want you for hacking for defense. And please reach out by the the website or email me directly and I'd be happy to answer any of your questions. Yeah, you have to be an American citizen. Oh, great question. No. So you don't need to be an American citizen. It's open to all Stanford students. There is no security clearance required. They're all open source problems. And there's no IP associated with them. So we try to keep it all open source until you graduate from the course. And we actually have some some funding that we can provide to help you move beyond and and create IP around the solution that you that you've generated. Any other questions? Yeah, that's it. That's another good question. See, it varies. All problems aren't created equally. And to be quite honest, as you could no doubt tell from the example I gave you, the way they thought that the problem would have developed is actually quite different than how it actually did. So there's always a core that is valuable to the defense space. And usually it's around it's around really bringing some maturity and some understanding to a problem. But I would say related specifically related to your point about a quarter of our teams continue on either producing that that product in the commercial space to sell to the government or continue working on it in their spare time. Thank you very much. I look forward to seeing you all at spring 2019.