Bottleneck blindness

In my previous job, my team automated software processes. One of our processes kept breaking down and consumed a large chunk of our time. We tried rewriting the code, increasing response time and adding more checks, but to no avail. Every couple of days, the process would break down and deprive our heads of a few clumps of hair.

We finally figured out that the process was running on an old computer with poor hardware. This rendered any software that ran on the machine unstable. The moment we shifted the process to another computer, our problems vanished. The bottleneck in the process wasn’t the software code that we tried so hard to fix, but the underlying infrastructure.

To optimize a process, it is obvious that the effort must be directed at its bottleneck. The less obvious corollary is that any amount of improvement to a process outside its bottleneck is wasted effort.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s