Mostrando entradas con la etiqueta theory of constraints. Mostrar todas las entradas
Mostrando entradas con la etiqueta theory of constraints. Mostrar todas las entradas

viernes, 27 de febrero de 2026

Bottlenecks Theory vs. Theory of Constraints: Are They the Same Thing?


If you’ve spent any time around operations or supply chain teams, you’ve probably heard someone say, “We need to fix the bottleneck.”

And they’re not wrong.

But here’s where things get interesting: fixing a bottleneck isn’t the same thing as applying the Theory of Constraints (TOC) even though the two ideas are closely related.

We have already spoken about Theory of Constraints in this blog:


But it is worth explaining in detail the differences between Bottlenecks Theory and Theory of Constraints, but first: What’s a Bottleneck?

A bottleneck is simply the slowest step in a process, the part that limits how much your system can produce.

Imagine this:

  • Production can make 1,000 units per day
  • Packaging can only handle 600 units per day
Packaging is the bottleneck. It doesn’t matter how fast production runs, your total output is capped at 600 units.

Bottleneck theory focuses on identifying that slow step and improving it.

You might add labor, reduce downtime, upgrade equipment etc. The goal is to increase flow by fixing the slowest point.

Now: What Is Theory of Constraints (TOC)?

The Theory of Constraints, developed by Eliyahu M. Goldratt, takes this idea much further.

TOC says: Every system has one constraint that determines its overall performance, and here’s the key that constraint isn’t always a machine, it could be a policy, a forecasting method, a batch size rule etc.

TOC isn’t just about finding the slow step. It’s about managing the entire organization around whatever is currently limiting throughput and profit.

For example, imagine you increase manufacturing capacity, but sales can’t sell more product. The constraint was never production. It was demand.

Optimizing production in that case just creates more inventory.

TOC forces you to look at the whole system before investing time and money.
 
Fixing bottlenecks is good operations management, managing constraints is smart business strategy. One improves a step. The other improves the system, and in today’s volatile supply chain environment, systems thinking wins.





 

domingo, 10 de septiembre de 2017

Just in time

Just-in-time manufacturing (JIT) also known as the Toyota Production System is a methodology aimed at reducing flow times within production systems as well as response times from suppliers and to customers.

It originated in Japan in the 1960s and 1970s, but the wise use of the term JIT faded in the 1990s as the new term “lean manufacturing” was established as a more recent name for JIT.

Benefits:

- Lower warehouse costs. Since less space is needed, this reduces the amount of storage an organisation needs to buy or rent.

- Less amount of inventory obsolescence, when companies use the traditional method of inventory they can end up with pallets of unsold items that simply go to waste

- Defect rates are reduced resulting in less waste and greater customer satisfaction.


Risks:


- You become reliant on your suppliers. Suppliers need to be able to supply materials quickly with very limited advance notice and any unexpected even can derive in long term out of stocks.

- Employees are at risk of precarious work as employers seek to easily adjust their workforce in response to supply and demand conditions by increasing the amount of contracting and temporary work.

- By not carrying much of stock, the risk of out of stocks is higher making imperative to have the correct procedures in place to ensure stock can become readily available.

- More and better planning is required to ensure stock is available at all times

If you want to learn more, check out the video below that explains in detail what JIT is and all the elements around this philosophy. 




Couldn´t finish this post without some music. Happy week!





domingo, 12 de febrero de 2017

Logistionary; Drum-Buffer-Rope


Drum Buffer Rope (DBR) is a planning and scheduling solution derived from the Theory of Constraints (ToC).

The fundamental assumption of DBR is that within any plant there is one or a limited number of scarce resources which control the overall output of that plant. This is the “drum”, which sets the pace for all other resources. In order to maximize the output of the system, planning and execution behaviors are focused on exploiting the drum, protecting it against disruption through the use of “time buffers”, and synchronizing or subordinating all other resources and decisions to the activity of the drum through a mechanism that is akin to a “rope”.

Theory of Constraints uses a 5 step process, called a ‘Process Of On-Going Improvement’ (POOGI), to improve any system. These steps are called the 5 Focusing Steps:

- Step 1. Identify the system’s constraint(s), the drum

- Step 2. Exploit the System’s Constraint(s). 

- Step 3. Subordinate everything else to the above decisions. 

- Step 4. Elevate the constraint(s). Basically improve the performance of the drum

- Step 5. If in the previous steps a constraint has been removed, go back to step 1 and identify the new bottleneck


The Boy Scout example in The Goal (I already wrote a post long time ago about one of my favorite books!)

A very illustrative example was how the protagonist of the book manages a boy scout outing, especially how to keep the group together while different boys walked at different speeds. The solution was to put the slowest boy scout Herbie at the front, and prohibiting all others from overtaking him. Additionally, he lightens Herbie’s backpack so that he can walk faster.