- [Resource Efficiency and Flow Efficiency
-
Pointing out that there are two ways to refer to the word “efficiency.”
-
I think the diagram is a little confusing.
-
What is called resource efficiency here corresponds to the utilization rate of factory machinery in constraint theory. - When you think about batch size, if you think only about resource efficiency when it is cheaper to make a large batch, you will end up saying, “Let’s make the largest batch at the lowest cost.
- The larger the batch size, the more time it takes to get the materials into the factory machinery and out of the factory machine where they are made, but that is often overlooked
-
Flow efficiency corresponds to shorter lead time
-
He explains that both of these two as “what the word efficiency can refer to” can easily be a trade-off.
- In learning-oriented management, shorter lead times are preferred because they directly increase the amount of learning.
-
To reduce batch size
- Do only what you need to do.
- In software, it’s called YAGNI or something like that.
- lean cycle
- Pointing out that the thought process is the opposite of an arrow.
-
Tends to make the constraint of a release date a given
- The result is a change in mindset to one that emphasizes resource efficiency.
- Make this constraint moveable.
-
Methods, practices, and methodologies to improve flow efficiency - pair programming reduces flow and increases quality - The amount of work per unit of time is halved, but the resource efficiency is more than halved because of the increase in quality. - If two people are doing the implementation and code review to maintain quality, the lead time is reduced because it only needs to be done once, and flow efficiency is increased. - As a side effect, knowledge sharing occurs and the frequency of “waiting for processing because the person who can do it is buried” is reduced, which increases both resource efficiency and flow efficiency.
-
If flow efficiency (reducing the amount of flow) is increased, the number of people on the line waiting for tasks to be completed will increase, and people who do nothing will be created. (Resource efficiency deteriorates).
-
Increasing resource efficiency (increasing flow volume) will increase human tasks on the line and lead time will increase. (Flow efficiency deteriorates)
-
relevance - Efficiently handling tasks would implement a fast fucking application.
This page is auto-translated from /nishio/リソース効率性とフロー効率性 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.