Bottlenecks

Bottlenecks are key in optimizing systems - the Theory of Constraints

Think about say a milk bottling factory.

If there is one machine for the entire plant that puts caps on bottles and can only do 6 bottles every minute.

Then the maximum output for the system will 6 bottles a minute.

You can improve other parts of the factory but it will never produce more than 6 bottles a minute if the speed of the capping machine is not improved.

The machine is the ‘constraint’ or ‘bottleneck’ for the entire system.

This is one of the most important ideas from the theory of constraints. If only one factor limits a system at a given time, then the only worthwhile thing to do is to fix it.

Effort expended fixing things which are not the most significant bottleneck will give negligible benefit until the biggest bottleneck is solved.

Don’t waste your time. Find and eliminate the largest bottleneck first.

What’s really cool about this is you have the power of compounding efficiencies.

Each bottleneck you eliminate results in increasing the speed of the process by a percentage every time.

Combine these together and they compound over time to add up to a huge difference.

This is where the magic of compound interest comes into place. You can see this visually in the following spreadsheet:https://docs.google.com/spreadsheets/d/1mx506x85EnP6btixveJW_4QFLGxqDWnMP8Xnlkcj7Bk/edit?usp=sharing

Your growth is limited by the speed at which you can identify and fix each bottleneck in sequence.

From this we can conclude:

You only need to focus on the biggest bottleneck, and solve it first. With many things to think about at a given time, it makes things much easier to prioritize and manage.

Think about what companies often do instead.

We run around trying to fix everything, all at once. The theory of constraints tells us that all we need to do is get really good at identifying the biggest bottleneck and solving that.

After you solve the first bottleneck, find the next biggest one and solve that, rinse-repeat

It makes sense when you think about it.

If you know of a bottleneck and you can fix it, then chances are you will just go ahead and fix it if you can.

The bottlenecks which don’t get fixed as easily are when the people who can see the bottleneck are not in a position to fix it.

For instance one of the biggest bottlenecks in our support process is licensing inquiries. To fix that means building a new licensing system which is really more of an action for development.

So good management is as simple as having an open dialog to find out where the real bottlenecks are and getting those fixed.

Next:https://interfaceware.atlassian.net/wiki/spaces/EC/pages/2713059688