Week 18: Build Systems, Not Hero-Driven Organizations
建立系統，而不是建立靠英雄撐住的組織
Time: 5 minute video
Category: Organizational Design 組織設計
Some teams look strong because a few people keep rescuing the work. A discharge almost gets delayed, so someone jumps in. A form is missing, so someone runs across the hospital. A scheduling issue gets solved because one coordinator stays late. From the outside, it looks like good teamwork. But if the process only works because someone saves it at the end, the system is fragile. This week’s video helps leaders shift from hero-driven work to system-designed work. The goal is not to reduce commitment. The goal is to reduce dependence.
有些團隊看起來很強，是因為少數幾個人一直在拯救流程。病人差一點無法出院，所以有人跳出來處理。表單少了，所以有人跑去找人簽名。排程出問題，所以某位協調人員留下來加班。從外面看，這好像是好團隊合作。但如果流程每次都要靠最後有人出手拯救，這個系統其實很脆弱。本週影片幫助主管從「靠英雄撐住」轉向「靠系統設計」。目標不是降低大家的投入，而是減少組織對少數人的依賴。
English Version
中文版 (AI)
Summary of Video
Why does this matter for leaders at KFSYSCC?
In a hospital, many important processes depend on timing, clarity, handoffs, and follow-through. When the process is unclear, good people compensate. They call, remind, chase, check, and rescue. That may protect the patient in the moment. But over time, it creates hidden dependence on a few people. Strong leadership means noticing where work depends too much on personal rescue and redesigning the process so the next step is visible, reliable, and easier to do.
When would you use this?
Use this idea when:
the same problem keeps coming back
one or two people always know what to do, but others do not
staff frequently need verbal reminders to move work forward
information exists somewhere, but people still have to chase it
a process only works when a specific person is present
a team praises “good teamwork,” but the work actually required last-minute rescue
leaders want to reduce burnout without lowering standards
What are the key phrases from this video?
If it only works with rescue, it is fragile
Work is being pushed, not flowing
Dependence replaces design
Fix the cause, not the fire
Make the next step visible
Fast rescue is not system strength
Design reduces dependence
How would you describe this tool in 30 seconds?
A hero-driven system works only because certain people keep rescuing the process. A system-designed team asks a different question: not “Who can fix this?” but “Why does this keep needing to be fixed?” Leaders use that question to make the next step clearer, reduce manual follow-up, assign ownership to the process, and remove unnecessary dependence on specific individuals.
影片摘要
為什麼這對和信醫院的領導者很重要？
在醫院裡，很多重要流程都靠時間、清楚度、交接和後續追蹤來維持。當流程不清楚時，好人會補上。他們打電話、提醒、追蹤、查系統、救流程。這在當下可能保護了病人，但長期下來，組織會越來越依賴少數幾個人。好的領導，是看見工作在哪裡過度依賴人的救火，然後重新設計流程，讓下一步更看得見、更可靠、更容易執行。
什麼時候會用到這個工具？
以下情況很適合使用：
同一個問題一直重複出現
總是一兩個人知道怎麼處理，其他人不知道
工作常常需要靠口頭提醒才會往前走
資訊其實存在某個地方，但大家還是需要到處追
流程只有在某個特定的人在場時才跑得動
團隊說這是「好團隊合作」，但其實是最後一刻有人救火
主管想減少疲憊感，但不想降低標準
這支影片的關鍵句是什麼？
如果每次都要靠救火，系統就是脆弱的
工作是被推著走，不是自然流動
依賴取代了設計
處理原因，不只是撲滅火
讓下一步看得見
快速救火，不等於系統強
設計可以減少依賴
用 30 秒怎麼描述這個工具？
靠英雄撐住的系統，是因為某些人一直在拯救流程，所以事情才沒有掉下來。系統設計的團隊，會問另一個問題：不是「誰可以處理這個？」而是「為什麼這件事一直需要被處理？」主管用這個問題，把下一步變清楚，減少手動追蹤，把責任放在流程上，並降低對特定個人的依賴。
Scripts for Leaders
Keep these short. The goal is not to sound impressive. The goal is to make work easier, calmer, and clearer.
-
I appreciate how quickly everyone responded. But I want us to notice something. This only worked because someone rescued it at the end. Let’s look at the process, not blame the person.
-
Instead of asking who can fix this today, let’s ask why this keeps needing to be fixed. What step is unclear? What information is missing? Where does the work stop?
-
The next step should not depend on someone remembering. Can we make the status visible? Can we add one shared place where the team can see what is ready, waiting, or urgent?
-
If every case needs a phone call, the process is too dependent on memory and interruption. Let’s decide which situations truly need verbal follow-up and which ones can be handled through a clear status update.
-
I do not want this to depend only on one person. Who owns this step? What is the backup? And how will the team know when this step is complete?
-
I know you have been holding this together. Thank you. Now we need to make sure the system does not keep depending on you alone. Let’s redesign the work so it carries more of the load.
-
It may be faster today. But if the same person has to rescue it every time, it is not truly efficient. It is hidden dependence.
給主管的對話腳本
這些句子請盡量簡短。目標不是講得厲害，而是讓團隊把注意力放回真正重要的工作。
-
我很感謝大家這麼快把問題處理掉。但我也想請大家看見一件事。這次能順利結束，是因為最後有人跳出來救流程。我們要看流程，不是責怪人。
-
我們先不要只問：今天誰可以處理？我們要問：為什麼這件事一直需要被處理？是哪一步不清楚？是哪個資訊不見了？工作是卡在哪裡？
-
下一步不應該只靠某個人記得。我們能不能讓狀態看得見？能不能有一個共享的位置，讓團隊知道什麼已經完成、什麼還在等、什麼是緊急？
-
如果每一個個案都需要打電話追，這個流程就太依賴記憶和打斷了。我們要先決定，哪些狀況真的需要口頭追蹤，哪些可以用清楚的狀態更新來處理。
-
我不希望這件事只靠某一個人。這個步驟由誰負責？備援是誰？團隊怎麼知道這個步驟已經完成？
-
我知道你一直在把這件事撐住。謝謝你。但接下來，我們不能讓系統一直只靠你。我們要重新設計工作，讓流程本身多承擔一點。
-
今天看起來可能比較快。但如果每一次都要同一個人出來救，那不是真正的效率。那是隱藏的依賴.
Supporting Research
-
High reliability research is especially relevant to hospitals because healthcare is complex, high-risk work where small failures can have serious consequences. AHRQ describes high reliability organizations as operating in complex, high-hazard settings for long periods without serious accidents by cultivating teamwork, resilience, and reliable processes. This supports the leadership idea that safety and quality should not depend only on individual heroics. They need systems that make reliable work easier to repeat.
Lean healthcare research also supports the importance of standard work, visual management, and reducing waste in the flow of work. One healthcare Lean study notes that standardizing work processes can make the system less dependent on individuals. This connects directly to the Week 18 message: dependence should move from individual memory to clear process design.
Visual management is another practical tool. Healthcare workflow guidance emphasizes that flow requires a visual management system, especially when teams need to see status, reduce unnecessary handoffs, and avoid waiting for a person to provide missing information.
-
Systems do not remove the need for human judgment. Hospitals will always need experienced people who notice risk, respond to exceptions, and act quickly when something is urgent. The danger is not having capable people. The danger is building daily operations that only work when those people constantly compensate for weak design. A system can be over-standardized, too. Leaders still need judgment to distinguish between useful standardization and rigid rules that do not fit clinical reality.
-
At KFSYSCC, we want to honor people who step in during difficult moments. But we also want to learn from those moments. When the same rescue happens again and again, leaders should treat it as a signal. Something in the process may be unclear, invisible, delayed, or poorly owned. Our practical goal is simple: make the next step visible, reduce unnecessary interruption, and design work so knowledge moves through the process, not only through a few key people.
支持性研究
-
高可靠度組織的研究很適合用在醫療場域，因為醫療工作本來就是高複雜、高風險的工作，小小的失誤也可能造成嚴重後果。AHRQ 說明，高可靠度組織能在複雜、高危險的環境中長期運作，而不出現嚴重事故，關鍵在於團隊合作、韌性，以及可靠的流程。這支持本週的領導觀念：安全與品質不能只靠個人英雄式的努力，而需要能讓可靠工作被重複執行的系統。
精實醫療的研究也支持標準作業、視覺化管理，以及減少流程浪費的重要性。有一篇關於精實醫療與員工角色的研究指出，工作流程標準化可以讓系統比較不依賴特定個人。這與第 18 週的重點直接相關：組織應該讓依賴從個人的記憶，轉移到清楚的流程設計。
視覺化管理也是很實際的工具。醫療流程改善的指引指出，若要讓工作順暢流動，價值流程需要視覺化管理系統，特別是在團隊需要看見狀態、減少不必要交接、避免等待某個人補資訊的時候。 -
系統不能取代人的判斷。醫院永遠需要有經驗的人看見風險、處理例外、在緊急時快速反應。真正的問題不是有能力的人太多，而是日常運作太常需要這些人補上設計不足的地方。系統也可能被過度標準化。主管仍然需要判斷，分辨什麼是有幫助的標準化，什麼是不符合臨床現場的僵硬規則。
-
在和信，我們要肯定那些在困難時刻願意出手的人。但我們也要從這些時刻學習。當同樣的救火一再發生，主管要把它看成一個訊號：流程中可能有某個地方不清楚、看不見、太慢、或沒有人真正負責。我們的實務目標很簡單：讓下一步看得見，減少不必要的打斷，並設計工作，讓知識跟著流程走，而不是只跟著少數關鍵人物走。
Bonus Clips
加碼影片
If you want a quick outside perspective, here are three videos that reinforce this week’s lesson:
如果你想快速聽聽外部觀點，以下三支影片會呼應本週課程的重點：
References
AHRQ PSNet. “High Reliability.”
Drotz E, Poksinska B. Lean in healthcare from employees’ perspectives. Journal of health organization and management. 2014 May 13;28(2):177-95.
Green J, Valentini A. A Guide to Lean Healthcare Workflows. IBM Redbooks; 2016 Oct 11.
Weick KE, Sutcliffe KM. Managing the unexpected: Sustained performance in a complex world. John Wiley & Sons; 2015 Sep 15.
Gawande, Atul. The Checklist Manifesto: How to Get Things Right.