Every system, no matter how optimized, has a constraint—the point in the system that has the lowest throughput. But do you know where yours is? And what are you doing about it?
Knowing your constraint means knowing where you can make meaningful improvements to your system. Because if you make improvements to the wrong part of the system, you could actually make your flow worse (*cough, cough* hiring more developers when they're not the actual source of the bottleneck).
In this episode, learn why you should know where your system's constraint is, how you can find it, and what options you have with what to do with it.