15 Comments
Oct 18Liked by Kent Beck

My dad's classic phrase is "when we get caught up". 20+ years later he's still stressed about getting "caught up". This is exactly why it will never happen!

Expand full comment

Reminds me of “The Goal”.

Expand full comment

I also had to immediately think of the theory of constraints 😁

Expand full comment

Improvement that do not impact the whole process are not improvements. They create new bottlenecks. The Goal and the phoenix project

Expand full comment
author

You know that. I know that. Why do _they_ act like they don’t know that?

Expand full comment

What a great analogy.

This reminds me of a saying."end to end is always farther than you think".

Expand full comment

I thought immediately of Goldratt as well when I saw this post.

Expand full comment

The first idea that pops after reading: you REALLY have to know what you're doing to introduce parallelism/concurrency smartly.

Expand full comment

One of the best introductions to Systems Thinking that I've read.

Expand full comment

There's a few thoughts going round my head on this one, firstly, always look for the level of the system before optimising around bottlenecks and secondly, there is **always** a outer system populated by customers and maybe two within that, wants and needs.

Expand full comment

Thanks for the great analogy. That’s why I like working in pull-based systems, like Kanban.

Expand full comment

Maybe the answer is to add fun animatronics to the line like an ammusement bark. Cheaper way to solve the complaining than another oven. :)

Expand full comment

A very good example of the futility of locally improving the steps that are not the constraint!

Expand full comment

"The PYP System." Good term for the lexicon.

Expand full comment