In this episode, Paul Keutelian, CTO of Applied Atomics, discusses his experience leading teams to tackle complex engineering challenges in the nuclear and advanced industry sectors. He shares insights from his time at SpaceX, including the role of responsible engineers, the importance of ownership, and how to create a culture where mistakes are learning opportunities rather than career setbacks. The conversation explores how Applied Atomics approaches rapid innovation by aligning supply chain capabilities with practical engineering solutions, and how transparency and clear communication enable effective problem-solving. Paul Keutelian also emphasizes the significance of hiring the right team, building collaborative environments, and balancing discipline with creativity to achieve ambitious goals. The episode concludes with thoughts on leadership, accountability, and building companies that empower people to take responsible risks.
Paul Keutelian [00:00:00]:
In my perfect world, if I had a big factory, I would have a countdown clock on the wall, but instead of the time, it would be the amount of uncommitted dollars the company has left. And so that way, everybody has the context. To be.
Matt Gjertsen [00:00:32]:
Probably the best thing about my career, from the Air Force to SpaceX to the rest of the startup world, is all of the interesting and amazing people I have gotten to meet along the way. And our guest today, Paul Cotillion, is certainly one of those people. When I first met Paul, he was the responsible engineer for the helium systems at the Vandenberg launch site for SpaceX. He then went on to do many other amazing things at SpaceX, and he's since gone actually start two different nuclear startups. He's currently the CTO at Applied Atomics, where their goal is to power the next 1000 years of advanced industry. I'm really excited for this conversation because he kind of exemplifies the person who I hope to be talking to with this podcast to kind of bring light into the other side of engineering and tackling tough engineering problems that often doesn't get talked about. Before we get into that discussion, I do want to remind you that if this is your first time listening to the show, make sure you subscribe so you never miss a future episode. And if you are already subscribed, then I would humbly ask that you share this show with at least one other person, because that, after all, is how we grow.
Matt Gjertsen [00:01:47]:
I can't tell you how much it means to me. So with that, let's get into the discussion with Paul Cotillion. Paul, how are you doing today?
Paul Keutelian [00:01:56]:
I'm doing great, Matt. Very happy to be here. Very kind introduction, and I am hopeful that I'm able to share experiences that helps the audience and just happy to be an open book and excited to be here.
Matt Gjertsen [00:02:11]:
Yeah, I'm really excited for this conversation. I was so happy when you said yes to it. To get started, I'd love to start with where you're at right now and kind of what your team is trying to do. What are you trying to do at Applied Atomics?
Paul Keutelian [00:02:23]:
Sure. So we are, like you said, trying to power the next thousand years of heavy industry. And the way we see it is the key enabler to being able to do things like desalination, industrial power, AI data centers, all sorts of things is power. And that seems to be the gatekeeper to all of these things. So what we're trying to do is get to delivering power to our customers as quickly as we can and scale up as quickly as we can, leveraging our experiences from the past to get there.
Matt Gjertsen [00:03:02]:
Incredible. What do you think? Because I think we've had this conversation before. I mean, the nuclear industry has obviously gone through lots of periods of where everybody thinks it's going to be great and then it takes a long time and everything's really expensive. What would you say for Applied Atomics right now? Like, what are the key things that you're trying to do differently so that it does happen fast?
Paul Keutelian [00:03:24]:
Yeah, I mean, like you're saying right now the iron's hot. And the way we think about it is there's the way to do it. The most quickly is to start from your supply chain, to start from what exists today and work backwards. And start from your customers and work backwards. So the way I approached the team with this was we went out and we started talking to vendors from our past and some new folks to us, new to us that have worked in this space before and gone around and asked, what, what do you make the most of? And what do you make today? And then given all those parts, coming back to the team and saying, what is the plant that we can build with this? And what we're hunting for is the Venn diagram between what we can build and what the market is willing to bear in terms of cost and time. And so when we started Applied Atomics, like Ben and I going through this exercise, where is there an overlap at all? And seeing one, that's the opportunity. And that's kind of how we've approached all of these, all the design points we've gotten to right now.
Matt Gjertsen [00:04:38]:
Oh, got it. So is it, if I'm hearing you correctly, tell me if this is right. The analogy that comes to my mind is how the last decade in the space world, the big shift was what if we use consumer electronics rather than specialty electronics? Is it kind of that kind of thing? But going through the whole supply chain and finding what's the nuclear equivalent of.
Paul Keutelian [00:04:59]:
That, that's a big part of it. The other part is focusing on. The other part is focusing on limiting choices to what'll get us to the finish line in time. Sure. Right. So if we're. If our goal is to get to 2030, we can't make choices by design.
Matt Gjertsen [00:05:27]:
Got it.
Paul Keutelian [00:05:30]:
That will take longer than that. So that, that pushes you into some pretty interesting spaces that I think engineers by default don't tend to go. We're geared by default to say we're going to be cost optimal and that we do that through thermodynamic optimization or neutronic optimization. And when you take this approach you kind of shift off of those points.
Matt Gjertsen [00:05:52]:
Got it. So it's more the time optimization. Yeah. Interesting. Awesome. Well, I want to get into some of the non engineering side of things. Right. Like that's kind of the point of this discussion.
Matt Gjertsen [00:06:05]:
Before we get to the explicit people leadership side of things, I wanted to start with kind of how I started the introduction, this idea of the responsible engineer. Because for those who aren't aware like, and this is kind of me also kind of understanding this as a non engineer. But from what I've read and picked up, the concept of a responsible engineer is something that's really changed, especially like the hard tech startup world in the sense that if you go to many legacy companies, there's just a lot more distributed ownership of things. And one of the things that SpaceX and companies like it have done is introduce this role where no like you are responsible for this entire system from the design to the implementation, the whole thing. And that that has allowed for much more ownership, much faster movement, much deeper understanding of the systems. And so let's, let's first let me pause there. Is that a right understanding of kind of what the responsibility, responsible engineer role is like? Could you, what is it? How is it different from what's happened before?
Paul Keutelian [00:07:13]:
Yeah, I think that's a great description of what the responsible engineer is. And then I think on top of it, you know, having the benefit of being part of launch or launch and test or folks that actually work on the ground support equipment is you really, you really start to feel it kind of in your body that like there's a way of life to the responsible engineer at work. And for us it was kind of on overdrive because we were usually in the machines we designed. So it became a very personal, a personally driven desire to be responsible because, you know, there's a lot of opportunity for impact to our personal lives if we're not responsible. But I think that it fosters a lot of really good ways of looking and thinking and appreciating the importance of responsibility, not only with respect to authority, but also with responsibility to safety and execution because you're letting your teammates down if you don't get it done or if it's not safe. And both of these things are important.
Matt Gjertsen [00:08:23]:
Yeah. The reason why I wanted to start with the idea of the responsible engineer is because I think in a lot of the corporate world we're hearing a lot of this idea of leading without authority. More and more companies are Becoming flatter and flattering. They're more interconnected than ever. And as, as, as a result, you can't just tell people to do things very often because they don't work for you. You're working with them. And I think the responsibility. That role probably has a lot of that.
Matt Gjertsen [00:08:51]:
So I'd love to kind of start to unpack, like, from your perspective in that role or in those kinds of roles. How. Yeah, what, how. What kind of people skills are really essential to being effective in those roles? And how did you see it?
Paul Keutelian [00:09:06]:
Yeah, that's a really interesting question, because I think the, the role of the responsible engineer in a flat structure kind of turns the whole paradigm on its head of you have this hierarchy, your boss is telling you what. What to do, it's your boss's call, and you're just doing the work. But now, because everybody's on a more even playing field, but people have the authority for their specific thing. They have ownership. You're. You're almost managing the equipment more than you are managing people. What that does is the way I think of it is you turn. You turn into almost a.
Paul Keutelian [00:09:54]:
A contractor within your own organization.
Matt Gjertsen [00:09:56]:
Interesting.
Paul Keutelian [00:09:58]:
When you, when you take that approach, everybody becomes your customer, right. Your leader, your peers, the consumers of your product, even if it's internal to the company. And then externally, the actual client that's buying your company's product, your regulator, all that stuff. Everybody is your customer. And when you take that mindset, it really starts to become a more collaborative effort because ultimately, having also been a consultant, what is our first thought? What is my customer's pain and how do I make it go away? Yeah. So now, now it's not like, well, you have to get this done because we have to meet quarterlies and all this other stuff. It's like you're. You're both working together because you're both consultants.
Paul Keutelian [00:10:44]:
You're both, both having to. You have the same customer at some point and you're both trying to solve their issue.
Matt Gjertsen [00:10:51]:
Yeah. So it's. I like that idea of it being. Because you can treat that. To put that in the world of a manager as well. I think the best manager is the whole idea of servant leadership is this idea of. In many ways, as you said, you know, you're. You're treating your team really as your customers.
Matt Gjertsen [00:11:06]:
You're a supplier to them. You're a supplier of resources, you're a supplier of authority, you're a supplier of direction. And so it's all about understanding their pain. I gotta believe, though, that there are still times where if. If everybody is kind of their own consultant within the organization where there's. You're competing for resources. You think this is the best way to solve a pain. They think this is the best way to solve the pain.
Matt Gjertsen [00:11:34]:
How. How did. For you. How did you go about navigating those. Those disagreements?
Paul Keutelian [00:11:39]:
Sure. Well, when those types of conflicts come up and they are frequent in this type of setup, I see it as an opportunity to refine an interface requirement, let me say, because I'd like to believe that if there are people on your team that are seeing different possible solutions, both of them could be equally right, then the problem isn't properly constrained. Right. And that's. That then becomes the role of the next higher person to add those constraints or to investigate and research it. Because ultimately in. In the perfect world, there's a solution that maybe, you know, one person just would have done it a different way, but they don't disagree with the other person's solution. And that stems into an even deeper conversation.
Paul Keutelian [00:12:34]:
I think that, you know, in this. In this age is an important one, is once you get to a certain level of product development or caliber of person you work with, I think stuff stops being right and wrong. It starts being. It starts being, am I the right solution for you? Are my teammates the right teammates for me? Are my customers the right customers for me, and am I the right vendor for them? And that kind of takes the ego and the person out of it, and you start working with people who are right for you. Right. Is. Is there a perfect bridge in the world? No. The San Francisco Bay Bridge was the right bridge for San Francisco.
Matt Gjertsen [00:13:22]:
Yeah, I love that. I think it really goes into this, you know, speaking from the talent development world and the HR side of things, I think very often we can maybe we get overzealous about trying to say, like, we can solve problems when maybe we're not the right solution to a problem. And I think a lot of it comes from this fear that we're. We're already often kind of on the side of the organization and we're, you know, we're a support function. And so we're worried that if we're not solving every problem that we just, you know, become irrelevant. And. And so we. Sometimes that leads us to say, like, oh, we can do it when we actually should be saying we won't.
Matt Gjertsen [00:14:03]:
We shouldn't do it because it's. Because it's not the right problem. But what you're saying really is this idea of imagining the world as an inf. There's infinite problems out there, and so we might as well find the right problems. How did you, you mentioned, once you get to a certain point in your career, how did you get to that point where you were able to, like, remove that ego from it and really look at it? Is, is this the right solution?
Paul Keutelian [00:14:34]:
Sure. The funny answer was, is I've been wrong a lot.
Matt Gjertsen [00:14:41]:
And haven't we all?
Paul Keutelian [00:14:42]:
And haven't we all? And I've been wrong in a lot of fantastic ways. And I think the, the positive thing about SpaceX that I took away from that experience was SpaceX allowed us to be wrong without it being fatal and both fatal to me personally and fatal to my career.
Matt Gjertsen [00:15:11]:
Yeah.
Paul Keutelian [00:15:11]:
And there was a good leadership structure, there's a good culture there that people understood the risks that they were taking. And it comes back to responsible ownership. Even at our leadership level, where they knew and they were empowered to take a chance with us. We were responsible for convincing them for providing that information, and they were responsible for taking the shot with us. And if we were wrong, we had to stand up for ourselves. We had to own that mistake. But they also acknowledged that risk and it wasn't a surprise to them. And once, you know, once you're in that type of system for a few years and you're able to solve a bunch of really extreme problems, some of which may have no solution, you can, you can really take that lens forward with you and, and take it out into the world.
Paul Keutelian [00:16:11]:
And that's one of the things I wanted to do. That's, that's what drove me into entrepreneurship, is taking some of these good pieces and expanding on them and creating more spaces like this for people to also learn that being wrong is okay as long as the whole team is on board. We've talked about it, you know, let's go do it. And then, and then this idea stemmed from that.
Matt Gjertsen [00:16:33]:
I'm really interested in what you were talking about. And this could be, you can speak from the experiences that you saw at SpaceX or kind of how you're taking that into, since SpaceX, of how do you create that kind of environment? Because I really like how you hit that on the head of. Even when the person on your team does something wrong in a perfect world, you're doing it in partnership. You empowered them to do certain things. So their mistake is your mistake too. And often that's, that's not a relationship that I think is, is seen a lot in, in workplaces where it is, it is very separate. And so Your mistake is your mistake, and I'm going to punish you for your mistake.
Paul Keutelian [00:17:14]:
Sure.
Matt Gjertsen [00:17:15]:
How, how have you seen it where one. That relationship gets built or that kind of environment gets built, but then also mistakes aren't fatal, but enough mistakes probably are. Like, like, what's, what's the other side? Like, where's the limit to this?
Paul Keutelian [00:17:30]:
This. Sure. Well, that's, that's the job of leaders, right. Is to manage how many, how many bullets you have in the gun and the amount of constraints you're going to put on the program and on your team and how many of these shots you can take. I think something that's important for leaders to do, and I'm certainly trying to do myself, is to have my team in on it, let them know this is what we have before it's over. Like, in my perfect world, if I had a big factory, I would have a countdown clock on the wall, but instead of the time, it would be the amount of uncommitted dollars the company has left.
Matt Gjertsen [00:18:16]:
Yeah.
Paul Keutelian [00:18:17]:
And so that way everybody has the context to be responsible. Because I know having been, you know, from the start of my career, sometimes the decisions and the constraints that came in didn't make sense to me because I didn't have context. And maybe the leaders couldn't tell me, maybe they didn't even know, but had I known what it was. And later on, as I became a senior engineer, when I started working on other programs and I started seeing even just a little bit more context, I understood, oh, okay, this is why you couldn't have given me this shot. It felt good to me, but the risk was just too high. And in context, I would have understood a little bit better and been more empathetic to this instead of being frustrated.
Matt Gjertsen [00:19:02]:
Yeah, yeah, I, I love that you said that. I was actually just recently listening to interview with the CEO of. I think it was the CEO of Castilian. The, the rocket engine. Rocket engine company. And he was saying the exact same thing about how he tries to be as transparent as possible with the team about their burn rate, about the amount of money that they have. And I think the, the underlying thing that I, that I'm getting from what you're saying is it's funny. So later on this year, I have a book coming out called Minimum Viable Manager.
Matt Gjertsen [00:19:37]:
And I am already, like, thinking about what's the opposite side of this book that would be called, like, Maximum Viable Leader. Like, what's like the, the extreme end of how do you go for the biggest bets and the biggest things? But not getting out of control. And one of the ideas that I've been thinking there is having setting this big, bold vision that's grounded in reality, like, you have to be able to trace a really clear line to it. And so. And the way this relates to what I'm hearing you say right now is often when we think about how many chances we're going to give somebody, how many mistakes they're going to make, it's just like, oh, I just. I don't know. I'm the. I'm the.
Matt Gjertsen [00:20:17]:
I, as the manager, I'm just. I'm just tired of working with them. I'm just frustrated. I just think they're not the right fit or whatever. But kind of what I'm picking up for you is almost like you as the leader, know where you are trying to get and the amount of resources, whether that's money or time that you have. In a perfect world, I have infinite money and time, and I can give you infinite chances to get better. And we can just learn and learn and learn, and you can get better along the way. But that's not real.
Matt Gjertsen [00:20:46]:
There is some end point, whether it's time, money, whatever. And you as the leader knowing that or like, looking at your team and kind of figuring out, like, are we on a glide path to get there or not? And you're making mistakes at a rate which we can't absorb, like, we're no longer. And so it's just a much more grounded way of thinking about, is it, can I keep working with this person or do I need to try a different. A different direction?
Paul Keutelian [00:21:14]:
Yeah, I completely agree. And I think that also, I'd like to believe that that conversation is easier to have with the team. And having been on the other side of that, like, I would like to believe that. I would take that conversation with Grace, where it's like, it's. It's not an interpersonal issue. It's exactly what you said. How many. How many shots can we absorb? Did I do my best as a leader? My responsibility was to make sure that you had all the tools you had to succeed.
Paul Keutelian [00:21:50]:
And for me to understand what it was that you were trying to do and make sure it fits in the company. And then, yeah, coming back and saying, hey, this, you know, being transparent, so it's not sudden, too, and saying, look, you've. You've had a lot of shots at. At base, you're out. But instead saying like, okay, this is the chance you're taking. This is the risk to you, and it's not personal. It's, you know, this is a big shot. How much are you willing to bet on it? And, you know, in the past, in, in my past experience, more for physical safety perspective.
Paul Keutelian [00:22:28]:
Boy, have I seen the quality of work shoot up when it's your own safety on the line.
Matt Gjertsen [00:22:33]:
Sure.
Paul Keutelian [00:22:33]:
Both in myself and, and in folks that I've trained and in my peers. And this is a good thing, right. If it's different, if you're designing a machine for somebody else to operate, it's way different. When you're designing a machine for you to operate.
Matt Gjertsen [00:22:47]:
Yeah.
Paul Keutelian [00:22:48]:
Why shouldn't, why shouldn't work be the same?
Matt Gjertsen [00:22:51]:
Yeah. I mean, I remember explicitly when that, that speech was made at SpaceX and in the lead up to the crew Dragon launch, and it was just kind of, if you're not, if you weren't comfortable putting your family on this craft, then we shouldn't be launching this craft. Like, we need to, like, really, really think it through.
Paul Keutelian [00:23:10]:
Yeah.
Matt Gjertsen [00:23:10]:
What. So now that you're on the, you mentioned kind of the, you know, the clock on the, on the board, whether it's time, whether it's money, now that you're out on your own and you've been in a couple companies now, what are some other things you think about? Trying to create an environment where there is that ownership, where there is that transparency?
Paul Keutelian [00:23:30]:
Yeah, I think a lot about interface controls and interface management. And what I mean by that is, you know, if you're going to have a responsible engineer or if you're going to have responsible folks, you need to know where your sandbox is. So I'll use a direct example. I, as the cto, am responsible for the product development of the company. I report to the board and I am a surrogate for our customer within the company. And my job beneath me are four regulatory, engineering, deployment and controls. And so my job is to develop a product that sets the rules of engagement between these four disciplines and some consistency around reliability and redundancy, you know, the process by which design will happen and some constraints, some performance constraints, and then after that, you know, it's up to the team to provide solutions that fit in this framework. Because the purpose of me setting those boundaries is to create a common communication layer between these disciplines.
Paul Keutelian [00:24:57]:
And then that's it. And then I have to, I kind of have to let go the ownership of it. I can, of course, dip in and say, hey, I don't know, or this is my thoughts on this based on my experience as an engineer here. But I really do leave the ultimate authority of that decision making to that team member. Even as the CTO. Now, it eventually comes back up to me and I have to make the call on it. Right. But those same rules of justification that I've asked the team in, when they talk to each other, they talk to me.
Paul Keutelian [00:25:29]:
I also enforce on myself. I have to convince my team that even if they might not think this is the perfect way to do it, they have to at least, it has to at least make sense to them.
Matt Gjertsen [00:25:40]:
Yeah.
Paul Keutelian [00:25:41]:
So, you know, culture comes from the top. I'm a firm believer in that. And so I get what my team gets. Yeah, that's it.
Matt Gjertsen [00:25:49]:
Well, and this idea of having a common language and kind of knowing where the boundaries of the sandbox are is really essential. It reminds me of, um, there's a, a framework called eos, the Entrepreneur Operating System that I, that I really like. It comes from a book called Traction. And one of the things that they have in that book is this concept of an accountability chart, as opposed to an org chart. Because very often, especially in startups, as they grow like an organization, an org chart kind of tends to grow very much based on personality. It's who's there at the time, it's who's will, who has some spare capacity to bring on some people. And it's why really easy, especially early in a company's growth, it can just lead to this hodgepodge where you're not really sure who's responsible for what or where or why they're responsible for it. And so the idea of an accountability chart is pretend there's nobody in the organization, nobody exists.
Matt Gjertsen [00:26:49]:
What are the big picture things? The big picture responsibilities that people need to be held accountable for. And you break those. And so you're going to wind up with like seven or eight things at the top. And then there's some sub things to those and some things to those. And then you look around at the people in your organization, you say, okay, who's best to be responsible for, accountable for each one of those things? And it's just a really grounded way of thinking through like where are those, those interfaces so that everybody understands them. Because I think in a lot of organizations people don't.
Paul Keutelian [00:27:21]:
I mean, I completely agree and I think we may have accidentally stumbled into that type of situation. Because a concept that I've been interested in, and I know some companies do, I know some larger companies have done this, is they separate engineering leadership from people leadership. They're different people. And I think that's extremely fair. That's very Interesting to me because I think some people are better leaders. I think some people. I shouldn't. I think some people are better led by certain people than other people and that it's better to decouple that from forcing both your top engineers, your top technical talent from being your top leaders.
Paul Keutelian [00:28:04]:
I know some exceptional engineers that have no interest in leadership and I know some exceptional technical leaders that are like individual, like tinkering and engineering just isn't their thing and like, let's leverage that. I think it's, it's not tenable to compel top technical and top leadership to have the capabilities of the other side.
Matt Gjertsen [00:28:36]:
Yeah, the, the split promotion track, dual promotion track, I think is just like an essential element of any technical organizations these days where you need to have a career path to advance as a pure technical contributor that does not involve people leadership. Like, it's just, it's just an essential thing.
Paul Keutelian [00:28:55]:
Yeah, we've already started those conversations too. Like that's, that's where we started with is how do we make this system work?
Matt Gjertsen [00:29:03]:
Yeah, yeah.
Paul Keutelian [00:29:06]:
Same with product ownership.
Matt Gjertsen [00:29:08]:
Yeah, yeah. Any other as, especially as you've, you know, been out in your, in, you know, building a couple different companies now. Any other big things that have appeared, like biggest challenges that have occurred to you or you've come across because you know, you're, you, you become more responsible for the people side of things? Yeah. Any big challenges that have, that have stood out for you and how have you gotten past those?
Paul Keutelian [00:29:36]:
Yeah, I think some of the biggest challenges have been. Convincing people that discipline is speed and that when you have startups don't need to be a frenzied mess. You know, there's a, there's. I almost kind of wanted to call it like a game that's being played where there is some benefit to having a sandbox where people are just able to go build and create and envision and dream and all that. And then there's a point where you get into, you've got to get into production as fast as possible. And at that point that takes a lot of discipline. And I have seen and experienced situations where having discipline from the get go gives you the freedom to explore, to experiment, to have that creativity. And I think that a lot of folks feel like that's impossible.
Paul Keutelian [00:30:48]:
You know, like, I think publicly the public perception is you need to have just this frenetic activity to make stuff happen. And so I think there's not a lot of appeal to try this path because there's a lot of upfront work that you have to do as leaders. That's not exciting. But I, I want to take people and say, I promise it's smoother on the other side. And yeah, it's funny.
Matt Gjertsen [00:31:14]:
I don't know if you know this. There's a, there's an ex Navy seal, Jocko Willink, who actually has a book called Discipline Equals Freedom. And so it's exactly this idea. What is? When you mention there like, you have to make some tough choices early on. What do you mean? Like, what are some examples of that?
Paul Keutelian [00:31:32]:
Sure. I mean you have to focus on, you have to focus on like your communications interface for the company. What does that look like? What is that? Mechanically, that's your quality program and that's your hiring team. I'm a firm believer that hiring is the number one most important function that a company has. That's it. Because I'm trying to make the 1990s championship bulls. Right. And all those players are phenomenal and they were phenomenal separate, but together they, it's a force multiplier.
Paul Keutelian [00:32:14]:
And that brings me back to, you know, that brings me back to the concept of for what we're trying to do, for the leaders that we are, for the experience that we have, there are people who are right for us and that we are right for. And that's the team we're trying to build. And it's not a judgment on, you know, we only have the top 2% of engineers or we have the best this or the ultimate that. It's as a unit. However we are, we're, we're right for somebody. And hopefully that's a lot of people and enough to make a good business.
Matt Gjertsen [00:32:49]:
But you know, in order. And that's where the challenge is. Because in order to do that correctly, in order to hire well, it is. Okay, let's like really define this job wreck. Let's really know who we are, what skills we do have, what skills we don't have. It's like it's taking that upfront time to really closely define that. So then the recruiters can go wild within those constraints and they can, they, they have the freedom to find somebody who is the non intuitive pick who didn't come from the college, who didn't have this background, but given these constraints is truly the right person for you. That's where it all comes from.
Paul Keutelian [00:33:31]:
Yeah. And it's months. And sure, I'm an engineer, I'm the cto. Nothing would make me happier than to be coding away and doing simulations and building stuff. But it's not right for my team, and I am a steward to them, and I'm a steward of their time. And we're trying to paint the ceiling of the Sistine Chapel, and all of us are Michelangelo's, and I got to make sure only Michelangelo's come in. And that's, you know.
Matt Gjertsen [00:33:58]:
Yeah. How do you define that? And, yeah, and. And just. I mean it, really. And everything you just said right there, I think really brings the conversation full circle. Is. Is it's you seeing your team as your customer. It's what do I need to provide them to make sure they have the resources that we're bringing in the right people to support.
Matt Gjertsen [00:34:15]:
Support them. But it's really viewing yourself as a leader, as the people who you're leading, as your customers. I like that. I like that. Awesome. Well, this has been a fantastic discussion, Paul. I think, you know, we could go for a lot longer. I'm really excited to hear what you're doing.
Matt Gjertsen [00:34:32]:
You know, the nuclear space is. Is. Is such a hot space right now, so best of luck to you and the team. We'll definitely have to keep in touch.
Paul Keutelian [00:34:41]:
Yeah, absolutely. And thank you kindly. And, yeah, we're excited for some announcements, hopefully coming out soon and to bring people along on our progress to 2030.
Matt Gjertsen [00:34:53]:
Awesome. I look forward to it.
Matt Gjertsen [00:34:55]:
Thank you so much for listening in on the conversation. I hope you got as much out of it as I did. If you are a manager yourself and you're looking for more insight on how to better lead your team, team, please make sure to check out some of our other amazing episodes. If you are responsible for developing leaders in your organization and you're struggling to make programs that actually change behavior and actually impact the business, please reach out so we can figure out how to make your organization better. Every day. Drop me a line using mat better everyday studios dot com. I look forward to the conversation.

