Chapter 7 — Faster Than Care Can Move

Faster Than Care Can Move

The clock began before the patient arrived. By the time the ambulance doors opened, the emergency department had already counted the minutes that had not yet passed.

A tracking board glowed above the nurses’ station. Each patient appeared as a row. Beside each name were small indicators: arrival time, triage status, tests ordered, disposition pending. Some rows were green. Some were yellow. A few had turned red.

Red meant too long.

The exact meaning of too long depended on the stage of care. Time to triage. Time to clinician. Time to decision. Time to discharge. Time between the decision to admit and the moment a bed became available upstairs.

The board did not create the pressure. The pressure already existed. People were waiting.

Some were in pain. Some were frightened. Some had been sent by clinics that could not see them quickly enough. Some had come because they had nowhere else to go. Ambulances were arriving faster than rooms were opening.¹ Staff moved among interruptions, alarms, questions, medication checks, test results, family members, and the accumulating awareness that everyone in the waiting room was measuring time differently.

The clock helped the department see what no individual could hold alone. It showed where patients were stuck. It revealed when a test had been ordered but not completed. It allowed a charge nurse to notice that one clinician had inherited several unusually complex cases. It made delay visible before delay became neglect.

The board was useful.

That morning, a woman in her late sixties arrived short of breath.

Her oxygen level was low but not catastrophic. She could answer questions. She carried a bag containing medication bottles, two of which appeared to have been prescribed for the same condition. Her daughter arrived twenty minutes later, breathless from the parking garage and angry that no one had called sooner.

The initial work moved quickly. A nurse assessed the patient. A clinician ordered imaging and blood tests. Respiratory therapy adjusted her oxygen. The daughter stood near the doorway and tried to explain that her mother had been confused for several days, though the patient insisted she was fine. The department had a target for how quickly cases like this should move from arrival to a preliminary decision. The target was not arbitrary.

Long waits can cause harm. Crowded departments miss things. Patients deteriorate in hallways. Ambulances remain unavailable while crews wait to transfer care. Staff fatigue grows as the queue lengthens.

Speed in an emergency department is not a corporate preference imported into medicine. It is part of care. But care does not move at one speed. The blood test returns on a laboratory clock. The scan moves on an imaging clock. The clinician thinks on a diagnostic clock. The daughter speaks on a family clock shaped by several days of worry. The patient answers on a body’s clock, pausing between sentences, trying to remember whether she took the blue pill in the morning or at night. The tracking board contains one of these clocks. It measures elapsed time. It cannot measure how long understanding takes.

This is one of the central tensions in collaborative work: the work must move, and some of what makes the work safe cannot be hurried without changing what it is.

A nurse can ask the medication questions faster. That does not mean the answers will become more reliable. Efficiency is real. So is the cost of asking care to travel at the speed of coordination. For several months, the hospital had been focused on improving throughput.

The word appeared in presentations, reports, and daily huddles. It referred to the movement of patients through the department: arrival, evaluation, testing, treatment, admission, or discharge.

The department had good reasons to care. Patients had been waiting too long. Staff were exhausted by crowding. Ambulances sometimes lined up outside because the department had nowhere to place the next person. Everyone understood that delay was not neutral. The hospital introduced several changes. Clinicians placed some orders earlier. Common discharge instructions were standardized. Daily reports compared teams against average length of stay. Cases without clear next steps were reviewed during the shift. The tracking board became more detailed. The numbers improved.

Patients were evaluated sooner. Some unnecessary waits disappeared. Tests were ordered earlier. A new handoff process reduced the time patients spent waiting for transportation.

The initiative worked.

The improved numbers can settle the board before anyone asks what disappeared inside them. Crowding eased. Patients moved sooner. Leaders can report that the department took waiting seriously. But a shorter stay can mean waste removed, and it can also mean a conversation shortened, a consultation deferred, or a family’s unease filed as something the pathway does not need to hold. The dashboard records the minutes that disappeared. It does not record what the minutes were doing.

It also changed what staff noticed about themselves. A nurse lingered in a room to help a family understand the difference between two medications and felt the red row on the board growing redder. A clinician asked social work to assess whether a patient could safely return home and knew the consultation would add time to the case.

A resident decided to reexamine a symptom that did not fit the initial explanation and felt the small pressure of a target moving farther away. No one told them not to do these things. The system did not need to prohibit care. It only needed to make some forms of care appear as delay.² Once time becomes visible, slowness acquires moral meaning.

The person who asks another question may be thorough. They may also be the reason the waiting room remains full. The nurse who sits beside a frightened patient may be compassionate. She may also be unavailable when another patient needs medication. The clinician who hesitates before discharge may be preventing harm. He may also be occupying a bed needed by someone arriving in an ambulance.

These are not imaginary tradeoffs. Every act of attention uses time that cannot be given somewhere else. But a metric can make one side of the tradeoff easier to see than the other. The minutes appear. The prevented misunderstanding does not. A discharge delayed by twenty minutes is legible. A return visit prevented three days later is harder to connect to the conversation that made the difference.

This is why efficiency initiatives often begin with obvious waste and gradually approach the edge of judgment. At first, the organization removes waiting that serves no purpose. A form is duplicated. An approval sits in an inbox. Information must be entered twice. A patient remains in a room because transportation was requested late. Everyone benefits when those delays disappear.

Then the remaining time becomes more difficult. It belongs to the work itself: the time required to notice that the family’s version of events differs from the patient’s, to ask whether the person has food at home, to understand why the medication list does not match the bottles in the bag. This time can look inefficient because its output is uncertain. Not every careful conversation reveals a hidden problem. Not every consultation changes the plan. Not every pause prevents harm. The system sees many minutes spent and only occasional evidence that the minutes mattered.

Optimization begins to ask a seductive question: Could we preserve the value while reducing the time? Sometimes we can. A better form prevents repeated questions. A shared record keeps people from reconstructing history. A trained interpreter improves a conversation that might otherwise require several attempts. A clear decision right prevents a meeting from circling a choice no one present can make. Human beings build tools precisely because care without structure is exhausting. But the question can also conceal a wish: Could we preserve the appearance of care while removing the part that resists scheduling?

A hospital can standardize discharge instructions. The printed page may be clear. The patient may still nod without understanding.

The form remains, and the relationship thins. This is the point where collaboration begins becoming mechanical. Not when tools enter the work. Tools are necessary. The change occurs when the tool stops supporting judgment and begins replacing the conditions under which judgment can be offered. The emergency department’s discharge template asked whether the patient had transportation, access to medication, and follow-up care. Each item had a checkbox. For many patients, the checkboxes worked.

A nurse asked the questions. The patient answered. The information traveled.

But a checkbox can record an answer more easily than it can record uncertainty about the answer. Transportation: yes. The daughter owns a car. The form does not show that she works nights and cannot leave her job during the next episode. Medication access: yes. The pharmacy is nearby. The form does not show that the patient sometimes confuses the bottles and does not want her daughter to know.

Follow-up: scheduled. The appointment exists. The form does not show that the patient has missed the last two because the clinic is difficult to reach by bus. The form is not wrong. It is too certain for the life it describes.³ Someone must absorb the uncertainty that does not fit. Usually, that person is closest to the patient.

The nurse writes an extra note. The social worker makes a call not required by the workflow. The daughter is given a number to use if the plan fails. A clinician says, “I know the form says she has support. I’m not convinced the support will hold.” That sentence is collaboration. It introduces judgment where the system has already declared the field complete.

Under pressure, such sentences become expensive. They reopen work. They add a consultation. They delay the discharge. They make the row redder. The person offering judgment must decide whether the concern is serious enough to justify the interruption. This is how efficiency compresses dissent. No leader needs to say, “Do not challenge the plan.” The system says something subtler: Challenge it only when you can defend the cost.

Efficiency does not remove judgment. It pushes judgment downward, often onto the people with the least authority to change the system. Leaders see throughput. Frontline workers decide which complexities can be safely omitted to produce it. This work rarely appears in the efficiency report. The report shows fewer minutes. It does not show how many moral calculations were compressed into those minutes. Who received less explanation? Which risk was accepted? Who stayed late to finish the care the schedule did not contain? Which exception became someone’s unofficial responsibility? The system appears leaner because the excess has moved into people. Organizations often describe this as resilience: the team adapted, staff found a way, the department met the goal despite difficult conditions. A system can improve its visible performance by consuming invisible capacity. The nurse skips a break. The family member becomes the unpaid navigator of a fragmented care system. The metric records the outcome. The human body records the cost.

This is one reason speed pressure feels different from an ordinary deadline. A deadline describes time. Speed pressure turns time into virtue. Fast becomes committed. Slow becomes resistant. The person who asks for more time must explain not only the need but the character implied by the need. Why are you not moving with urgency? Why is your team the bottleneck? Why does this case require special treatment? Why can everyone else meet the standard? The language shifts attention away from what the work requires and toward whether the person is sufficiently willing.

Speed pressure makes the sorting feel obvious: fast people care; slow people protect themselves; one is committed, the other is a bottleneck. But the person asking for more time may be carrying the return visit the last quick discharge produced or the family detail that does not fit the checkbox. What looks like a difference in willingness may still be a difference in what each person cannot afford to leave unseen.

This can happen even in organizations filled with caring people. The emergency department’s leaders cared about patients. They also cared about staff burnout, ambulance availability, and the people waiting unseen behind the current case. Speed was not imposed by villains. It emerged from overlapping forms of care. The patient in the room needed attention. The patient in the hallway needed a room.

The ambulance outside needed to return to the city. The nurse needed a shift that did not require running without pause. The hospital needed beds upstairs. Every delay belonged to someone. The danger came when one measure attempted to represent all of these needs. Average length of stay became a way to see crowding. It could not explain which minutes were waste and which were care.

That distinction remained inside people. Under chronic pressure, people protect themselves by narrowing what they offer. At first, they stop raising concerns unlikely to change the outcome. Then they stop asking questions whose answers will create more work. They learn which consultations leadership treats as necessary and which are seen as defensive. They complete the required fields.

They follow the pathway. They hand the patient to the next stage. This can look like professionalism. It can feel like surrender. The work continues, but contribution changes. People no longer offer everything they see. They offer what the system can receive. This is collaboration’s mechanical form: people remain coordinated while mutual updating declines.⁴ The parts move.

The workflow completes. The meeting ends. The patient leaves. The project launches. But the system has become less capable of being changed by the knowledge inside it. That loss may remain hidden for a long time. A mechanical system can be highly effective under familiar conditions.

Standardization saves lives. Predictable workflows reduce error. Clear escalation paths help people act under pressure. Repetition allows large institutions to coordinate across shifts, sites, and professions.

The problem is not mechanism. The problem is brittleness. A system becomes brittle when variation is interpreted only as deviation. The patient who does not fit the pathway becomes a problem for the pathway. The technical concern that cannot be quantified becomes a problem for the schedule. The employee who names a structural contradiction becomes a problem for alignment.

The neighborhood that does not respond to the program as expected becomes a problem of engagement. The work is increasingly designed around the cases that travel smoothly. The difficult cases become exceptions. Exceptions require explanation. Explanation takes time. Time becomes failure. Eventually, the people most in need of collaboration are those the collaboration is least able to hold.

The woman in the emergency department did not fit cleanly into the initial plan. Her tests suggested an infection that could be treated. Her breathing improved. From a medical perspective, discharge appeared possible. The daughter remained uneasy.

“She says she’s taking her medicine,” she told the nurse. “But I found pills all over the kitchen.”

The patient became irritated.

“I know how to take my medication.”

The daughter lowered her voice.

“She has been forgetting things.”

The patient said she was tired and wanted to go home. The clock continued. The nurse could see several versions of care competing in the room. Respect the patient’s account. Take the daughter’s concern seriously. Avoid unnecessary admission. Do not send someone home into an unsafe situation. Open the room for the next person. The discharge pathway had answers for most of these questions. It did not have an answer for how much doubt was enough to stop. That threshold lived in judgment. The nurse asked the clinician to return.

The clinician reviewed the case and requested a pharmacy consultation. The pharmacist compared the medication bottles and found that two prescriptions had overlapping instructions from different visits.⁵ A social worker spoke with the daughter. The patient became increasingly frustrated.

The case remained open. The row turned red.

Nothing dramatic had been discovered. There was no single piece of evidence proving the patient could not go home. The consultation created a slower, more complicated picture.

The department’s metric worsened. The understanding improved. This is what makes efficiency morally difficult. The inefficient step is not always wise. The extra consultation may change nothing. The meeting may genuinely be unnecessary. The request for more evidence may be avoidance. The person slowing the work may be protecting status, resisting change, or seeking certainty that reality cannot provide. We cannot declare every delay sacred merely because some forms of care take time. But neither can we ask the clock to distinguish judgment from waste. People must do that. And people need conditions in which making the distinction does not automatically place them against the system’s goals.

A healthy efficiency practice begins by asking not simply where time is spent, but what the time is doing. Two identical delays can contain different work—one friction, one protection. The dashboard may show only duration. People must distinguish waste from care, and people closest to the work must help interpret the metric, not as a courtesy after leadership decides what the number means, but as part of the decision itself. A throughput review that includes only executives and analysts will see patterns. It may miss the adaptation producing the patterns.

The people doing the work are not infallible. They may normalize dysfunction because they have lived with it too long. They may protect inefficient habits. They may interpret every measurement as distrust. Their perspective does not settle the question. It reveals dimensions the measure cannot contain alone. Collaboration requires this tension: distance enough to see patterns and proximity enough to know what the pattern is made of.

The emergency department needed the tracking board. It also needed nurses who could say why one red row should remain red. Over time, the hospital changed the throughput review. The metric remained. The department still tracked length of stay, waiting time, admission delay, and return visits. But the review began including a small set of cases in which speed and safety had come into tension.

Not only adverse events. Cases where someone had chosen to slow down. Why did the delay occur? What information emerged? Could the same information have been gathered earlier? Was the delay caused by a missing resource, a poor handoff, a necessary conversation, or a workflow that forced staff to rebuild the patient’s story? This changed the meaning of inefficiency.

Some delays remained indefensible. A test had not been ordered because everyone assumed someone else had done it. A patient waited for transportation that could have been arranged two hours earlier. A consultation was requested without a clear question. These delays could be reduced without thinning care. Other delays revealed design problems. Medication information arrived too late.

Families repeated the same history to several people. Social work became involved only after discharge was otherwise complete. The review did not conclude that staff should work faster. It asked why necessary care had been placed at the end of the clock. This is a more humane form of optimization. It does not romanticize slowness.

It moves the work that requires time to a place where time is less expensive. The medication review begins earlier. The family concern enters triage rather than appearing at discharge. Efficiency improves not by asking care to hurry, but by allowing care to begin sooner.

This sounds obvious after the fact. Many structural improvements do. The difficulty is that invisible work often becomes visible only when someone refuses to compress it further. A nurse says the patient is not ready. The statement interrupts momentum. It creates the possibility of better design. It also creates social cost for the person who says it. A system serious about collaboration must not depend entirely on individual courage at the moment courage is most expensive.

It needs rituals, measures, and review practices that make slowing down a legitimate form of contribution under defined conditions—not unlimited delay, not veto by discomfort. A pause becomes less threatening when it has shape.

The construction crew in the previous chapter could stop the lift because the right to stop had been designed into the work. The emergency department could not stop the department. Patients continued arriving. But it could create smaller pauses inside motion: a medication check, a reassessment, a consultation, a conversation in which a family’s concern became part of the clinical picture. The institution did not become free from speed. It became more careful about what speed was allowed to erase.

Late in the afternoon, the woman was admitted for observation. The decision was not dramatic.

Her breathing had improved. The infection was treatable. But the medication confusion and change in memory made the home plan less reliable than it had first appeared.

The daughter looked relieved. The patient looked annoyed. The nurse returned to the tracking board. The row had been red for a long time. When the patient left the emergency department for a room upstairs, the row disappeared. A new patient took its place. The metric recorded a long stay. It did not record the daughter’s hesitation in the doorway. It did not record the pills scattered across the kitchen. It did not record the nurse’s decision to ask one more question. It did not record the pharmacist noticing that two reasonable prescriptions had become dangerous together. The system needed the clock. The clock could not tell the whole story of what happened inside its minutes.

A few weeks later, the daughter sent a brief message through the hospital’s patient portal. Her mother had returned home after the medication plan was simplified. The family had arranged more help. She thanked the staff for listening when the situation had not looked serious.

The message did not appear in the throughput report. It belonged to a slower form of evidence. Much of care does. Collaboration becomes mechanical when we insist that every valuable act move at the speed of the system built to count it. The answer is not to throw away the clock. People are waiting.

The answer is to remember what the clock cannot know.

A system can measure how long care takes.

Only people can decide when moving faster would make it something less than care.

Footnotes

1. See Claire Morley, Maria Unwin, Gregory M. Peterson, Jim Stankovich, and Leigh Kinsman, “Emergency Department Crowding: A Systematic Review of Causes, Consequences and Solutions,” PLoS ONE 13, no. 8 (2018): e0203316, on crowding’s association with poorer patient outcomes and delayed care. ↩

2. See Hochschild, The Managed Heart. ↩

3. See Scott, Seeing Like a State. ↩

4. See Weick, Sensemaking in Organizations. ↩

5. See Janice L. Kwan, Lisha Lo, Margaret Sampson, and Kaveh G. Shojania, “Medication Reconciliation During Transitions of Care as a Patient Safety Strategy: A Systematic Review,” Annals of Internal Medicine 158, no. 5 pt. 2 (2013): 397–403, on identifying and resolving unintentional medication discrepancies across transitions in care. ↩