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.

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

• 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.

LinkedIn: https://www.linkedin.com/in/zurbuchen/

Website

• thomaszurbuchen.com
• federationspeakers.com

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

1. You can't find the constraint if you never push the system past its limits.
2. Trust isn't about comfort — it's about making people comfortable with discomfort.
3. Once you find the constraint, hierarchy stops mattering. Resources go there, full stop.
4. The difference between what's impossible for a director and easy for a VP is just authority, not complexity.
5. 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.

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

1. Delegation is a multi-year transition, not a flip of a switch.
2. Technical leaders still need a way to “scratch the itch”, just maybe not at work.
3. Tribal knowledge should constantly be converted into shared knowledge.
4. Training isn’t overhead. It’s leverage.
5. Culture compounds the same way leadership does.

Brian Ippolito

1. LinkedIn: linkedin.com/in/brian-ippolitto-62325029
2. Marotta Controls: https://marotta.com/

Matt Gjertsen

1. Website: https://www.bettereverydaystudios.com/
2. LinkedIn: https://www.linkedin.com/in/matthewgjertsen/
3. 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

1. Coordination is the real bottleneck in big problems.
2. Avoiding short term discomfort creates long term damage.
3. First principles thinking requires structure, not slogans.
4. Coaching isn’t optional even for top talent.
5. 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

1. Website: https://www.caseyhandmer.com/
2. X / Twitter: linkedin.com/in/casey-handmer-60183262
3. LinkedIn: linkedin.com/in/casey-handmer-60183262
4. Terraform Industries: https://terraformindustries.com/

Matt Gjertsen

1. Website: https://www.bettereverydaystudios.com/
2. LinkedIn: https://www.linkedin.com/in/matthewgjertsen/
3. 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.