Chapter 23 - FIVE MINUTES OF SILENCE
The new center portal went offline for exactly five minutes during the first week of March. No one outside the technology team would have noticed if the outage hadn't occurred while an intake worker was correcting the contact number of a woman waiting for transportation. When the screen returned, the change she had entered was gone, and a different address appeared in the destination field.
Amina, our data manager, did not call it sabotage. She locked the affected record against further changes, preserved the screen history, and opened an incident report. Then she asked the participant directly which address she wanted used. The woman confirmed her original destination. The correction was made through a verified channel and documented.
“What scares me,” Amina told me later, “is how easy it is to call a field an error instead of asking what the error would have done to the person.”
“Do you know why it happened?”
“Not yet. We had a connection to a retired directory for five minutes. I need logs from our provider before I can say more.”
That evening Celeste gathered staff for a meeting. She described the incident in general terms and reminded us that nobody should improvise changes outside the approved process. The protocol sounded tedious. A few employees grumbled about how many confirmations were required.
“I know it slows you down,” Celeste said. “If you see a way to make it faster without making it less safe, tell me. But don't skip the checks while somebody's ride depends on the address.”
I thought of my first months as a housekeeper. Everything had to be done quickly, and the person who questioned an instruction was treated as a nuisance. The difference now was not that our center never made mistakes. It was that the mistakes had names, dates, and a pathway for correction.
After work I met Luca at an accessible greenhouse open to the public. He had brought Sophie because she was preparing a science project on plants that could survive Chicago winters. She carried a notebook and asked the volunteer gardener so many questions that he invited her to help label the seedlings.
“Does a plant remember being cold?” she asked.
“Not the way people remember,” he said, “but some plants respond to patterns of temperature.”
Sophie thought about that. “So they need the right information.”
“Exactly.”
I glanced at Luca. He had noticed the coincidence too. He smiled without turning it into a lesson about our investigation.
We walked along the greenhouse's broad paths. He told me his rehabilitation team had suggested a new home exercise routine and asked whether I wanted to hear about it. He was proud of reaching farther across the worktable without pain. I praised his effort without pretending it meant he'd soon abandon the wheelchair.
“People keep asking when I'll walk again,” he said quietly. “It's strange. Some days I want to tell them I've already arrived where I'm going.”
“You're allowed to want better mobility without making walking the price of a good life.”
He looked at me. “You keep finding the sentence I need.”
“Only because other people taught me.”
Sophie returned holding a small plant in a paper cup. She'd named it Captain Parsley and insisted we give it a sunny windowsill. Luca bought the plant after checking the greenhouse's rules, and Sophie informed us she would need a written care schedule.
“She's turning into a committee chair,” I said.
“It's your influence.”
“Your daughter was issuing orders long before I arrived.”
He laughed.
The following day the provider delivered a preliminary explanation for the five-minute outage. A legacy synchronization process had briefly restored an old destination record. The event was described as unintended, but Amina found that the same synchronization had run several times before. She requested a full history and recommended temporary manual verification for high-risk changes.
The incident with the five-minute outage led to an unexpectedly intense debate at the center. One group of staff wanted a complete ban on automated changes. Another pointed out that manual entry also caused errors and consumed hours that could have been spent helping people. Celeste invited Amina to moderate a discussion using examples rather than slogans. I helped prepare the room and kept track of the questions raised by community representatives.
Amina showed us two fictional cases. In the first, an automated system copied an old address into a new appointment because a person had moved. In the second, a worker typed an apartment number incorrectly while trying to help a caller quickly. Both mistakes could produce the same result: a driver at the wrong door. The question was not whether humans or machines were morally better. It was which safeguards caught errors before they harmed someone and how easily the person affected could correct them.
A father who attended the session said he wanted automated reminders because he worked shifts and often couldn't answer daytime calls. Another participant said automated voice systems failed to recognize her speech. Amina wrote both requests on the board and asked whether the system could offer multiple routes rather than forcing everyone through one. We drafted a proposal for participant-selected contact preferences, with periodic opportunities to update them and a human escalation route.
I took the draft home and showed Mom a fictional sample, asking whether the choices made sense. She circled a sentence that said “primary communication modality” and replaced it with “How would you like us to contact you?” She drew a second circle around the checkbox for text messages. “Some people have a phone but can't read small print,” she said. “Ask them what works.” I brought her comments to Amina the next morning. We changed the form before sending it to the advisory group.
The following evening I stayed late at the college library to prepare for an assessment. Jo found me amid a stack of articles and asked whether I had become a full-time form designer. I laughed and told her about the training. She pointed out that my paper was supposed to discuss ethics, not software. “Maybe ethics lives in how the software works,” I said. She considered that, then helped me cut three pages of repetitive explanation from the essay. The finished paper focused on one idea: a correction process is part of consent, because choices aren't meaningful if errors cannot be challenged.
On Sunday I visited Luca and Sophie. Sophie had been experimenting with a little electronic keyboard in the art room. She showed me how a single wrong note could be fixed by playing the measure again. Luca said she had made him repeat a rhythm exercise until he stopped rushing. “She won't let me erase the mistake,” he said, “but she does let me try again.” I looked at the sheet music, marked with pencil corrections, and thought of Amina's logs. The old note stayed visible. The next attempt could still be better.
Luca's external review team independently confirmed that one legacy directory still carried the name of a Moretti-financed contractor. They did not know whether that directory was involved in the center's incident. Their counsel provided the information to the appropriate investigators rather than passing the documents through me.
One complication came from a participant who wanted every automated reminder switched off. The center could honor that preference for its own messages, but external providers controlled some appointment notifications. Amina helped the person identify which organizations held the relevant permissions, then prepared separate requests. The process took longer than anyone liked. It also showed why a single checkbox labeled NO MESSAGES could create false confidence when several systems were involved.
At the advisory meeting, Miriam asked us to put that limitation in the handout. “Don't tell people they've opted out everywhere if you only changed one database,” she said. We revised the language. I admired how often she caught an assumption the rest of us had overlooked. She didn't need a technical job title to recognize when a promise was too broad. The people using a service were often the best testers of whether its explanations made sense.
Before the week ended, Amina asked two volunteers to try the new contact-preference form without coaching. One chose telephone calls but found that the form still asked for an email address as a required field. The other preferred written letters and wondered whether that choice would slow urgent notifications. We corrected the mandatory field and added an explanation of what would happen if a message was time-sensitive. Neither volunteer had complained loudly. They had simply pointed to things the designers had stopped seeing. When Amina thanked them, one said, “I'd rather find the mistake here than at the door of a clinic.” I carried that sentence with me to class, where our professor asked for examples of how consultation could change an actual service. For once I had a clear answer that didn't depend on a dramatic emergency.
That night I called Mom. She had gone to her cooking class and was furious because another student had put raisins in savory bread. I let her complain for ten minutes. The ordinary absurdity was a relief.
“You sound tired,” she said at last.
“I am.”
“Come over Sunday. We can make bread without raisins.”
“I'd like that.”
“Bring Luca if you want. He can learn the difference between kneading and attacking dough.”
I smiled. “I'll ask.”
May you like
When I returned to my desk, a new note from Celeste waited in the training folder. She had written: A FIVE-MINUTE FAILURE CAN MATTER EVEN WHEN NOBODY INTENDED IT. THE QUESTION IS WHAT WE DO AFTER WE KNOW.
I taped it beside my class schedule. It seemed to describe our whole year, from the night of the fall to the ordinary Wednesday when an address changed on a screen.
