Why a backlog never sits still, and why it is hard to escape

A backlog is not a quiet pile waiting until you have time. According to the source, it grows by itself, it creates new work that eats the hours meant for clearing it, and anything in it that is only half finished counts as if it was never done.

A backlog is a process, not a state

A backlog is everything that has piled up and not been done: quotes not sent, replies not written, jobs still waiting. The source opens with a warning. Hidden inside a backlog is an effect most people never suspect, and it is strong enough to crash the results of a whole area while everyone in it is working flat out.

For the definition itself, the source borrows from the dictionary rather than writing its own: an increasing accumulation of work not done and material nobody processed. The word that matters is increasing. A backlog does not stay the size it was born at.

Suppose a business owner has seven quotes that have not gone out yet. A month later there are fourteen, because some customers got in touch again. He did not get more work. The backlog simply doubled itself.

Half-done is worth zero

The source separates two kinds of backlog: things not done, and things only half done. Then it puts them at the same weight: “HALF-DONES are as bad as NOT-DONES.” Its reason is that they break an area up, bit by bit, until it turns into a swamp.

The picture it chooses is a car factory. Imagine a plant in Detroit that started turning out half-cars. All the materials would be used up, all the hours would be spent, and everyone would look extremely busy. And at the end of the day, not one car would roll out of the gate.

That is exactly what happens in a business with ten things stuck in the middle. The money and the time are already gone, and there is no product you can hand over.

The problem the source points to is that in your business, half-done work does not look like half a car. It looks like a confident answer: yes, I handled it. The source gives the case of a lawsuit someone reported as handled, and the case was lost, because the papers were only partly prepared and partly filed.

Suppose a studio owner has eight projects, each one nearly finished. Revenue from all of them combined is zero, because none of them has been delivered to a client.

Now the opposite. The same studio owner finishes two of them all the way, before she touches the rest. Two payments come in, and suddenly she has room to breathe.

Or a business owner who sends an application to a government office and forgets one attachment. As far as he is concerned, it is filed. Two months later it is rejected, and the whole process starts again from the beginning.

The backlog makes the work that blocks it

Here is the mechanism the source marks as the key point of the chapter, and it starts with a single sentence: “No backlog ever quietly lies there.”

As long as someone else depends on what has not been done, there is pressure on whoever is behind. The customer calls, the supplier asks, the partner reminds. So an area that falls behind starts producing new work, and that work has nothing to do with shrinking the backlog itself.

The source's example is an insurance company that falls behind on paying claims. A flood of queries arrives asking why. The claims department spends its time answering those queries instead of paying claims. The workload doubles and triples, and not a single claim gets paid.

Suppose a business owner is two weeks behind on email. Half of what lands in her inbox now is people checking that she got their last message. Or an installer who is behind on jobs, where calls from customers asking when he will show up take exactly the hours he could have used to show up.

That is why you cannot seem to get out from under a backlog. It produces the very work that stops you from reducing it. Another hour of effort does not fix that, because the hour goes to the follow-ups.

Why it looks like so much work

According to the source, the storm of activity you see in an area like this exists precisely because it never handled things in the first place. Whatever was not handled comes back as new traffic. From outside it looks like a heavy load, and from inside it feels like hard work. In practice, most of it is another lap around the same things.

The answer the source gives is not clever. What is interesting about it is the result it names: not that the area becomes fast or efficient, but that it becomes calm. And only once it is calm does real production happen there.

What the booklet has on this

The chapter this article is based on includes two exercises: the sort, and the immediate quiet. It also has a self-check, and it belongs to a booklet that gives a name to each of the things that eat your day.

If you are running all day and still cannot close what is open, it is worth checking how much of your day goes to the backlog itself, and how much goes to the questions it keeps creating.