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!
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.
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!
Reminds me of “The Goal”.
I also had to immediately think of the theory of constraints 😁
Improvement that do not impact the whole process are not improvements. They create new bottlenecks. The Goal and the phoenix project
You know that. I know that. Why do _they_ act like they don’t know that?
What a great analogy.
This reminds me of a saying."end to end is always farther than you think".
I thought immediately of Goldratt as well when I saw this post.
The first idea that pops after reading: you REALLY have to know what you're doing to introduce parallelism/concurrency smartly.
One of the best introductions to Systems Thinking that I've read.
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.
Thanks for the great analogy. That’s why I like working in pull-based systems, like Kanban.
Queueing theory FTW. I wrote a story about this phenomenon.
https://open.substack.com/pub/thepolarisflowdispatch/p/the-entrepreneur-and-the-queueing?r=fjllf&utm_medium=ios
Maybe the answer is to add fun animatronics to the line like an ammusement bark. Cheaper way to solve the complaining than another oven. :)
A very good example of the futility of locally improving the steps that are not the constraint!
"The PYP System." Good term for the lexicon.