Episode Description
Hello and welcome to Leadership Launchpad! I’m your host, Matt Gjertsen, and in this episode, we explore the intricacies of high cadence engineering and leadership with our guest, Chris Kaufield. Chris, VP of SaaS Growth at Stokespace, shares how distributed ownership in engineering leads to collaborative success. We delve into Stokespace’s mission to achieve rapid, reusable rocket flights, drawing parallels between hardware and software development. Chris highlights optimizing products by focusing on immutable laws and customer-centric approaches while emphasizing data-driven decision-making and traceability. Tune in to uncover how leadership and cultural shifts forge groundbreaking technologies and drive organizational growth. Whether you're an engineering enthusiast or a leader aiming for excellence, this episode is packed with invaluable insights. Don’t miss out! 🌟🚀
Want more tips on effective training? Sign-up for our weekly newsletter: https://www.bettereverydaystudios.com/newsletter
Visit us at https://www.bettereverydaystudios.com
Want practice developing your skills as a leader? Check out our Leadership Skill Accelerator sessions at www.bettereverydaystudios.com/accelerator.
Chris Kaufield [00:00:00]:
The idea of bringing to life and things quickly, there's some traits that I've seen and observed, and we certainly follow here at Stoke. You know, one of them is certainly the idea of distributed ownership. If there's any impression that engineering is still a sort of cascaded chief engineer to staff, to, you know, technician and on down, that's not the way it works anymore. There's ownership. And so for every element that we show, and this is true at most significant hardware programs, you have responsible engineers and people who own aspects of the product who need to come together because their dependencies are just driving them forward. So that's one of many traits. But distributed ownership certainly is where it starts, and that's one of the kind of core leadership principles to give people a sense of just shared commitment and make sure that's really happening.
Matt Gjertsen [00:00:51]:
Hello, and welcome to The Leadership Launchpad, where we help technical managers improve themselves, their teams, and their organizations. On this show, I talk with industry leaders, coaches, authors, and experts to give you actionable insights to help improve your own performance and the performance of those around you. Our guest today is Chris Cofield. Chris builds operating solutions for teams that thrive on speed to market. At rocket company Stokespace, he leads the growth of its commercial software fusion, which is equipping aerospace, climate and defense businesses with methods for breakthrough hardware development. Chris specializes in organizational culture shifts, previously owning sales and marketing of new teams platforms at Microsoft, as well as manufacturing, industrial and logistics experts. I can't tell you how excited I was for this conversation. I will admit the beginning of this episode geek's a little bit out on space.
Matt Gjertsen [00:01:54]:
And so if you're not as much of a nerd about that stuff as I am, I highly recommend that you stick around because we get into a lot of leadership and culture topics in this episode. Expect to learn what it means to have a high cadence organization, the tension and trade offs of building an organization that is focused on product first, and how distributed ownership and operational accountability can build better leaders. Before we get into the discussion, I do want to ask you very quickly that if you are not subscribed, please make sure you subscribe to the show so you never miss a future episode. And if you are already subscribed, then I would ask you to share this show with at least one other person. Because after all of that is how we grow. I can't tell you how much it means to me. So with that, let's get into the discussion with Chris Caulfield. Chris, welcome to The Leadership Launchpad.
Matt Gjertsen [00:02:50]:
How are you doing today?
Chris Kaufield [00:02:52]:
I'm great. Thanks for having me.
Matt Gjertsen [00:02:54]:
Yeah. I can't tell you how excited I am for this conversation because me, as a space nerd, I've been following stokespace pretty closely, I think probably ever since the everyday astronaut tour several months ago. That was. That was pretty big. I think a lot of people saw that. But a lot of my listeners aren't up to speed necessarily on the space industry. So I would love to hear from you what is, what kind of, what's at a high level, the ambitious goals of stokespace.
Chris Kaufield [00:03:27]:
Yeah, we're a rocket company in Washington state, about 150 people, and what we're building is a new kind of rocket to carry commercial and government payloads. The new kind of rocket is pretty exciting because it's meant to drive daily flights. We think the space industry is moving in this direction, and it's sort of the inevitable outcome of all the work people are doing on reusability and bringing things back to earth and not tossing them in the ocean, but flying them again. In our case, the breakthrough is reusing the stage two, which really hasn't been demonstrated before. We recently showed the first flight of a demonstrator vehicle not that long ago and how that's going to work. But ultimately, we think that by flying daily and a rapid turnaround clip with a rocket that's meant to go up and come back down in all of its pieces, you end up with just as fast pace and low cost, something like an airline model. So that's really the mission and the focus on Stokes bases, from Stokes base's leadership team, which put together the company about four years ago. These are folks that are Andy and Tom, ex Blue Origin brought in experts from all over, including your former employer, who's got just a ton of talent to share with the world.
Chris Kaufield [00:04:38]:
And since then, we've grown to build everything in house and as much as we can and really develop the system so that it can be really a breakthrough in how the industry receives services from space providers along the way, we've built this rocket, but there's sort of this, you know, this relationship between building breakthrough things and having to build the systems and methodologies and cultures to build the thing. And so that's a pretty exciting part of my role, which is to help take the methodology that we use to develop this rocket system and bring it to others.
Matt Gjertsen [00:05:09]:
Yeah. And that, I think, is one of the unique things about the company. I mean, not only, I mean, jeez, 150 people, you all are doing a lot. Just the pace at which you all are operating is really really impressive. And you yourself are the VP of SaaS growth, the vp of software growth, and that's different. So you say you're a rocket company, but you're a rocket company that's selling a SaaS product. How did that happen?
Chris Kaufield [00:05:40]:
Yeah, I think for most companies that build new hardware, there's an understanding that the tough bit isn't so much the design. I mean, if you and I decided that we're going to build a new rocket, we could at least design it on a napkin today. We'd probably get that far and say, this is the shape and this is the general requirements. And then in the world of making things, there's a lot of production capacity out there. Companies that do nothing but do fabs and contract manufacturing, or in house at an automaker. But the problem with most breakthrough hardware, and I'm talking about anything from aerospace products to submersibles, to climate tech, to energy plants, is this development period. And the development period is really when the abstract design meets the physical world, where you're getting into actual hands on parts and components that might break, that might succeed, but you need to know why either way. And you need to be able to move those forward into the next milestone.
Chris Kaufield [00:06:35]:
And so this whole space of development is really, in a sense, it's kind of the business model of stoke. If we can't bring together this concept of a fleet of vehicles that can fly quickly, if we can't bring that to life quickly, we as a company are going to have some stress about how much that cost. And are our customers just waiting indefinitely? Well, no, we really want to bring this to life as soon as possible, because the industry needs it. And so this development process, what we've realized is that there is a way to approach development, development using some new methods, or at least refined methods that we're calling high cadence engineering. And that idea and the principles behind it of how you bring to life something that's complex and new and maybe even just unprecedented, that's something that we thought we could bottle up. In fact, we kind of had to, because as we grow, our team needs to follow some of these principles and practices. So rather than what is really quite typical in the world of new hardware, building on spreadsheets and sort of organizational tools and project management tools, and note taking apps, which really happens in the world, we wanted to codify a lot of the sort of behaviors and methods into something that we call fusion. And that's now become a successful commercial offering.
Chris Kaufield [00:07:50]:
It's available to companies that are building their own breakthrough hardware. But it really became, I think, this flywheel between hardware and software that once we unlock that, we can make sure that that pace that we want is kept as quick as possible. Fortunately, I'm really just thrilled to say that the company has hit these major milestones, including first engine fires and first flights using these methodologies. And it's a really interesting relationship between hardware, software, people and methods. But that's what it takes to really build the exciting stuff that we all are just following online and social.
Matt Gjertsen [00:08:24]:
Yeah, exactly. And it's really interesting because, I mean, it's great proof that the pudding is good, really, in that if you're having this tremendous success and you're doing it with this software and this approach, then when you approach others, it's probably pretty easy, like, oh, okay, let's do this. And I love how you spoke to that point of kind of needing to build the ecosystem. I remember when I was at SpaceX and always in the back of my mind, I always kind of had this fear of thinking like starship is going to get built and then there's going to be nothing to put in it, because nobody like believes that something like that is going to exist. Briefly mentioned earlier that you're almost like, it's not so much a software, it's a culture, it's a way of doing things. What high cadence engineering is, it's a way to operate, it's a culture for a company to have. What, I would love to know some of the elements of that culture. What's different about this high pace of operations?
Chris Kaufield [00:09:27]:
Yeah, when we think of high Keynes engineering, you think of a sort of attention between hitting your commercial milestones or those milestones are going to drive your company forward as fast as possible, while simultaneously setting yourself up to reduce the burden for the next set of milestones. So that tension is kind of interesting. For example, on our, in our world, we knew that we had to get usability out of a rocket in order to really serve our customers the way we wanted to. We knew that's where the business model was, is full reusability. But it sure is much easier to hit a milestone that says just launch something, because you can launch an expendable rocket or another design much more quickly than you could to put together a reusable time in the first place. However, if you do that, you actually did not minimize the burden for the next set of milestones. You made yourself more difficult because now you have to unwind first, go at it, and start over to pick up where you really want to be. And so you kind of can end up in some deception and sort of faints and frustrations if you don't sort of build those things together.
Chris Kaufield [00:10:32]:
This sort of path to milestones that'll move your company forward. And when I say that, I mean you're building your product, but you're also building your company as you go, because the product is effectively new. So that's the, that's kind of the essential tension. There's a few key things that. That really seem to recur again and again when you think this way. And I think you can tell me in your own experience and maybe others have a point of view about this, but it doesn't necessarily apply to just hardware. The idea of bringing to life and things quickly. There's some traits that I've seen and observed, and we certainly follow here at StOQ.
Chris Kaufield [00:11:09]:
One of them is certainly the idea of distributed ownership. If there's any impression that engineering is still a cascaded chief engineer to staff, to technicians and on down, that's not the way it works anymore. There's ownership. And so for every element that we show, and this is true at most significant hardware programs, you have responsible engineers and people who own aspects of the product who need to come together because their dependencies are just driving them forward. So that's one of many traits. But distribute ownership certainly is where it starts. And that's one of the kind of core leadership principles to get people a sense of just shared commitment and make sure that's really happening.
Matt Gjertsen [00:11:52]:
Yeah, I think you're 100% right in that this isn't a thing that's unique to the hardware world, but it really comes to light in the hardware world because there can be so much more investment than in other things in each step forward. So if it's software or if it's building a consulting business or just building an idea, sometimes it can be easy. It's a lot easier for you to run down a road and then change the road. Whereas in your world, in any hardware world, you're investing a lot in the infrastructure, in the tools to make the thing, and sometimes the tools to make the tools to make the thing.
Chris Kaufield [00:12:30]:
Yeah, that's right. There's a paradox. You're going to invent something new. Well, congratulations. You're going to invent the tools to build the new thing. So everybody assumes that. But what if you could do something a little differently? And that's been our experience, is that you can start to embed these practices into software and into behaviors as well, you actually brought up an interesting point, because the iterations you make as you make that progress, one of the other elements of hiking's engineering, or let's just call it hiking's output, is the idea of continuous traceability. You really need to know what each step produced in order for the next step to depend on it or be successful, or to change course.
Chris Kaufield [00:13:10]:
Here again, if you tested a new engine design, or even a new accounting system, or maybe a partner relationship model, if you don't know if it worked or not, or even worse, even if it did work or not, the reasons behind it, you're sort of doomed to repeat the problem one way or another. Hardware is just more tangible in that way where if I have a bolt that broke while that physical thing broke, let's find out what happened. Whereas if it's in more of a squishy, you know, corporate culture, maybe you just don't know how to even diagnose that problem. But tracing what you've done is one of the things that software can help with. It's great at it. It's great at recording things. Now you got to figure out how to record the right things and not the wrong things, I suppose, but you really need to know what happened in order to be able to move forward. And there's industries like government, customer industries especially, where if you don't prove along the way what happened and how you did the thing, you may not even have a business after all.
Matt Gjertsen [00:14:11]:
Yeah, no, absolutely. You've mentioned a couple terms here that I want to make sure to pause and kind of parse out, you know, you know, bring us into this leadership realm that kind of, we talk about, and this idea of organizational culture. The first thing you mentioned was distributed ownership. That, for me, I will admit, I think when I left the military and went into more of the space kind of tech world, that was one of the things that I struggled the most with making a transition in, because I was used to a world where there was always a owner. If I want to make a change, I go out and find which leader is responsible for that part of the organization, I convince them, and then I'm done. Like, then the decision just kind of cascades down. And a lot of companies now, just no matter if they have a higher, you know, whatever the hierarchy looks like, it in practice is much different because a lot of that ownership is at much lower levels, and getting the okay from the boss really is just an okay to go convince everybody of your idea. And that.
Matt Gjertsen [00:15:16]:
And that's kind of it. How does, what does distributed ownership look like at Stoke? How does, how does that manifest itself?
Chris Kaufield [00:15:23]:
Yeah, I mean, it's. Fortunately, it's a very straightforward understanding, even if you're not from the world of rocket engineering or hardware in general. If you see something on a rocket that looks like a physical thing, there's probably a person that owns that physical thing. And of course, that sort of makes sense. If you own the propulsion system, or you own a structure, or you own a navigation or avionics computer, it's sort of, it's very tangible and tactile. So that's one thing that really, I think hardware gets an advantage. Overdose. More abstract ideas of classic corporate management, maybe.
Chris Kaufield [00:16:00]:
And I've lived in that world as well. I had 13 years at Microsoft, for example. And so we're dealing with software and go to market motions, and all the things that make commercial success there are just a little different compared to a rocket that either flies or it doesn't. So it's very binary. So as a result, I think products like rockets tend to draw people into very specific areas, because without those owners, the void would be obvious to all if we didn't have a thruster engineer that's owning the thrusters. Everybody who's waiting for that connection to essentially hook up to the rest of the structure and bring the whole machine to life. The dependency is ultra clear. So that kind of ownership, if you can find ways of creating ownership that blanket the end product, whatever that is, the product or service, you have a good chance, especially if you build dependencies among people, of people right sizing and finding the right trade offs to make that system work.
Chris Kaufield [00:16:57]:
But I think you alluded to this. Even in classic aerospace cultures, there is a lot of departmental and budgetary behavior which drives ownership, rather than product ownership, that can really bring down an agile, nimble program like a new rocket, like we're building, because you don't know how to size departments when you're building a product like this, you don't know what the right budget should be now versus the future. You don't know whether the corporate design you built is even going to support the product when it goes. And so we take much more of a product oriented focus on building our output and shape the organization to the product, versus attempting, which is so classic, of creating this reusable enterprise, and then hope that products can just flow across the top of it.
Matt Gjertsen [00:17:44]:
Yeah, yeah. The last time we talked to, you said it so succinctly. You said, build an organization based on the product, instead of building the product based on the organization. And it actually reminded me of something that Jason Fried from 37 signals once said, where he talks about how one of, and this is a few years ago, before funding crashed in startups, but he was saying how one of the reasons why so many startups, even software startups, needed to go get millions of dollars of capital to start is because they were all trying to start as if they were Facebook or Apple. And so, like table stakes was a 50 team, you know, software engineer, 50 person software engineering team. And, you know, all the, all this, you know, almost bloat, because to your point, you don't know what you're going to do. How do you make those decisions? Because, and this goes back to that tension that you were mentioning at the beginning of, there is a little bit of, you know, you don't want to over, you need to build a product, but then you need to build the organization to support it. And there's kind of that back and forth.
Matt Gjertsen [00:18:49]:
How do you make those decisions in terms of when to grow the organization or not?
Chris Kaufield [00:18:56]:
I think a lot of the growth that we encourage is a result of kind of natural conditions pushing you to the next milestone because you've created a certain level of accountability. And what I mean by that is we are heavily vertically integrated, for one. And so building in house and relying on the work that responsible engineers or owners make and seeing it all the way through is a really quick way of sussing out where you've got weaknesses and lack capacity. So that's one way to bring forward the know the areas of investment that you need to make. I mean, so, for example, you know, in our, in our world, if we can put an engine on a test stand in, you know, hours or days instead of weeks or months, meaning we're close to our test site, we can additively manufacture components that we need, meaning that we've got a supply of infrastructure right on site, meaning that our components are modular enough where they can be transported, all of that, all the logistics that make that happen. If we can do that, then we're self sufficient in a way that is ahead of the pace of the industry and ahead of our own milestones. Whereas if we had allowed ourselves to sort of stretch out these responsibilities and sort of softly tail off into supply chains and consultants and partners, you really don't know whether or not you've got what you need to get the job done. And you really also delay the time in which you see the output or the value coming back from your investment.
Chris Kaufield [00:20:24]:
So having that, that focus on that in house capability where you can do end to end projects shows you then where you're going to reach the limits of those ended projects and shows you where people need to invest further. So, you know, for us, if we build all the propulsion elements that go on a rocket, and we say, you know what, we need to turn that up times five. We know exactly the math to turn that up times five versus this loose sense of suppliers and, and ownership that's out there. So that kind of self sufficiency is really important. I'd introduce one more accountability that really helps, I think, with this in terms of do you have the right people running the right thing, and are you getting back what you thought you would? And that's what I'll call operational accountability, meaning, do you have to run the stuff that you build? In our case, our business model depends on it. We're going to have a fleet of vehicles that are, if we're on course for daily flights and we're turning things around as rapidly as possible. The ability to do that goes all the way back to the original engineering team that started out building for that problem. And then you now live with it and you understand where you need to refine it.
Chris Kaufield [00:21:31]:
This is something that also helps with the guidance that grows a company successfully. If you have to live with your stuff, if you don't and you hand off your product to someone else, the signals are going to be fuzzy, varied, and if nothing else, just lengthy before you really understand what's going on and how to be successful. So we want to shorten all of that so you get a much more precise signal, and that signal will drive your organizational behavior.
Matt Gjertsen [00:21:55]:
It's really interesting how things that can seem so different are so similar. You know, you mentioned how when you build a part on the rocket, it's a physical thing that you can see, and if it works, it works. If it doesn't, it doesn't. And how that can be more difficult in fuzzier, you know, maybe soft skills, leadership, culture kind of things. But, wow, everything you were just saying, I think you could just change a few words and it would have the exact same meaning in the world that I'm more traditionally accustomed to. You say we want to launch some dei initiatives, and so you build a whole team in order to do that without taking the time. If you saying you want some Dei initiatives, there should be some clear outcome that you're trying to achieve or some clear wrong that you're trying to address in your company so that you can have that clear identif that clear, you know, go no go idea of did this work or did this not. But once you hire a bunch of people, build a big team, well now you got to use those people.
Matt Gjertsen [00:22:57]:
And so you're going to start doing stuff whether you need to or not really. And then similarly, let's say you don't build a big team, you outsource your leadership development. And so now there's some new thing, new problem that you're trying to solve inside your organization. Well, rather than going to an instructional designer and, you know, tweaking some slides or tweaking a presentation in a couple days and, you know, next week you're doing delivering some new material, you now have to go to the consultant, sign a new contract, figure out a whole new way you're going to work together. And now it's six months before you can roll it out. So in the end, you know, it all comes back to, you know, when we talk about like hard skills and soft skills. I always say the only difference between hard skills and soft skills is that we haven't thought about the soft skills hard enough to make them hard. Right.
Matt Gjertsen [00:23:46]:
But it all comes down to these same kind of clear deliverables or clear outcomes that we should all be trying to define.
Chris Kaufield [00:23:54]:
I think that's right. And I have a benefit of having worked in sort of the software world and certainly the software world and then in the hardware world and back again. And there is a, I mean, it's nothing more illuminating to cross the ponds where you may have come from, the world of software or consulting or something else, you go work on hardware for a while. And similarly going from hardware to these more ip driven or at least sort of cloud driven ideas these days, it's just hugely humbling. But it also lets you know that, yeah, there are some best practices you can borrow here and there. I happen to recommend hardware businesses these days. One, I think it's just the vanguard of a lot of things that the US needs, but also the world needs a lot of solutions that are coming, whether they're reducing carbon at sea or they're solving for more efficient supply chains or medical care. There's all sorts of things that are going to be hardware dependent and so we're seeing a lot of those things come to life.
Chris Kaufield [00:24:50]:
But again, that kind of hardware product tends to bring together or it tends to remove fuzziness about the state of the problem and the state of the development. Now, really opaque products can get into trouble kind of notoriously, you know, AI gadgets and all sorts of stuff that's meant to be top secret and then show up with a customer that probably didn't sort of, you know, follow a few of the things we just talked about. Like, for example, do you have to run those yourself? Would you have to sit with a caregiver to see how that actually works in the real world? You know, if you just sort of foist it on your customers. That's not the spirit of this at all either. The goal is to go quickly, but have attention so that you can keep going quickly and deliver the right thing.
Matt Gjertsen [00:25:36]:
Yeah. A couple more terms that have come up. You dove into continuous traceability. Traceability is something that I had never heard of until I got into the. Into the hardware world. Many people probably never heard about it. And then you realize as soon as you get there, as you were saying, it is one of the more important words in hardware, especially if you're dealing with government contracts. How have you seen that? Can you see that in a non hardware way as well? Like, when it comes to leadership, what does it mean to be trying to have that same kind of traceability? Or do you make an attempt to have that same kind of traceability of things like decisions in the organization?
Chris Kaufield [00:26:21]:
Yeah, I think the term is, it actually is everywhere. It's one of those terms where when you look for it, you'll just sort of see it everywhere. For example, you know, the food supply traceability of North Sea salmon, where did that come from versus. And how was it caught?
Matt Gjertsen [00:26:35]:
Yeah, exactly. Just for anybody who hasn't heard the term before, just to spread it out a little bit, again, in this world, you're selling a rocket to the us government. They put a big, expensive satellite on it. It goes up, something goes wrong with the launch, you kind of trace back to. There was a problem with this bolt. Okay, you know, what lot number was that bolt? Where was it stored? Was it stored properly for its entire life? Where did it come from? What plant was it manufactured in? That's kind of what traceability tends to mean in this hardware world.
Chris Kaufield [00:27:09]:
Yeah, that's right. And it does cross over into the human activity because it's not just the bolt. It was the procedure used to install the bolt. Well, that's a very human thing. That's an instructional thing. That's a process thing that, you know, does apply in any other industry. And the same is true with, you know, safe handling of food or medicines. Traceability is required for lots of aspirin.
Chris Kaufield [00:27:33]:
And these are the types of things that, for those folks that run critical supply chains like this, you know, almost every conversation is about how to get a better understanding and inspection of where things are going, where they're not, or, you know, could be fair, fair trade apparel. I mean, there, there's all sorts of physical products now that have to embed a history and a story of their provenance to be successful. But I think it really is for high performance cultures where you're making some of these breakthrough moves one way or another. I think companies find a way to, if they don't call it traceability, they embed it into the culture. I mean, famously at Amazon, the notorious six page memo that everybody needs to read before they embark on a particular track of a new project. Dedicate time to reading the memo. You go to the meeting and say, don't worry about being prepared. We're all going to sit down and study the original view of what we're about to take on the pros and the cons, but also the expected outcome.
Chris Kaufield [00:28:29]:
That original memo is a traceability history for the moves you're going to make. And so when Amazon goes into music or they go into some new distributed product, you can see all the way back to the path of decision making and how that led to different investments and the course corrections and so on. So I think, yeah, traceability certainly has a role in human decisions and behavior. I think it just, hardware is one of those great sort of disciplines that forces you to look at it and say it's not a nice to have, it's a must have.
Matt Gjertsen [00:28:58]:
Yeah. Well, as you said, you've been at a lot of organizations. You've been on the hardware side, you've been at the software side, you've been in a lot of very successful organizations. When you think about this, like high cadence engineering or a high cadence organization for leaders, whether they're all organizations like this or they're just trying to create a team like this, what are some other ways other than what we've talked about, kind of the role of a leader change in a high cadence organization?
Chris Kaufield [00:29:26]:
Well, certainly you're not looking for, I think it puts a new stress on leaders as practitioners or to have some ability to contribute the actual effect of the team. So in other words, for a long time we thought we could abstract away the idea of leadership and simply have managers in place. And that's been seeing some upheaval. The folks that run and own elements of a rocket program at STOQ are the folks that understand what the team is building. And so they may not be in the placed at the most senior level, but they run that functional team in a sort of a matrix style, I suppose. But certainly ownership of the product means that you're a leader in practice, if not in the chart. So that's something to look out for of just put people in harm's way, put people where they have to do the job that they're responsible for. Allow the team to right size itself appropriately so that that leader gets the support they need, but give them some tools and hands off and let them run.
Chris Kaufield [00:30:32]:
And the best way to do that is not to sort of hope for the best, but create dependencies among other leaders so that the whole system is adjusting and checking on where there might be gaps or limits or maybe even skills that need to be brought in. Because otherwise it's a little bit, feels a little disempowering to sort of, especially at an executive level, say, okay, leaders, let's just run amok. What we're really trying to do is create a system of dependencies so that leaders are boosting each other.
Matt Gjertsen [00:30:59]:
Yeah, yeah, and yeah, I 100% agree with that. Of this idea of like, you need to. It goes back to the idea that you used of operational accountability, of you need to give people some tools and let them run with it. The one thing I would ask you though, you know, with this like kind of matrix style organization, with this distributed ownership, is do you have any particular ways to make critical decisions or even just general decisions or deal with conflict because there's so many different owners and you're kind of relying on this give and take between them to find the right, the right solution. How do you make sure that those are amicable discussions, that they're based on fact and not personality? You know, what are the techniques that you use?
Chris Kaufield [00:31:41]:
Yeah, engineering specifically. But again, I think we can generalize here. It's all about trades. And again, you get a bit of a benefit in hardware that the trades are based on physics and real world conditions that people have not conjured up. And so, you know, what you're really doing is you're resolving conflicts around the expected performance of the product you're making. Not conflicts among people, is what happens. Because if I say, boy, I found a great way to build a very reliable battery system for the avionics. It's just going to cost us 20 payload.
Chris Kaufield [00:32:16]:
People are saying, hey, we can't have that trade because that payload is already under stress from something else we're trying to have. So you can have 5 kg, that very sort of contrived example, but it happens nonstop. And when you have a product that's front and center, asking for people to optimize it. That's what happens. And that's where conflict gets resolved. Versus the classic, well, it's time for annual budgets. Raise your hand and advocate for your team and hope you get the extra head count or hope you have the least amount of pain when it comes to reducing the team. All of that sort of thing is trying to optimize an organization.
Chris Kaufield [00:32:50]:
Nothing. Optimize a product. So I think wherever possible, find those things that have the immutable laws around them and have people attack that optimization schedule, rather than the things that we all like to contrive and the things that don't really matter in the end. If you're not building a hardware product, get customer centric. That's the way to do this, is to get in front of a customer who has to optimize with their rules, which to you are immutable, but you can work on those and you can ship away at those. And so if you have a consulting client or you have a software product you're shipping, that customer wants to have a trade off between sort of cost and performance. They want to have a trade off between ease of use and sophistication. They want all those things.
Chris Kaufield [00:33:31]:
Well, that's pretty good. And that's a lot better than taking the guesswork internally and just sort of propping up your departments.
Matt Gjertsen [00:33:38]:
Yeah, absolutely. And I also just really love that idea of trades. You know, I heard recently someone, I forget where exactly I heard this, but they said there's no solutions, there's only trade offs.
Chris Kaufield [00:33:51]:
Yeah.
Matt Gjertsen [00:33:52]:
And it's such a great way to enter into a mindset, to enter into any disagreement or any conversation with, because it becomes not about deciding who's right or wrong. We're saying there is not a right and wrong. Many of these things could be right or wrong, depending on what we care about most. And so it's just about these trade offs of finding how we're going to find a balance between the two decisions.
Chris Kaufield [00:34:17]:
Yeah. And of course, to complete the loop, you need to instrument the trades to understand, did we get what we thought we would out of that trade? Did you get the thrust out of the rocket engine, or did you get the uptick in sales? Or did you get the increased safety headroom of a given problem? And so you need to instrument it constantly. So data is absolutely the lifeblood of, but it's no substitute for people having a concept of what are good trades. We'll see if AI can help with this. But so far in this type of world where you're really breaking new ground and you're coming up with new products, it's a lot of judgment backed by evidence and a sort of a virtual cycle to make sure that those two things stay together as fast as possible.
Matt Gjertsen [00:34:56]:
Yeah. Awesome. I love talking. I think one of the most interesting things about the rocket world is that getting to space is just such a hard problem that it pushes. You're always on the edge cases. You're always, you know, just pushing the boundaries. And I think it's a really great way to think about all aspects of human challenges and taking that same kind of mindset. So, really excited to kind of talk through this with you.
Matt Gjertsen [00:35:25]:
What, you know, so, stokespace, like you said, you, you had your first flight of kind of that, the, this the test second stage of the vehicle. You got the initial hot fire of your first stage engine, which is just tremendous. Um, I know you don't talk, as you said, you tend to, like, do more than talk at Stoke. What are, like, the next big milestones? I mean, I feel like if you're just doing imagine it's going to be a quite a long campaign of hot firing before we start talking about, like, first stage stuff. Like whole first stage.
Chris Kaufield [00:35:54]:
Yeah, I'm, you know, as we talk, I'm sitting in about 175,000 manufacturing space in my side room here, and it's humming. I mean, we're building all the components that you would expect to visualize on our rocket, which we call Nova. Nova two stage rocket, if you want just sort of a sense of what can carry, think, small car kind of payload and maybe a bit beyond sort of medium lift category is the way we look at it. But all the elements are now been either fabricated in full scale or close to it, and are now available for our, you know, sort of, let's call it light integration tests of how things will come together. So that's really for us, a major milestone in that we can say we're now on the later stages of development, cycles sort of all up. And as we move forward, it's going to be more and more systems becoming larger blocks for testing rather than for, you know, smaller discrete elements. And then ultimately what that sort of turns into is the first, you know, full scale launch in orbital flight, which is sort of in a calendar year plus sort of horizon. So not far off, but not immediate, but certainly on a rocket schedule that will be the fastest ever of a company moving from seed money to first flight.
Chris Kaufield [00:37:10]:
In fact, all of our milestones, first engine fires and hops have all been ahead of any industry pace like this, so that's something that's really hard earned. But it's also just a lot of great people figuring out how to pull together a program and borrow all the things they learned elsewhere and bring them to a nice point here. Coupled with some fantastic leadership of Andy and Tom who've been through this before in different places and saw things they liked and didn't. And now we're just keeping up that pace so we can hit that goal of daily flights and full reuse.
Matt Gjertsen [00:37:43]:
Awesome. Well, I'm a huge fan. I'm excited. I hope I'm certain Stoke got a few more fans listening to this, people who'd never heard of it before. So I can't wait to see the future success of the company. Thank you again so much for coming on today. Chris and I look forward to chatting with you.
Chris Kaufield [00:38:01]:
You're welcome. Thanks so much for having me.
Matt Gjertsen [00:38:04]:
Thank you so much for listening to today's show. If you are looking for help turning your organization's great engineers into great managers, me and my team at better everyday studios would love to help. We deliver targeted and interactive training workshops that are designed to help build the three fundamental skills of any new manager, building trust, giving feedback, and setting goals. Reach out to me through matt@betterevydaystudios.com so we can start making your organization Better Every Day.

