Published by Matt Gjertsen - Better Every Day Studios
Management
Business
Careers
Welcome to the Leadership Launchpad where we help technical managers improve themselves, their teams, and their organizations. Host Matt Gjertsen — former Air Force instructor pilot and head of training and development at SpaceX — brings hard-won lessons from the world's most demanding organizations to help new managers lead with clarity and confidence. Each episode cuts through the noise with practical frameworks, real stories, and straight talk on what it actually takes to build high-performing teams in aerospace, defense, and beyond. Whether you're managing engineers, navigating organizational chaos, or just trying not to let your team down, Leadership Launchpad gives you the tools to get better every day.
Everyone talks about ownership. Very few people can actually explain what it looks like. Seth Kovnat spent six years at SpaceX helping scale Falcon launches from 24 to 148 missions a year before joining Impulse Space as Director of Vehicle Engineering. Along the way, he developed a way of thinking about engineering that goes far beyond technical ability. At the center of that mindset is the Responsible Engineer. Not someone who owns a part. Someone who owns the outcome. We get into why ownership isn't about protecting your work. It's about bringing in the right people, inviting criticism early, and doing whatever gives the mission the best chance of succeeding. That sounds simple, but it's a very different way of leading technical teams than most organizations practice. We also talk about what changes when engineers become leaders, why letting go of technical control is one of the hardest transitions to make, and how great engineering organizations create cultures where responsibility grows with every level of the organization instead of getting bottlenecked at the top. If you lead engineers, build products, or care about creating teams that move fast without sacrificing quality, this conversation is packed with practical lessons from someone who's helped build at the highest level. EPISODE HIGHLIGHTS [00:00] Introduction [00:03:13] Why Seth wrote an engineering children's book [00:08:00] Building vehicles at Impulse Space [00:10:10] The responsible engineer mindset [00:12:18] What SpaceX got right about ownership [00:18:16] Building a culture of ownership [00:21:19] Why planning beats reacting [00:23:00] Failing smart instead of failing busy [00:26:20] The hardest transition from engineer to leader [00:27:28] Scaling ownership across an organization KEY TAKEAWAYS Ownership means owning outcomes, not just completing tasks Great engineering requires collaboration, not individual heroics The best engineers actively seek feedback early Strong engineering cultures remove ego from decision-making Responsible engineers orchestrate people as much as technical work Building without clear intent creates the illusion of progress Attack the biggest risks first, not the easiest problems Leadership requires letting go of technical control Accountability should grow as organizations scale High-performing engineering teams succeed because ownership exists at every level If this episode resonates with you, subscribe to the show, share it with someone building engineering teams, and leave a review so more technical leaders can discover the conversation. Links & Resources Seth Kovnat LinkedIn: https://www.linkedin.com/in/sethkovnat/ Website: https://pragmatist.tech/ Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most engineers become leaders because they're great at solving problems. Then they get promoted... and suddenly the thing that made them successful starts getting in the way. If you've ever struggled to delegate, found yourself jumping in to fix everything, or wondered why your team keeps bringing every problem back to you, this conversation will probably hit close to home. Ashley Chang started her career as an engineer and now leads training and development at Anduril. She talks about what really changes when you move from individual contributor to leader, and why leading isn't about having all the answers anymore. It's about asking better questions, setting clear expectations, and creating an environment where your team can solve problems without depending on you. We also get into why so many companies confuse "don't micromanage" with "don't lead," why coaching is a skill that has to be developed, and why technical experts don't automatically become great teachers just because they're the best at the job. If you're leading engineers, manufacturing teams, or any technical organization, this episode is a practical conversation about what actually changes when your job shifts from doing the work to helping other people do it well. EPISODE HIGHLIGHTS [00:00] Introduction [00:02:38] Why engineers struggle when they become managers [00:05:48] Finding the right balance between delegation and micromanagement [00:09:16] What makes technical training different [00:11:32] Breaking old habits and creating new standards [00:14:00] Why great performers don't always make great trainers [00:17:12] Asking better questions instead of giving answers [00:22:28] Why training should be treated like a product [00:25:57] Overcommunication beats undercommunication [00:26:56] Knowing what should and shouldn't be trained KEY TAKEAWAYS Great engineers don't automatically become great leaders Leadership starts when you stop trying to solve every problem yourself Delegation changes based on each person's experience and maturity Clear expectations are different from micromanagement The best coaches ask questions before offering solutions Technical experts need coaching skills to become effective trainers Good onboarding teaches both the work and the culture Training only works when leaders reinforce it every day Overcommunication is usually better than undercommunication Teach principles that stay the same, even when processes change If this episode resonated with you, subscribe to the show, share it with someone leading a technical team, and leave a review so more engineering leaders can find these conversations. Links & Resources Ashley Chang LinkedIn: https://www.linkedin.com/in/ashleylchang/ Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most companies say they’re developing leaders. But when you look at what actually happens on the floor, or inside a new manager’s first real team, it doesn’t line up. Craig Coyle spent years as an Army aviator and now works with frontline leaders in manufacturing and defense environments. What he saw in both worlds is the same gap, people are promoted into leadership, then left to figure it out in real time, without the structure they were used to as operators. In aviation, that doesn’t happen. You don’t just become a pilot in command and get told to figure it out. There’s progression, there’s repetition, there’s instructor pilots inside the mission, not outside of it. That contrast is what drives this conversation. We talk through what changes when leadership is treated like a skill that needs structured training instead of something people just “grow into.” And why most development programs fall short, not because the content is wrong, but because it’s removed from the environment where the work actually happens. There’s also a deeper problem underneath it all, most organizations don’t have a clear definition of what “good” looks like for a manager. So people default to whatever worked for them personally, or whatever their last boss did. That inconsistency is what creates the gap between intent and execution. Craig breaks down what he’s building now, a model that treats leadership development less like theory and more like progression inside a system, similar to how pilots are trained over time, not in isolated workshops. If you lead people, or you’re responsible for people who lead people, this episode is really about one thing, what it would take to make leadership actually show up on the floor, not just in training materials. EPISODE HIGHLIGHTS [00:00] Introduction [00:01:00] Most people don’t know what training actually is [00:02:33] Military vs corporate leadership development gap [00:06:46] “Figure it out” leadership in the Army [00:09:35] Learning leadership the hard way after promotion [00:10:05] Why pilot training builds a different standard [00:15:28] Procedure vs technique in decision making [00:17:00] Science vs art of leadership [00:22:20] Why classroom training fails on the floor [00:29:00] The bandwidth problem in leadership roles [00:32:00] Why prioritization decides everything in leadership [00:35:03] Why most leadership training doesn’t move the needle [00:37:00] Closing the “back door” in workforce development [00:39:00] Minimum Viable Manager concept KEY TAKEAWAYS Most leadership training fails because it’s removed from the environment where work actually happens “Figure it out” is not a leadership system, it’s a gap in one Aviation builds leadership through progression, not one-off training Good management requires structure, not just experience Instruction needs to exist inside operations, not outside them Procedure creates consistency, technique creates flexibility Most organizations don’t define what “good manager” actually means Context is what makes training stick, not content alone Bandwidth is one of the biggest hidden limits in leadership You don’t fix leadership by adding content, you fix it by changing the system If this episode resonates with you, subscribe to the show, share it with someone who leads a team, and leave a review so more people building in complex environments can find it. Links & Resources Craig Coyle LinkedIn: https://www.linkedin.com/in/craig-coyle/ Website: https://operationlead.com/ YouTube: https://www.youtube.com/@OperationLead Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most technical training programs fail before the first technician ever sets foot in the room. Not because the content is wrong. Because the entire design is wrong. Traditional training asks: did they understand it? Technical training asks something harder: can they actually do it? And in aerospace, where it takes a million things to go right and one thing to go wrong. In this first ever live episode of the Leadership Launchpad, Matt sits down with Roy Samson, a technical training veteran from the aerospace industry. Together they break down what it actually takes to build a training program for a technical team. What you'll learn: Why "passing the course" isn't the same as being ready — and how to handle the gap How to decide how much theory a technician actually needs (and when to skip it entirely) What "building an OS for quality" means and why it matters more than any curriculum How to build credibility with subject matter experts when you don't have a technical background Why training will happen in your org whether you plan it or not — and why that should scare you For engineering managers, technical leads, and L&D professionals trying to build real capability in hard tech environments. New episodes weekly. Subscribe and drop a comment if you want us to go deeper on any of these topics. Learn more at BuiltLeaders.com
Most leaders talk about speed. Ian Walsh doesn’t. In this conversation, he separates speed from what actually matters in leadership: velocity, meaning speed with direction. Ian has spent his career in aerospace and defense, from flying Marine Cobra attack helicopters to leading companies through scale and transformation. Now as CEO of FDH Aero , he is operating inside an industry that is growing fast and getting more complex. He starts every new role in listen and learn mode. No immediate changes, no playbook, just understanding how the business actually works. That mindset carries through how he thinks about scaling. Fixing a business is about rebuilding capability. Scaling is about making sure the core can support growth without breaking when conditions change. A big part of his approach is how decisions move through an organization. Push them closer to the work, but keep clear guardrails and one accountable owner for each outcome. He also focuses on a few simple questions: do people know where they are going and how fast, are decisions stuck at the top, and do people actually feel accountable. At the center of it all is communication. When people are guessing, alignment breaks. And when alignment breaks, everything slows down, even if it looks like progress. This episode is a grounded look at leadership inside complex environments where clarity and ownership matter more than anything else. If you are early in your career, this is a blueprint for how leaders think. If you are more experienced, it is a check on whether you are still getting the basics right. EPISODE HIGHLIGHTS [00:00] Speed is dangerous, velocity requires direction [00:02:49] Aerospace as a constantly evolving global industry [00:06:36] Starting any new role in listen and learn mode [00:10:24] The difference between fixing and scaling a business [00:14:45] Speed versus velocity in decision making [00:18:22] Communication as the foundation of alignment [00:22:53] Why delegation fails without training and support [00:27:13] Values versus performance in leadership decisions [00:28:53] Lessons on risk and judgment from aviation [00:31:27] Building better risk awareness through experience [00:32:54] Sustaining a high performance culture over time KEY TAKEAWAYS Speed without direction creates risk rather than progress Every new organization requires time spent listening and understanding Leadership playbooks rarely transfer cleanly between companies Scaling requires leveraging fixed systems, not only adding resources Decentralization only works when paired with clear guardrails Accountability breaks down when ownership is unclear Most bottlenecks are caused by misalignment, not lack of effort Communication needs to match the pace of change in the organization Values can be identified, performance can be developed High performance cultures are built through consistent behavior over time If this episode resonates with you, subscribe to the show, share it with someone who leads a team, and leave a review so more people building in complex environments can find it. Links & Resources Ian Walsh LinkedIn: https://www.linkedin.com/in/ian-walsh-76864a2b/ Website: https://fdhaero.com/ YouTube: https://www.youtube.com/@FDHAero Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most people think leadership starts when someone gives them authority. I don't think that's true. One of the ideas that kept coming up in my conversation with Keith Ferrazzi is that leadership is rarely granted before it's demonstrated. The people who create outsized impact inside organizations aren't waiting for the title, the promotion, or the perfect moment. They're already acting like leaders long before anyone officially calls them one. That matters more today than ever. The pace of change is accelerating. Industries are being reshaped by AI, supply chain volatility, shifting markets, and entirely new ways of working. In that environment, technical expertise alone isn't enough. The people who continue to grow are the ones who know how to learn faster, build stronger relationships, challenge ideas constructively, and bring others with them. Keith has spent decades studying high-performing teams and advising some of the world's largest organizations. What stood out to me most wasn't a complicated leadership framework. It was how much of great leadership comes down to simple, repeatable practices that most teams never adopt. The uncomfortable reality is that most teams are mediocre. They avoid conflict. They don't challenge each other when it matters. They don't hold each other accountable. They don't create the kind of trust that allows great work to happen. The good news is that you don't need permission to change that. This conversation explores what it means to lead without authority, how high-performing teams are built through practice rather than personality, and why taking responsibility for your own growth is still one of the highest leverage decisions you can make. If you're early in your leadership journey, this episode is a blueprint. If you've been leading for years, it's a reminder that the fundamentals still matter. EPISODE HIGHLIGHTS [00:00] Intro [04:28] Is the MBA Still Worth It in an AI-Driven World? [07:48] Why Relationships Drive Opportunity, Learning, and Execution [12:08] Why Most Teams Never Reach High Performance [15:09] The Stress Test Framework for Better Team Decisions [19:58] Building Teams That Care About Each Other's Energy [21:53] The Three Types of Trust Every Leader Must Understand [26:00] Why Most Leaders Are Still Mediocre [29:37] Building a Peer Group That Won't Let You Fail KEY TAKEAWAYS Leadership begins before you receive a title or formal authority The fastest learners build relationships with people already doing what they aspire to do Everything meaningful in your career happens with and through other people High-performing teams are built through practice, not personality Most teams avoid the difficult conversations that create trust and accountability Trust is not one thing; it includes personal, professional, and structural trust Changing behavior is often easier than changing mindset Simple collaboration practices can dramatically improve team performance The bar for exceptional leadership is lower than most people realize Taking responsibility for your own development is a competitive advantage Links & Resources Keith Ferrazzi LinkedIn: linkedin.com/in/keithferrazzi Website: https://ferrazzigreenlight.com/ Book: https://shop.givingtons.com/products/never-lead-alone Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most teams don’t fail because they lack talent. They fail because they lose their ability to operate under discomfort. In this solo episode of Leadership Launchpad, I look at why the ability to stay effective when things get uncomfortable has become a defining factor in how modern teams perform. I draw a distinction between pressure that sharpens performance and pressure that overwhelms it, and why the difference between the two shows up in how teams are built, led, and developed over time. This matters because most organizations are operating in environments where change is constant, expectations shift quickly, and comfort is no longer a reliable indicator of stability or success. The real question for leaders is not whether their teams can avoid pressure, but whether they can function inside it without losing clarity or speed. That is what this episode is ultimately about. Episode Highlights: [00:00] Why uncomfortable teams outperform comfortable ones [03:19] Why the Body Only Grows Under Pressure [06:48] What Discomfort Looks Like Inside Organizations [07:50] Accountability vs Committee Culture [10:50] The Leadership Challenge of Pushing People [12:12] Why AI and Rapid Change Are Increasing Organizational Stress [15:08] Building Trust Before Raising Standards [17:31] The Key Question Every Manager Should Ask Key Takeaways: High-performing teams expand their capacity for discomfort over time Not all pressure reduces performance, some of it improves it Growth comes from exposure, not avoidance Feedback and accountability shape how teams respond under stress Fast-changing environments reward adaptability over stability Leadership is often about deciding what level of pressure a team can sustain The future belongs to teams that can stay clear and effective under uncertainty If this resonates with how you think about leadership and performance, subscribe for more conversations on building teams that operate well in complex environments. Links & Resources Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most companies don’t fail because they lack process. They fail because they keep the wrong ones alive for too long. Process starts as a survival tool. It reduces chaos, aligns people, and turns scattered effort into repeatable execution. But at scale, the same systems that create clarity slowly become the thing that blocks it. The real challenge isn’t building structure, it’s knowing when it stops serving the work. Chap Snowden , COO of AstroForge , has had to live inside that tension in one of the most extreme environments possible: building a company trying to mine asteroids. When your timeline is measured in mission cycles and your risks are existential, there’s no room for process that exists “just because it used to work.” What emerges instead is a different operating principle: processes are temporary hypotheses. They exist to solve problems inside a specific window of time, sometimes 60 days, sometimes 180. After that, they either prove their value or they get removed without hesitation. This episode explores what it actually takes to build that kind of operating system in practice. Not in theory, not in frameworks, but in real organizational decision-making where speed, alignment, and clarity constantly collide. It’s a conversation about how companies scale without calcifying, how leaders stay aligned when they don’t always agree, and why the most dangerous thing in any growing organization is an unexamined process that no one remembers the origin of. Episode Highlights: [00:00] When processes quietly become the problem (and why most teams miss it) [03:53] From Banking to Building: The Search for Meaningful Systems [08:35] Choosing High-Binary Bets and Aligning Under Uncertainty [14:57] Disagree Fast, Design Light: The Minimum Viable Process Mindset [20:56] Minimum Viable Process: Killing Tribal Knowledge and Friction [24:16] Instructional Design and Respecting User Attention [27:06] Communication Speed Over Perfection [31:27] Bad Process Starts With Unclear Problem Key Takeaways Process is temporary and should expire when the problem changes The real failure in scaling is keeping outdated process too long Misalignment in mental models is a bigger problem than lack of effort Minimum viable process means only what is necessary for repeatability Speed forces clarity and exposes weak assumptions early Tribal knowledge does not scale and eventually breaks systems Operations should be designed like product experiences The hardest skill in leadership is removing process not adding it If this resonates with how you are thinking about leadership and scaling teams, subscribe for more conversations like this. Links & Resources Chapman Snowden LinkedIn: https://www.linkedin.com/in/chapmansnowden Website: https://www.astroforge.com/ Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most people think leadership in technical companies is about being the most knowledgeable person in the room. Knowing the answers, setting the direction, and solving the hardest problems yourself. But the longer you spend actually doing the job, the more obvious it becomes that this is almost never what matters. The real challenge is much simpler to describe and much harder to execute. Getting people aligned on what actually matters, making sure they’re working on the right problems, and then building the environment where they can keep improving how they do it. Most teams don’t fail because they lack talent, they fail because they slowly drift away from focus without realizing it. In this episode, I sit down with Nancy Cable , Senior Director of Manufacturing at Ursa Major, to talk about what leadership actually looks like inside a fast-scaling aerospace company. We get into how she thinks about building and scaling manufacturing systems, why hiring for attitude and initiative matters more than pure technical skill in her world, and how she thinks about managing teams that are growing quickly in both size and complexity. A big theme in this conversation is the tension between chaos and structure. In an environment where teams are building real hardware fast, it’s easy to get pulled into constant tactical firefighting. The real leadership challenge is knowing when to step into that chaos, and when to step back and make sure the system is actually scaling in the right direction. Episode Highlights 00:00 Setting the stage for leadership in aerospace 01:00 From Propulsion to Scalable Aerospace Manufacturing 04:24 Inside Manufacturing at Ursa Major 07:10 How Leaders Show Up, Not What They Represent 09:54 Building teams with emotional and technical diversity 13:14 The mistake of treating everyone the same 18:05 Hiring for initiative over pure technical ability 20:59 Why Hiring Isn’t About Finding Perfect People 24:06 Culture screening and the ‘airport test 28:57 Balancing chaos vs structure in fast-moving teams 30:57 Staying grounded when everything feels tactical Key Takeaways Leadership is not about having all the answers, it is about making sure the team is working on the right things. Most teams do not fail from lack of talent, they fail from lack of focus and alignment. Hiring for initiative and attitude matters more than purely technical skill in fast moving environments. Scaling is not just doing more work, it is building systems that can handle growth without losing speed or clarity. Great leaders do not create answers, they create environments where better answers surface and get used. Culture is not a one time screen, it is reinforced through every hire, decision, and interaction. The real challenge of leadership is balancing chaos and structure without losing direction. Links & Resources Nancy Cable LinkedIn: linkedin.com/in/nancy-cable-583929b Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most leaders think their job is complicated. It’s not. I tend to break it down into three things: get people working together, get them working on the right things, and improve the work over time. The problem is that second one. Getting people focused on the right things sounds simple, but in practice, it’s where most teams fall apart. In this episode, I sit down with Matt Gialich , CEO of AstroForge , to talk about what that actually looks like inside a company trying to do something insanely hard, mining asteroids in deep space. We get into how he unexpectedly became CEO, why the job is less about vision and more about doing whatever needs to get done, and how easy it is for teams to drift even when everyone is talented and working hard. A big theme throughout this conversation is focus vs overengineering. Engineers naturally want to go beyond the requirement, make things stronger, better, more robust. But that almost always comes at the cost of speed. And in environments like space or startups, speed is not optional, it is the advantage. Learning faster, iterating faster, and actually shipping matters more than building something “perfect.” We also talk about fear, how it shows up in teams, how it leads to overthinking and unnecessary work, and why staying close to the actual mission is the only real way to fight it. No frameworks, no hacks. Just being in the room, talking to people, and constantly reinforcing what actually matters. If you are leading a team, especially in a fast moving or technical environment, this is really a conversation about what the job actually is and what it is not. Episode Highlights 00:00 What it actually means to be a CEO 03:40 AstroForge Didn’t Start in Space, It Started as a Submarine Company 07:54 Building Somebody Else’s Company15:30 The “overengineering problem” in technical teams 13:42 Monthly Calendar Audit for Cutting Out Noise 18:49 Why Small Teams Overbuild Instead of Staying Focused 23:12 Speed, Fear, and Why Iteration Beats Perfection 27:28 Flight Cadence, Failure, and Why Speed Beats Perfection in Space 31:45 Execution, Auditing Reality, and the First Deep Space Missions Key Takeaways A CEO’s job is not abstract vision, it is execution on whatever increases enterprise value Small teams don’t fail from lack of talent, they fail from lack of focus Engineers naturally optimize beyond requirements, but that often slows down learning and iteration Speed is not just execution, it is a way to reduce risk over time Fear inside teams often shows up as overthinking or overbuilding The real job of leadership is constantly reinforcing what matters and removing noise You do not scale alignment with frameworks, you scale it with repetition and presence Most organizational problems are actually prioritization problems in disguise Links & Resources Matt Gialich LinkedIn: https://www.linkedin.com/in/matthew-gialich AstroForge Website: https://www.astroforge.com/about-us Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
This solo episode explores the challenges and opportunities facing hard tech and leadership in today’s rapidly evolving technology landscape. The host announces the rebranding of their company from Better Everyday Studios to Built, with a renewed focus on training the next generation of hard tech leaders. The discussion covers why large-scale technology projects so often run over budget, highlights the critical role of leadership in the success of ambitious endeavors, and examines how AI is reshaping company sizes and the demand for effective technical leaders. The episode also outlines three key reasons why developing strong leaders is more essential than ever. Listeners are invited to tune in next week for a conversation with Matt Gialich from Astroforge, who will share insights on asteroid mining and building agile organizations.
On this week’s episode of the Leadership Launchpad, we are bringing you a crossover episode from the VHTB podcast. If you enjoy the discussion and want more make sure to check out other episodes. YouTube: https://bit.ly/4sooBQo Spotify: https://bit.ly/3YRPxue Apple: https://apple.co/4q3Zn8k Where’s the line between pushing people to do their best work… and just being an asshole? It’s a question that comes up a lot in high-performance environments especially in hard tech, where the stakes are high and the margin for error is small. Because in industries like space, defense, and advanced engineering, “good enough” isn’t good enough. The standards are high for a reason. But how you enforce those standards? That’s where things get complicated. In this episode, Matt Gjertsen from Better Every Day Studios is joined by Brian Mejeur from AdAstra Talent Advisors and Justus Kilian from Space Capital to talk through that tension. We get into what actually drives people to perform at their best and why simply pushing harder isn’t always the answer. We get into the difference between attacking the problem versus attacking the person, why self-motivation matters more than external pressure, and how culture shapes where that “line” actually sits. We talk about the reality that not everyone is motivated the same way. Some people thrive in intense, high-pressure environments. Others shut down completely. And if it’s not clear upfront, that creates real problems in hiring, retention, and performance. If you’re leading a team or working in one, this episode is a thoughtful look at how to balance high standards with respect, and how to build a culture that pushes people without breaking them. Episode Highlights [00:00] Why high standards matter more in hard tech [01:43] The fine line between pushing performance and crossing it [04:04] Why people only work hard when they’re bought into the mission [05:21] Self-motivation vs. forced motivation [08:09] Personal vs. problem-focused feedback [10:06] What happens when leaders go too far [12:00] The “asshole tax” of doing big, disruptive things [14:04] Why the line moves depending on context [15:00] The real job of a manager: driving performance, not venting Episode Takeaways High standards are necessary in hard tech, but how you enforce them matters just as much. People are more motivated by mission and belief than by pressure alone. Great leaders focus criticism on the problem not the person. Self-motivation (“batteries included”) is one of the most important traits in high performers. Culture clarity is critical people need to know what they’re signing up for. Intensity can drive performance, but only in high-trust environments. The line between pushing and going too far isn’t fixed it moves based on trust, consistency, and alignment. Subscribe to VHTB for more insights on the talent, culture, and finance sides of space startups. Resources & Links Space Capital: https://www.spacecapital.com/ Better Every Day Studios: https://bettereverydaystudios.com/ Ad Astra Talent Advisors: https://adastra.us/
Most teams think leadership at SpaceX is about speed, pressure, and technical brilliance. Hans Koenigsmann, former VP of Build and Flight Reliability and one of the earliest employees at SpaceX, describes something more subtle: it’s about constantly operating outside your comfort zone, and learning how to make decisions when everything is changing at once. In this conversation, Hans reflects on what it was like growing with SpaceX from a handful of people to over 14,000 employees, and how that scale forced him to repeatedly shift not just his role, but his identity as a leader. He talks about moving away from being a “generalist who can duct tape things together” toward finding where he could actually be useful at system level. We also get into how he thinks about risk, not as something objective, but as something deeply personal. Hans explains why you should never evaluate risk alone, how teams normalize danger over time, and why diverse perspectives matter more than most formal risk frameworks. There’s also a strong theme around leadership humility. Hans shares how SpaceX changed his perspective on ego, company alignment, and what it actually means to put organizational goals ahead of individual ones — especially when decisions get uncomfortable. And throughout the episode, one idea keeps coming up: growth doesn’t come from staying in control, it comes from repeatedly stepping into situations where you’re not. If you’re interested in how high-performance technical organizations actually operate behind the scenes, this one is worth your time. Episode Highlights 00:00 Stepping outside your comfort zone 03:10 Scaling from early SpaceX to 14,000+ people 06:00 Finding where you’re actually useful as a leader 08:30 Leadership training and what doesn’t translate 11:30 Why risk is personal, not objective 14:05 How teams normalize risk over time 15:59 Learning from other people’s failures 17:54 Thinking about launch costs and competition Key Takeaways Leadership roles shift dramatically as organizations scale, even if titles stay the same. Generalists often need to reposition themselves as systems become more specialized. Risk perception is personal and changes based on experience and context. Teams need diverse perspectives to properly evaluate risk. You should never evaluate risk in isolation. Most of leadership growth comes from operating outside your comfort zone repeatedly. Learning from other people’s failures is one of the fastest ways to build judgment. Humility and company alignment become more important as organizations scale. Links & Resources Hans Koenigsmann LinkedIn: linkedin.com/in/hans-koenigsmann-2a141b5 Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most teams don’t realize they’re missing critical data until something goes wrong. In this episode, Austin Spiegel, co-founder and CTO of Sift and former SpaceX engineer, dives into why telemetry, simple in concept, a value and a timestamp, can become a massive problem in hardware. Miss even a fraction of a second, and you lose the story. Software engineers have plenty of tools to solve this. Hardware engineers haven’t, until now. We also talk leadership, what it’s like stepping into management early, why teams can actually be too flat, and how your role shifts from doing the work to connecting context. On hiring, Austin explains why pedigree doesn’t equal talent, and how Sift focuses on practical, real-world ability. And throughout, one theme emerges: speed. Not just moving fast, but learning and iterating faster than anyone else. If you’re building complex systems or leading technical teams, this one hits on a lot of things that don’t usually get said out loud. Episode Highlights 00:00 What telemetry actually is (and why it fails) 05:07 Why hardware never got its “Datadog moment” 12:05 The real challenge of high-frequency data 17:43 Becoming a manager too early at SpaceX 22:27 Interviewing for skills and values over pedigree. 26:59 The shift from doing work to providing context 31:32 Motivating engineers through customer impact Key Takeaways Telemetry is simple in theory but breaks at scale and speed. Hardware teams lack the modern data tools software teams take for granted. Flat organizations can create decision bottlenecks. Great managers connect context more than they give answers. Pedigree is a weak signal, practical ability matters more. Interviews should mirror the actual job, not abstract problems. Speed is really about learning faster than everyone else. Engineers move faster when they’re closer to the customer. Links & Resources Austin Spiegel LinkedIn: https://www.linkedin.com/in/austin-spiegel/ Sift Website: https://www.siftstack.com/ Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most technical teams think they have a technology problem. They usually don’t. In this episode, Dr. Thomas Zurbuchen, former head of NASA’s Science Mission Directorate, talks about what actually goes wrong after overseeing dozens of missions and tens of billions in spend. We get into why canceling missions isn’t failure. It’s what makes risk possible in the first place. If you don’t kill things, one bad bet can quietly consume everything around it. He also breaks down something that feels backwards at first. Constraints are what make teams better. Not more time. Not more people. Not more budget. Constraints. There’s a moment where he talks about realizing he could actually destroy teams by giving them more funding. That shift from “provide resources” to “protect focus” shows up again and again in how he thinks about leadership. We also get into what happens as organizations scale. How they drift toward safety. How bureaucracy creeps in without anyone intending it. And why speed is usually the first thing you lose. On the team side, we talk about why adding people when you’re behind often makes things worse, not better. And how much of leadership is just making sure the right people are in the right roles, not trying to turn everyone into something they’re not. There’s also a really practical piece on creating a culture where ideas get challenged hard, without people feeling attacked. What that actually looks like in a room, and why most teams get that balance wrong. And probably the biggest takeaway: It’s not the technology. It’s the people system around it. If you’re leading engineers, running complex projects, or trying to move faster inside a system that keeps slowing you down, this one will feel very familiar. Episode Highlights 00:00 Why canceling missions enables risk 06:40 How organizations drift toward safety 12:05 Constraints vs resources 18:20 Why adding people slows you down 24:10 Getting the right people in the right roles 29:30 Attacking ideas not people 34:45 The real reason projects fail Key Takeaways Constraints drive innovation more than resources ever will. Adding people to a late project usually makes it later. Most failures are people problems, not technical ones. You can’t turn every leader into every type of leader. If ideas aren’t being challenged, you’re not moving fast enough. Dr. Thomas Zurbuchen LinkedIn: https://www.linkedin.com/in/zurbuchen/ Website thomaszurbuchen.com federationspeakers.com Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Most people ask what makes SpaceX different. It's a fair question. But the answer isn't what most people expect. In this solo episode, Matt breaks down the two qualities that separate organizations that thrive in chaos from the ones that get buried by it — and why most teams are unknowingly doing both of these things wrong. The trigger was Jared Isaacman's changes to the Artemis program and a framing that came out of the Off Nominal podcast: nobody said they were the constraint. So Isaacman said, fine — let's go faster and find out who is. That's not just a NASA story. That's a story about how high-performing teams actually work. The first quality is being willing to push people hard enough that they fail. Not because failure is the goal, but because failure is the only way to find the constraint. If everyone's comfortable, you don't actually know what's holding the team back. You just think you do. The second quality is what happens next. Once you find the constraint, you have to disregard hierarchy and throw whatever resources are required at that one thing. Because by definition, fixing it raises the ceiling for the entire system. Then you find the next one and do it again. This is what founder mode actually looks like in practice. Not chaos. Not ignoring process. It's knowing what the constraint is at all times, and having the authority and willingness to go solve it personally. There's also a piece here on trust that Matt keeps coming back to. You can't push a team to failure in an environment where people are afraid to admit they're failing. The job isn't to make people comfortable. It's to make them comfortable being uncomfortable. If you're trying to figure out why your team keeps hitting the same ceiling, this episode is probably going to feel very familiar. Key Takeaways You can't find the constraint if you never push the system past its limits. Trust isn't about comfort — it's about making people comfortable with discomfort. Once you find the constraint, hierarchy stops mattering. Resources go there, full stop. The difference between what's impossible for a director and easy for a VP is just authority, not complexity. Every high-performing team is doing these two things: finding constraints and eliminating them, over and over.
Most engineers don’t start their careers thinking, “I can’t wait to manage people.” They want to build things. Tinker. Solve hard problems. See hardware fly. In this episode, Brian Ippolito from Marotta Controls talks about what it’s been like to grow inside a third-generation aerospace company that grew from about 130 people to nearly 1,000 during his career. We talk about the moment you stop being someone’s peer and become their manager, and how uncomfortable that shift can be. Brian shares what actually changes when you move from leading a team to leading leaders, and why simple advice like “hit the forward button more” is harder to put into practice than it sounds. He also explains the very real “Bob from Valves” problem in manufacturing. When critical knowledge lives in one person’s head, it feels efficient until it becomes a risk. That’s part of the reason they built “Valve Camp,” an onboarding program that brings engineers, technicians, and even HR closer to the product so everyone understands the mission. Throughout the conversation, Brian reflects on how Marotta has kept its family-company culture while competing in aerospace and defense for more than 80 years, building hardware that has flown from the Apollo era to today’s heavy-lift rockets. If you are an engineer moving into management, leading technical teams, or trying to scale without losing what makes your company special, this episode is for you. Marotta Controls continues to grow across engineering, manufacturing, and support roles. If you want to work on aerospace systems that go from design to flight, take a look at their open positions. Episode Highlights 00:00 From engineer to leader inside a growing aerospace company 07:45 The “buddy to boss” transition 11:30 Why delegation feels uncomfortable at first 14:42 Finding purpose when you stop doing the hands-on work 19:19 The “Bob from Valves” problem 24:40 Why documenting the “why” matters more than the “how” 27:13 Valve Camp and building technical talent from day one Key Takeaways Delegation is a multi-year transition, not a flip of a switch. Technical leaders still need a way to “scratch the itch”, just maybe not at work. Tribal knowledge should constantly be converted into shared knowledge. Training isn’t overhead. It’s leverage. Culture compounds the same way leadership does. Brian Ippolito LinkedIn: linkedin.com/in/brian-ippolitto-62325029 Marotta Controls: https://marotta.com/ Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
Managing people is still the hardest problem in business. We’ve built rockets, nuclear reactors, and AI systems… but getting humans to coordinate? Still unsolved. In this episode, Casey Handmer talks about what leadership actually looks like when real stakes are involved when families depend on payroll, when bad decisions compound, and when “being liked” can quietly kill performance. He shares what he’s learned building Terraform Industries, why most management books aren’t that useful, and why firsthand accounts from people like General Groves hit differently. This conversation gets into hard feedback, demanding standards, and first principles thinking and why leaders need the social permission to push people without becoming jerks. If you care about building things that actually work, this one’s for you. If you enjoyed this episode, subscribe to the show and share it with one person who’s building something hard. That’s how this grows. Terraform Industries is hiring across multiple technical roles. If you want to work on synthetic fuels, energy, and real world hardware problems, check out their website for open positions. Episode Highlights 00:00 Why management is still humanity’s unsolved problem 08:53 Managing people is kind of the perennial problem 15:06 Coaching high performers even when they’re better than you 18:13 “Being liked is optional. Succeeding is mandatory.” 21:39 How to argue hard without attacking the person 23:30 Why most teams don’t practice real first principles thinking 28:18 What makes outlier companies different 34:09 The power of simply being present as a leader 38:10 Terraform’s next milestones Takeaways Coordination is the real bottleneck in big problems. Avoiding short term discomfort creates long term damage. First principles thinking requires structure, not slogans. Coaching isn’t optional even for top talent. Leadership compounds over time. Small edges add up. If this conversation resonated with you, make sure you’re subscribed and send it to someone who needs to hear it. Terraform Industries is actively hiring engineers and operators who want to work on synthetic fuel, methanol production, and large scale energy systems. Learn more at their official site. Casey Handmer Website: https://www.caseyhandmer.com/ X / Twitter: linkedin.com/in/casey-handmer-60183262 LinkedIn: linkedin.com/in/casey-handmer-60183262 Terraform Industries: https://terraformindustries.com/ Matt Gjertsen Website: https://www.bettereverydaystudios.com/ LinkedIn: https://www.linkedin.com/in/matthewgjertsen/ YouTube: https://www.youtube.com/@BetterEveryDayStudios
In this episode, Matt Gjertsen shares practical advice for managers on how to set clear expectations for their teams. Drawing from his experience as a former Air Force instructor pilot and talent development leader at SpaceX, he introduces the concept of "commander's intent," a military technique for effective delegation and communication. The episode breaks down the three essentials for communicating tasks: context (explaining the purpose and impact), outcome (defining what success looks like), and constraints (clarifying timelines, resources, and check-in points). Listeners will learn how these steps help ensure team members understand what is expected of them at work, leading to better engagement and performance.
In this episode of Leadership Launchpad, Matt Gjertsen shares practical strategies for developing talent within teams. Drawing on his military experience, Matt Gjertsen explains why building talent internally is often more effective than hiring externally. He emphasizes the importance of employee development in driving engagement and productivity, referencing Gallup research on workplace engagement. Matt introduces three simple questions leaders can use in one-on-one conversations to support employee growth: identifying one thing to improve, choosing an action to develop that skill, and setting a follow-up date. The episode offers actionable advice for managers looking to foster both team improvement and engagement.
