[klenwell]

That's an interesting idea. I picked up this book, Principles of Product Development Flow, based on some recommendations I think I came across here on HN:

https://www.goodreads.com/book/show/6278270-the-principles-o...

Reinertsen really helps you appreciate the costs associated with queues (of which the TODO list would be a common form) and this seems consistent with the principles he advocates.

One key quote related to this that I am still trying to wrap my head around:

Few product developers are aware of the causal links between high capacity-utilization, queues, and poor economic performance. Instead, developers assume that their cycle times will be faster when resources are fully utilized. In reality, as we shall see later, high levels of capacity utilization are actually a primary cause of long cycle time.

[TeMPOraL]

> In reality, as we shall see later, high levels of capacity utilization are actually a primary cause of long cycle time.

So what's the reason explained by the book?

(My guess would be something along the lines of: high level of utilization lead to sudden peaks in load exceeding available capacity, and thus throwing a wrench in the process as you scramble to add capacity.)

[jwhitlark]

100% use of nearly anything is over use, not just because of peaks in load, but because it must both be done and perfect.

Think of a bookcase. 100% means you can never add more books, and it also makes it very difficult to reorganize anything.