Critical Chain

02The Hidden Trap of Safety Time

We all love a good safety net, especially when our professional reputation is on the line. When your boss walks up to your desk and asks how long it will take to write a specific report or design a new piece of software, what goes through your mind? If you are like most people, you perform a rapid mental calculation. You know that if absolutely everything goes perfectly, you could probably finish the task in five days. But you also know that things never go perfectly. The server might crash, you might get pulled into endless meetings, or you might hit an unexpected technical roadblock. So, to protect yourself, you add a comfortable margin of safety. You look your boss in the eye and say, "It will take me ten days." This behavior is completely rational and happens at every single level of a project. The programmer pads their estimate, the team lead adds a few days to the programmer's estimate just to be safe, the project manager adds a week to the team lead's estimate, and the executive adds a month before presenting it to the client. By the time the project schedule is finalized, it is absolutely bloated with safety time. Theoretically, with all this hidden padding, projects should be finishing weeks or even months ahead of schedule. Yet, paradoxically, they still finish late. Where does all that safety time go? In Critical Chain, Goldratt explains this mystery by introducing us to two fundamental phenomena of human behavior: Student Syndrome and Parkinson’s Law. These are the silent killers of project schedules, and they are directly fueled by the very safety time we add to protect ourselves. Let us start with Student Syndrome. Think back to your school days. If a professor gave you an assignment and told you it was due in two weeks, did you rush home and start working on it that very night? Of course not. You knew you had plenty of time. You relaxed, hung out with friends, and focused on other things. It was only when the deadline was looming just a few days away that the panic set in, and you finally started working frantically. This is human nature. When we know we have protective safety time built into our schedule, we naturally delay the start of the actual work. We feel a false sense of security. In the corporate world, Student Syndrome happens every day. If you have ten days to do a five-day task, you will likely spend the first five days catching up on emails, attending low-priority meetings, or simply working at a leisurely pace. You do not feel the urgency to sprint. But here is the catch: because you delayed the start of the intense work, you have effectively burned through all your safety time before you even encountered a problem. When you finally dive deep into the task on day six, and an unexpected technical issue pops up on day eight, you are suddenly behind schedule. The safety time that was supposed to protect you from the unknown was completely wasted at the beginning of the task. The second culprit is Parkinson’s Law, which states that work expands to fill the time available for its completion. If you are given ten days to complete a task, you will find a way to take ten days. Even if you finish the core work in five days, you will not immediately hand it in. Why? Because if you hand it in early, your boss will realize you padded your estimate. The next time you ask for ten days, they will say, "No, you did it in five last time, you only get five days." So, to protect your future safety time, you hold onto the work. You spend the remaining five days polishing it, tweaking minor details, or simply letting it sit on your desk. Furthermore, in many organizations, finishing early is not rewarded; it is actually penalized. If you finish your task early and pass it on to the next person in the chain, they probably are not ready for it anyway because they are busy working on something else. So the early finish provides absolutely no benefit to the overall project. But if you finish late, the delay is instantly passed on to the entire project schedule. Goldratt points out a devastating asymmetrical reality in traditional project management: delays are always accumulated and passed down the schedule, but early finishes are almost never capitalized upon. If Task A finishes three days early, Task B cannot start early because the person assigned to Task B is busy finishing another commitment. The three days gained are completely lost. However, if Task A finishes three days late, Task B is forced to start three days late, pushing the entire project timeline back. This creates a vicious cycle. Because projects are always late, management tries to crack down by arbitrarily cutting everyone's estimates by 20%. The workers, realizing management is going to cut their estimates, respond by inflating their initial estimates even further. It becomes a toxic game of corporate negotiation where the numbers lose all connection to reality. The schedule becomes a work of fiction, and the actual execution becomes a chaotic scramble. To break this curse, we have to fundamentally change how we view estimates and safety time. We have to realize that burying safety time inside individual tasks is the worst possible place to put it. It encourages bad habits, hides the true status of the project, and ultimately guarantees that the project will take the maximum amount of time possible. The solution is not to eliminate safety altogether—that would be a recipe for disaster in an uncertain world. The solution, as we will discover, is to extract that safety time from the shadows and place it where it can actually protect the entire project.

Continue reading with LeapAhead app

Full summary is waiting for you in the app

Continue reading