A few years ago, I read a famous novel in the manufacturing world — The Goal by Eliyahu Goldratt. The story follows a factory manager who tries to improve efficiency by running every machine at full speed. The result was the opposite: piles of unfinished products filled the warehouse, and deliveries were still delayed.

This book highlights a simple but often overlooked truth — local efficiency doesn’t equal overall efficiency.

1. The bottleneck determines the whole system
In a factory, production speed is not defined by the fastest machine, but by the slowest one. The same happens in an office: project progress often gets stuck because “a document hasn’t been submitted” or “a manager hasn’t reviewed it yet,” not because people aren’t working hard enough.

2. Improving non-bottlenecks is meaningless
Speeding up the front end without fixing the bottleneck only pushes more work downstream and increases pressure. Similarly, finishing a presentation faster doesn’t help if your manager won’t review it until three days later.

3. System flow matters more than individual speed
The real goal of lean thinking is to let work flow smoothly from start to finish, not to keep everyone busy all the time. Instead of chasing individual performance, focus on whether the project as a whole can move smoothly and be delivered on time.

My observations

Working in U.S. factories, I often see teams get distracted by performance targets: some departments try to keep machines running at full load, which only leads to excess inventory; some design teams rush to issue drawings, even when the production floor is already overloaded. When optimization doesn’t revolve around the bottleneck, it only pushes problems downstream faster.

This becomes even more obvious when companies start automation. Many teams begin with the “easiest part to automate,” but that often amplifies the chaos. Real value comes from understanding the entire process, identifying the slowest step, and prioritizing automation where it truly matters.

It’s been forty years since The Goal was published, but I still see its warning every day: If you improve in the wrong direction, speed means nothing. Find the right bottleneck, and the whole system begins to flow.

幾年前我讀到一本在製造業很有名的小說《The Goal》。主角是一位工廠廠長，為了提升效率，他讓每台機器全速運轉。結果卻更糟：半成品堆滿倉庫、交期延誤。這本書提醒我們一個簡單的道理 — 局部效率，不等於整體效率。

1. 瓶頸決定整體
在工廠裡，產出速度不是看最快的機器，而是看最慢的那一台。在辦公室裡也是如此：專案進度往往卡在「那份資料還沒交」、「主管還沒批」的環節，而不是誰最努力。

2. 改善非瓶頸沒有意義
若加快前端流程，卻沒處理瓶頸，只會把更多半成品推向後端，造成更大壓力。同樣地，簡報做再快、主管三天後才回來看，專案仍不會更快。

3. 整體流動比局部速度更重要
精實思維真正的目標，是讓工作能「順暢地從頭走到尾」，而非讓每個人都看似忙碌。與其各自衝績效，不如專注在「專案能否順暢並按時交付」。

我的觀察

在美國工廠，我常看到績效讓團隊跑偏：有的部門為了讓機器滿載，結果庫存爆量；有的設計團隊急著出圖，卻忽視生產端已經超載。如果優化沒有圍繞瓶頸，只是更快地把問題推向下游。

這在自動化導入時更明顯。許多公司直覺從「最容易自動化」的地方下手，結果放大混亂。真正的價值，是先看清整體流程，找到「最慢的一站」，再決定自動化的優先順序。

《The Goal》出版四十年了，但我每天仍在現場看到它的警示：找錯方向，再快都沒用；找對瓶頸，整體才會真正流動起來。