Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Kevin Goldsmith. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Kevin Goldsmith or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

The Right Amount of Process: Finding the Balance Between Chaos and Bureaucracy

44:38
 
Share
 

Manage episode 525379517 series 3548342
Content provided by Kevin Goldsmith. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Kevin Goldsmith or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

In this episode of It Depends: Lessons in Technology Leadership, Kevin Goldsmith tackles one of the most contentious topics in growing companies: process. Drawing on decades of leadership experience from IBM and Microsoft to Spotify and Adobe, he explores why process is neither inherently good nor bad; it's a tool that must fit the problem you're solving.

Kevin introduces a practical framework for deciding when to add process and when you have too much. He explains how to identify the coordination problems you're actually trying to solve and find the lightest-weight solution, rather than copying what works at Google or Amazon. The episode covers the warning signs of too little process (chaos, rework, unclear accountability) versus too much (bottlenecks, loss of autonomy, slow decisions), and why the size and culture of your organization fundamentally changes what works.

Through real examples from his career, Kevin addresses common scenarios leaders face: the scrappy startup founder who resists process until the org becomes dysfunctional, the experienced big-company hire who imports heavy processes that crush a smaller team, and the risk-averse leader who adds gates after every incident. He explains the critical difference between enabling process (which helps teams move faster with confidence) and controlling process (which centralizes decisions and kills speed), and why involving your teams in process design dramatically increases adoption.

Whether you're an engineering leader wondering if you're choking your team, a founder trying to scale without losing your speed, or a manager navigating the tension between autonomy and coordination, this episode gives you a strategic lens for making better decisions about when and how to add process, and when to remove it.

  continue reading

52 episodes

Artwork
iconShare
 
Manage episode 525379517 series 3548342
Content provided by Kevin Goldsmith. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Kevin Goldsmith or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

In this episode of It Depends: Lessons in Technology Leadership, Kevin Goldsmith tackles one of the most contentious topics in growing companies: process. Drawing on decades of leadership experience from IBM and Microsoft to Spotify and Adobe, he explores why process is neither inherently good nor bad; it's a tool that must fit the problem you're solving.

Kevin introduces a practical framework for deciding when to add process and when you have too much. He explains how to identify the coordination problems you're actually trying to solve and find the lightest-weight solution, rather than copying what works at Google or Amazon. The episode covers the warning signs of too little process (chaos, rework, unclear accountability) versus too much (bottlenecks, loss of autonomy, slow decisions), and why the size and culture of your organization fundamentally changes what works.

Through real examples from his career, Kevin addresses common scenarios leaders face: the scrappy startup founder who resists process until the org becomes dysfunctional, the experienced big-company hire who imports heavy processes that crush a smaller team, and the risk-averse leader who adds gates after every incident. He explains the critical difference between enabling process (which helps teams move faster with confidence) and controlling process (which centralizes decisions and kills speed), and why involving your teams in process design dramatically increases adoption.

Whether you're an engineering leader wondering if you're choking your team, a founder trying to scale without losing your speed, or a manager navigating the tension between autonomy and coordination, this episode gives you a strategic lens for making better decisions about when and how to add process, and when to remove it.

  continue reading

52 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play