2
The Strategic Power of the Takt Time Comparison 0:53 Jackson: You know, I love that bridge metaphor—it makes the physical reality of a bottleneck so clear. But if we want to move from just seeing a pile of inventory to actually measuring the impact, where do we start? I mean, every factory has some "traffic," right? How do we know which traffic jam is the one actually killing our bottom line?
1:14 Nia: That’s where we get into the math—but don't worry, it’s the good kind of math. We need to look at our actual cycle times and hold them up against something called Takt time. Have you heard that term tossed around in the plant?
1:26 Jackson: I have, yeah. It’s a German word, right? Like a musical beat or a pulse?
0:40 Nia: Precisely. It’s the heartbeat of your customer demand. If your customer needs 100 widgets a day and you have 400 minutes of production time, your Takt time is four minutes. Every four minutes, a finished product needs to roll off the line. Now, here is the secret for identifying a bottleneck using your spreadsheet: you look for any work center where the actual cycle time is higher than that Takt time.
1:54 Jackson: So, if my customer needs a part every four minutes, but my assembly station takes five minutes to finish its task—that station is officially a bottleneck.
2:04 Nia: You've hit the nail on the head. It doesn't matter how fast the rest of the line is. If assembly is at five minutes, your entire plant is at five minutes. You can have a cutting machine that takes thirty seconds—it’s just going to spend four and a half minutes waiting or, worse, making a giant pile of inventory that the assembly team can't touch yet.
2:23 Jackson: That sounds like a recipe for chaos. But wait, what if I look at my ERP data and I see a station that is "busy" 99% of the time? Isn't that a good thing? We usually want high utilization, don't we?
2:36 Nia: This is one of those paradigm constraints we have to break. In the Theory of Constraints, high utilization at a non-bottleneck is actually a liability. If a machine that isn't the constraint is running at 100%, all it’s doing is flooding the floor with Work in Progress. It’s creating that traffic jam we talked about. You only want the bottleneck running at 100%. Everything else should actually have some idle time.
2:59 Jackson: That feels so counter-intuitive. I can imagine a manager walking the floor, seeing a machine sitting idle, and losing their mind.
3:07 Nia: Oh, absolutely. It’s a huge cultural shift. But think about it—if you force that non-bottleneck to stay busy, you’re just spending money on raw materials and labor to create inventory that isn't selling yet. That’s money tied up in a pile of metal on the floor instead of sitting in the bank. According to throughput accounting, which was popularized by Eliyahu Goldratt in "The Goal," inventory is a liability, not an asset.
3:31 Jackson: So, to identify the real constraint, I shouldn't just look for who is busy—I should look for whose cycle time is exceeding that customer pulse, the Takt time.
3:41 Nia: Exactly. And you can do this today. Just export your work center logs to a spreadsheet. Calculate the average time it takes to complete an order at each station. Then, calculate your Takt time based on your current orders. If any station’s time is higher than Takt, you’ve found your primary constraint. It’s the most intellectually rigorous way to start because it’s based on the reality of your customer’s needs, not just a "feeling" that a certain area is slow.
4:04 Jackson: And once we have that data, we can start asking why. I’m thinking about that "Five Whys" technique you mentioned earlier. It’s not just about knowing the machine is slow—it’s about finding out if it’s the machine, the person, or maybe even a bad policy.
4:20 Nia: Right! And sometimes it’s even a "market constraint" where the factory is fine, but there aren't enough orders. But for most of us, the problem is right there on the floor, hidden in those cycle time numbers. By comparing cycle time to Takt time, you move from reactive firefighting to strategic optimization. It gives you a target. You aren't trying to make everything faster—you’re only trying to get that one specific station under the Takt time. Everything else is a distraction.