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