Week 21: The Myth of Fully Utilized Systems
滿載系統的迷思
Time: 6 minute video
Category: Leadership Systems 領導系統
A hospital system can look efficient from the outside. Every role is filled. Every hour is assigned. Every process has coverage. But a full schedule does not always mean a strong system.
This week’s video looks at what happens when a healthcare system becomes fully loaded. The work may still continue. Tests are still run. Medications are still given. Decisions are still made. Patients still move through the process. But underneath the visible work, more and more safety work may be carried by individual attention, memory, reminders, side messages, and informal follow-up.
The risk is not that people stop working hard. The risk is that the system starts depending too much on people noticing one more thing while they are already under pressure.
A strong system does not remove human judgment. It protects human judgment at the moments where safety depends on it most.
一個醫院系統，從外面看可能很有效率。每個角色都有人。每個時段都排滿。每個流程都有涵蓋。但是，排得很滿，不一定代表系統很強健。
本週影片討論的是：當醫療系統完全滿載時，會發生什麼事。工作可能還是會繼續往前走。檢驗還是有做。藥物還是有給。決策還是有下。病人還是繼續在流程中移動。但是在這些看得見的工作底下，越來越多安全工作，可能開始由個人的注意力、記憶、提醒、旁邊的訊息，以及非正式追蹤來承擔。
真正的風險，不是人停止努力工作。真正的風險是，系統開始太依賴人在已經有壓力的情況下，還要多注意到一件事。
強健的系統不會取代人的專業判斷。它會在安全最依賴判斷的時刻，保護這份判斷。
English Version
中文版 (AI)
Summary of Video
The Central Idea
The myth of full utilization is the belief that a system is strongest when every person, every room, every hour, and every process is fully used.
That belief is tempting because full utilization looks efficient. Nothing appears wasted. Everyone is active. Work keeps moving.
But healthcare is not only about movement. It is also about review, judgment, clarification, confirmation, and safe handoff. These parts of the work require attention. When a system is fully loaded, this attention becomes harder to protect.
This is why a system can be fully busy and still fragile.
Why This Matters for Leaders
A leader may look at a department and see full activity: people moving, tasks completed, patients progressing, and no obvious failure. But activity alone does not show whether the system is safe, stable, or sustainable.
The deeper question is: how much safety work is being carried informally?
Are people remembering too many follow-ups?
Are clarifications happening through repeated side messages?
Are handoffs safe because the process is clear, or because someone is especially careful?
Are people catching issues because the system made them visible, or because someone happened to notice?
These questions help leaders see the difference between a system that is productive and a system that is protected.
Key Takeaways
Full utilization can hide fragility
A fully loaded system may still look productive. But if safety depends too much on memory, reminders, interruptions, and informal follow-up, the system is carrying risk in a less visible way.
Effort is not the problem
People may be working very hard and still be placed in a fragile system. The issue is not lack of effort. The issue is whether the system protects the attention needed for safe work.
Some work needs protected attention
Reviewing a result, clarifying an order, confirming a handoff, and closing a follow-up all require time and focus. These moments should not depend only on someone remembering under pressure.
Strong systems protect judgment
A strong system does not replace clinical judgment. It creates conditions where judgment can happen clearly, safely, and at the right time.
The most important work is not always visible
Visible work is easy to count. Invisible safety work is easier to miss. Leaders need to pay attention to both.
Reflection Questions for Leaders
Where in our current workflow does safety depend too much on someone remembering?
Which steps often require extra messages, phone calls, or informal follow-up?
Where do people need protected attention, but usually receive interruption instead?
Which unclear items should be made visible earlier in the system?
What is one point in our process where a deliberate pause would protect safety?
Are we measuring only how busy people are, or are we also measuring how fragile the work has become?
影片摘要
核心概念
「滿載系統的迷思」指的是一種想法：如果每個人、每個空間、每一分鐘、每個流程都被充分使用，系統就最有效率，也最強。
這個想法很有吸引力，因為滿載看起來很有效率。好像沒有浪費。每個人都在動。工作也一直往前走。
但是醫療不只是讓工作往前移動而已。醫療也需要審閱、判斷、釐清、確認和安全交接。這些工作都需要注意力。當系統完全滿載，這種注意力就更難被保護。
這就是為什麼，一個系統可以全員忙碌，卻仍然脆弱。
為什麼這對主管重要
主管看一個部門時，可能會看到很多活動：大家都在動、任務有完成、病人有繼續往前走，也沒有明顯的失誤。但是，活動量本身不能說明系統是不是安全、穩定，或能不能長期維持。
更深的問題是：有多少安全工作，是靠非正式方式撐住的？
大家是不是記著太多後續追蹤？
釐清問題是不是常常靠旁邊訊息一來一往？
交接之所以安全，是因為流程清楚，還是因為某個人特別小心？
問題被攔下來，是因為系統讓它變得清楚可見，還是因為剛好有人注意到？
這些問題可以幫助主管分辨：系統只是看起來有生產力，還是真的有被保護。
重要提醒
滿載可能會隱藏脆弱性
完全滿載的系統，仍然可能看起來很有生產力。但是，如果安全太依賴記憶、提醒、打斷和非正式追蹤，風險就被移到比較不容易看見的地方。
努力不是問題的核心
大家可能非常努力，但仍然身處一個脆弱的系統。問題不是不夠努力。問題是，系統有沒有保護安全工作所需要的注意力。
有些工作需要被保護的注意力
審閱結果、釐清醫囑、確認交接、完成追蹤，這些都需要時間和專注。這些時刻不應該只靠人在壓力下記得。
強健系統會保護判斷
強健的系統不會取代臨床判斷。它會創造條件，讓判斷可以清楚、安全，並在正確的時間發生。
最重要的工作不一定最看得見
看得見的工作比較容易被計算。看不見的安全工作比較容易被忽略。主管需要同時看見這兩者。
主管反思問題
在我們目前的流程中，哪些地方太依賴某個人記得，才能維持安全？
哪些步驟常常需要額外訊息、電話，或非正式追蹤？
哪些地方其實需要被保護的注意力，但實際上常常被打斷？
哪些不清楚的項目，應該更早在系統裡變得清楚可見？
在我們的流程中，哪一個地方如果設計一個明確的暫停點，會更能保護安全？
我們只是在衡量大家有多忙，還是也有看見工作已經變得多脆弱？
Scripts for Leaders
Keep these short. The goal is not to tell people to work less or try harder. The goal is to help the team notice where the system is relying too much on memory, interruption, and informal follow-up.
-
“I can see that everyone is working hard. The question is not whether people are trying. The question is whether the system is protecting the attention needed for safe work.”
-
“If we keep needing reminders and follow-up calls, the issue may not be the reminder itself. It may be that the process is not making the next step clear enough.”
-
“I’m glad this was caught. Now let’s ask whether the system would catch it next time, or whether it depended on one person remembering.”
-
“Where does this process require careful judgment? And how do we protect that moment?”
-
“Efficiency is not only using every minute. In healthcare, efficiency also means protecting the attention needed for safety.”
-
treating protected attention as wasted time
depending on memory instead of process design
using reminders and phone calls as the normal safety system
measuring activity while missing fragility
blaming people for missing details before examining the system
給主管的對話腳本
這些句子請盡量簡短。目標不是叫大家少做一點，或更努力一點，而是幫助團隊看見系統在哪裡太依賴記憶、打斷和非正式追蹤。
-
「我看得出來大家都很努力。現在的問題不是大家有沒有努力，而是系統有沒有保護安全工作所需要的注意力。」
-
「如果我們一直需要提醒和追蹤電話，問題不一定是提醒本身。也可能是流程沒有把下一步做得夠清楚。」
-
「這次有被發現很好。接下來我們要問的是，下次系統會不會發現？還是仍然要靠某個人記得？」
-
「這個流程裡，哪一個地方最需要仔細判斷？我們有沒有保護那個時刻？」
-
「效率不只是把每一分鐘用滿。在醫療裡，效率也包括保護安全所需要的注意力。」
-
把被保護的注意力當成浪費
依賴記憶，而不是流程設計
把提醒和電話當成正常的安全系統
只看活動量，卻沒有看見脆弱性
還沒檢查系統，就先責怪人沒有注意到細節
Supporting Research
-
This week’s idea connects with human factors, cognitive workload, resilience engineering, high-reliability organizing, and healthcare workflow design. Research in patient safety has repeatedly shown that healthcare work depends on attention, coordination, communication, and system design. Human factors approaches emphasize that safety is not produced only by individual effort, but by designing work systems that support people in doing the right thing under real-world conditions.
The concept also connects with resilience engineering: safe systems are not only systems that avoid failure. They are systems that can adapt to variation, detect weak signals, and support people when work becomes more complex than planned.
-
Not every reminder, message, or double-check is a problem. Some are necessary and protective. Healthcare will always require human judgment and follow-up. The issue is not whether people should pay attention. The issue is whether the system depends too heavily on memory, interruption, and informal coordination as the normal way to keep work safe.
-
At KFSYSCC, this matters because cancer care depends on careful review, timing, handoff, and judgment. Chemotherapy orders, lab values, imaging results, discharge plans, and patient education all require focused attention at key moments. Leaders can protect attention by creating clear pause points, making unclear items visible, clarifying responsibility, reducing unnecessary chasing, and ensuring that important work does not depend only on someone remembering under pressure.
支持性研究
-
本週影片的概念，和人因工程、認知負荷、韌性工程、高可靠度組織，以及醫療流程設計有關。病人安全研究一再指出，醫療工作高度依賴注意力、協調、溝通與系統設計。人因工程的觀點強調，安全不只是靠個人的努力，而是要設計出能支持人在真實工作條件下做對事情的系統。
這個概念也和韌性工程有關。安全的系統，不只是避免失敗的系統，也是能夠面對變化、看見微弱訊號，並在人們需要處理更複雜工作時支持他們的系統。
-
不是每一個提醒、訊息或重複確認都是問題。有些提醒和確認是必要的，也確實能保護安全。醫療永遠需要人的專業判斷和後續追蹤。真正的問題不是人要不要注意，而是系統是不是太常把安全工作交給記憶、打斷和非正式協調來承擔。
-
這對和信很重要，因為癌症照護高度依賴仔細審閱、時機、交接和判斷。化療醫囑、檢驗數值、影像結果、出院計畫和病人衛教，都在關鍵時刻需要專注的注意力。主管可以透過設計清楚的暫停點、讓不清楚的項目可見、釐清責任、減少不必要的追答案，並避免重要工作只靠人在壓力下記得，來保護團隊的注意力。
Bonus Clips
加碼影片
If you want a quick outside perspective, here are three videos that reinforce this week’s lesson:
如果你想快速聽聽外部觀點，以下三支影片會呼應本週課程的重點：
References
Carayon PA, Hundt AS, Karsh BT, Gurses AP, Alvarado CJ, Smith M, Brennan PF. Work system design for patient safety: the SEIPS model. BMJ Quality & Safety. 2006 Dec 1;15(suppl 1):i50-8
https://pmc.ncbi.nlm.nih.gov/articles/PMC2464868/pdf/i50.pdfGurses AP, Ozok AA, Pronovost PJ. Time to accelerate integration of human factors and ergonomics in patient safety. BMJ quality & safety. 2012 Apr 1;21(4):347-51.
https://qualitysafety.bmj.com/content/21/4/347.shortHollnagel E, Wears RL, Braithwaite J. From Safety-I to Safety-II: a white paper. The resilient health care net: published simultaneously by the University of Southern Denmark, University of Florida, USA, and Macquarie University, Australia. 2015 Sep 7.
http://www.qpsolutions.vn/cgi-bin/Document/Safety%20II%20WhitePaper.pdfWeick KE, Sutcliffe KM. Managing the unexpected: Sustained performance in a complex world. John Wiley & Sons; 2015 Sep 15.
https://www.amazon.com/s?k=9781118862414&i=stripbooks&linkCode=qsCatchpole K. Toward the modelling of safety violations in healthcare systems. BMJ quality & safety. 2013 Sep 1;22(9):705-9.
https://qualitysafety.bmj.com/content/22/9/705.short