<a href="/en/Improvements%20other%20than%20identifying%20and%20eliminating%20bottlenecks%20are%20futile.">Improvements other than identifying and eliminating bottlenecks are futile.</a>
<ul>
<li>Maybe that&#39;s too much?</li>
<li>True for systems where the <a href="/en/flow%20metaphor">flow metaphor</a> is valid<ul>
<li>It cannot be said to be True because there is no guarantee that the flow metaphor is valid for all systems in the world.</li>
</ul>
</li>
</ul>
<a href="/en/Identify%20and%20eliminate%20bottlenecks">Identify and eliminate bottlenecks</a>
<a href="/en/Identifying%20Bottlenecks">Identifying Bottlenecks</a>
<ul>
<li><a href="/en/First%2C%20identify%20the%20bottleneck.">First, identify the bottleneck.</a></li>
<li><a href="/en/bottleneck">bottleneck</a>
<a href="/en/Identify">Identify</a></li>
</ul>
<hr>
This page is auto-translated from <a href="https://scrapbox.io/nishio/%E3%83%9C%E3%83%88%E3%83%AB%E3%83%8D%E3%83%83%E3%82%AF%E3%82%92%E7%89%B9%E5%AE%9A">/nishio/ボトルネックを特定</a> 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 <a href="https://twitter.com/nishio_en">@nishio_en</a>. I&#39;m very happy to spread my thought to non-Japanese readers.

Identify bottlenecks