Chapter 3: The Exceptions
By the third protected Thursday, Pree had acquired four calendars and lost an argument with all of them.
She came to my desk on Tuesday carrying her laptop open in both hands.
“Can I borrow your eyes?”
“You can have the left one. The right is on a deadline.”
She put the laptop beside mine. Her calendar was packed with coloured rectangles. The client call stood at three on Thursday, a weekly review with a transit authority that used our ticketing software at several service counters.
“The call stays,” she said. “Gareth was clear about external meetings. What I can’t have is the half-hour beforehand.”
The briefing brought together Client Support, Engineering, Field Services and occasionally someone from my team. Pree used it to establish which problems were ours, which belonged to the client’s network and which had already been fixed by someone who had forgotten to tell Client Support.
“Wednesday?” I asked.
She showed me Wednesday. Anneke had a release review until four. The Field Services lead, Nikhil, was at a client site outside the office all day. The transit authority sent its updated incident list on Thursday morning, after its regional managers had checked the overnight figures.
“We could brief on Wednesday using last week’s list,” Pree said. “Then on Thursday I could call everyone separately about the new one.”
“How many calls?”
“Four, if everyone answers. Eight if they don’t.”
I pulled my chair closer. “Move the client call?”
“I asked. Their operations people finish collecting the figures at noon. Their director leaves at four. They’ve found us a window, and I’d like to keep it.”
Pree spoke evenly, but she had been pressing her thumbnail against the edge of the laptop. She let go when she saw me notice.
“What about a written update?” I said.
“We have one. Here.” She opened a document with seven headings and a table. “Engineering writes what they know. Field writes what they know. Support reads both and finds out whether they mean the same thing.”
“Could someone write the differences down?”
“They could. I’m not objecting to writing. I’m objecting to discovering at three-fifteen that two people have used ‘resolved’ to mean different things.”
I knew the document. Last month, “resolved” had meant a replacement screen was on its way. The client had understood it to mean the screen was working.
Pree opened a message thread. Nikhil could join at eight-thirty on Wednesday if Anneke could move her release review. Anneke could move the review if the testing team finished by Tuesday afternoon. The testing lead had replied that Tuesday afternoon was when they intended to test.
“It’s like moving a wardrobe through a house,” Pree said. “You get it around one corner and find somebody has put a bath in the hall.”
I suggested ten on Thursday. The incident list might have arrived by then, and the briefing would be well away from the client call.
Pree looked at me.
“Still Thursday,” I said.
“Still internal.”
We studied the grid. Pree dragged the proposed briefing to Wednesday at four-thirty and sent a tentative invitation to the people she needed. Within minutes Nikhil declined: he would still be driving back. Anneke accepted, then added that she could attend only if the release review finished on time. The testing lead marked it tentative and asked whether Tuesday’s testing could move.
Pree closed her laptop.
“I’ll take it up with Gareth.”
“Tell him about the bath.”
“I think he’s already in it.”
On Thursday I was halfway through a comparison of service-counter wait times when a message appeared from Pree.
Could you look at the incident list? Five minutes.
I called her. She had the list open and was looking for a discrepancy between two versions of a report. We found it: one showed abandoned tickets by location, the other grouped them under the central office. I sent her the corrected table.
At two-twenty-five an invitation arrived: TRANSIT AUTHORITY PRE-CALL.
It was for two-thirty. Pree had included Anneke, Nikhil, me and her deputy. In the body she had written, Internal briefing for today’s external client call. I’m proceeding because the updated figures arrived this morning and we could not find a workable Wednesday time.
There was no attempt to disguise it as an external meeting. Pree had made the difficult choice of naming what she was doing, which left the rest of us with the difficult choice of accepting.
I accepted.
Anneke joined from her desk, Nikhil from a parked van. Pree’s deputy had already marked three items in red.
“The client says the display at Northpoint skipped six numbers,” Pree said.
“It skipped the display,” Anneke said. “The calls went through. The fix is installed everywhere except Northpoint.”
“Why?”
Nikhil leaned towards his phone. “Their manager asked us to hold until their end-of-month count. I have her email.”
“Good. Send it to me, please. Delia, the abandoned-ticket figure?”
“Central office had the right total. The location breakdown was wrong.”
Pree crossed something off. “And the screen replacement?”
“Delivered yesterday,” Nikhil said. “Not installed. They need an electrician for the socket.”
Her deputy looked up. “The note says resolved.”
“It’s resolved for shipping.”
“Then I’ll change the note.”
At two-fifty-six Pree thanked us and ended the call. At three she joined the client. I returned to my comparison, which now required me to remember why I had selected a column in orange.
Pree messaged later.
They’ve agreed to install the fix next week. Also, the electrician is coming Monday. Thank you.
Below that she added:
Gareth has asked to speak to me.
I typed, How did he know? and deleted it. The invitation had been on five calendars. She had not exactly hidden it in a biscuit tin.
Gareth’s listening session took place the following week in a meeting room whose walls were painted with a coating that allowed people to write on them. The previous occupants had left a small blue arrow pointing towards the door. Someone had added escape beneath it.
Gareth capped a marker and greeted each person as they arrived. Pree took a chair near the end of the table. Doug Trelevan from Finance sat opposite her with a folder under his arm. Nikhil came in carrying his phone and apologised for possibly having to answer it. A plant manager from Cambridge joined on the screen, her face occupying most of a wall.
“I want to be clear,” Gareth said, “that this is about listening, not catching anyone out.”
Pree glanced at me. She had told me Gareth’s conversation with her had been courteous. He had also asked her not to repeat the pre-call until he had considered the implications.
On the wall he wrote WHAT MUST HAPPEN ON THURSDAY?
Doug raised a hand. “How firm is ‘must’?”
“Let’s hear the case.”
“Our month-end close depends on a bank file we receive Thursday afternoon when the timing falls that way. We need to check it before a reporting deadline.”
“Could you check it individually?” Gareth asked.
“We do. When it doesn’t match, we need to talk to each other.”
Gareth wrote FINANCE: BANK FILE.
“But,” Doug added, opening his folder, “the preparation meeting we hold that morning could move. We’ve always done it then because the file used to come earlier.”
He slid a printed schedule across the table. He had marked the bank’s delivery window in pen and drawn a line through the Thursday preparation session.
Pree leaned over to see it. “You can move yours?”
“The preparation. I haven’t moved the bank.”
Gareth smiled and added PREP MOVABLE beneath the first note. The marker squeaked.
Nikhil said his team had a different problem. “If an engineer is driving to a site Friday morning, we need to confirm the parts and access details before they leave. Sometimes the client doesn’t confirm until Thursday.”
“Could that be a call with the client?” Gareth asked.
“Sometimes. Sometimes the client tells Support, and Support tells us, and then we find out the part is still in a warehouse in Brampton.”
Pree nodded. “And sometimes the client tells three people three different things.”
On the screen, the Cambridge plant manager lifted her hand. “We have a supplier who confirms Friday collections on Thursday. If the quantities change, our floor lead and purchasing need to agree what ships.”
“How long does that take?” Gareth asked.
“Ten minutes when the numbers agree. Longer when they don’t.”
“Could you exchange messages?”
“We can, and we do. Last week the floor lead was away from the computer loading the things we were messaging him about.”
Gareth wrote CAMBRIDGE: COLLECTIONS. There was a sharp smell from the marker now. He opened the door an inch.
A man from Marketing said his team had held its planning meeting every Thursday for six years. Gareth asked whether there was a reason it could not move.
“We like having it before Friday.”
“Could it be Wednesday?”
The man considered this. “Yes.”
Nobody laughed, including Pree. Her laptop was open on her knees, and she was moving an invitation while Gareth continued down the table.
By the time everyone had spoken, the wall held a mixture of deadlines, habits, shift patterns and one request for the Thursday ban to begin after lunch. Gareth read the list with his marker against his chin.
“We need a consistent way to consider these,” he said.
“Can you decide mine today?” Pree asked. “The client call is tomorrow.”
He looked at her. “For tomorrow, go ahead with the briefing. After that, I’d like us to use the same process.”
“What process?”
“I’ll put together a short form.”
Nikhil checked his phone. “Who reviews it?”
“I will.”
“All of them?” Doug asked.
“At first. I want to understand the patterns before we make anything more elaborate.”
Pree shut her laptop. “And how much notice do you need?”
“Let’s say two working days where possible. If something genuinely unexpected comes up, tell me directly.”
Doug tapped the schedule in his folder. “Will approval cover a recurring meeting, or do we apply every time the bank sends a file?”
Gareth hesitated. “Put the recurrence in the request. I’ll look at it.”
It was a reasonable answer to a room full of different problems. It was also an answer that made Gareth the point at which all the problems met.
He emailed the form that afternoon. It had four questions: the proposed meeting, who needed to attend, why it had to happen on Thursday and what alternatives had been considered. There was a box for urgency and a box for recurrence. Submissions went directly to Gareth.
Pree copied her calendar negotiations into the alternatives box. Doug attached the bank schedule. Nikhil asked whether a missed supplier confirmation counted as unexpected if it happened most weeks.
By the end of the first day, Gareth had received thirty-seven requests. Nine days after launching the form, he had 206.
He told me the number at the printer while we waited for a paper jam to clear. He was holding a stack of applications, each with his handwritten notes in the margin.
“I thought people might be reluctant to ask,” he said.
The printer made a grinding sound and offered us a corner of paper.
“Some of them were,” I said. “Then they found out everyone else was asking.”
He freed the sheet, looked at the torn edge and put it on top of his pile. His phone chimed before he reached the lift. He read the screen, then turned back.
“Delia, would you have time to help me make sense of these?”
I looked at the papers. One page had worked loose from the stack. Gareth caught it against his chest before it fell.
“Yes,” I said.