Chapter 13: The Dashboard
Corinne’s office window faced another window. On clear days I could see the people in the building opposite drinking coffee and attending meetings. On this particular morning, a man was standing with his back to us, adjusting a large photograph of a mountain.
“He’s had that crooked for weeks,” Corinne said.
I looked at her. “Do you know him?”
“No. I know the mountain.”
She turned her screen towards me. A blue tile occupied its upper corner.
PARTICIPATION: 68%
“That’s wrong,” I said.
“Good morning to you too.”
“Sorry. What does it count?”
“Transfers. Gareth’s team gave us the figures.”
I pulled my chair closer. Underneath the tile was a smaller line: Thirty-four of fifty team leads and designated representatives recorded in transfer activity, 15 October–31 January.
“Thirty-four people are named,” I said. “Some of them appear many times.”
“The tile says participation, not transactions.”
“Participation in what?”
Corinne tapped the screen. “The programme.”
“Those fifty people are the leads and representatives on the list. They aren’t the staff who attended the meetings, and they aren’t all the people affected by moving them.”
She folded her hands. “Does the number describe the proportion of that list who took part in a transfer?”
“Yes, if we call being named on a transfer taking part. Some were approving a colleague’s request.”
“Then it’s a useful number.”
“It could be. It isn’t a measure of whether the transfer helped them.”
Corinne considered the tile. “It doesn’t say it helped them.”
“People will infer that.”
“People infer all sorts of things from a blue box. What would you call it?”
I suggested Representatives named in transfers. She typed it beneath the number, then sat back.
“That’s accurate,” she said. “It also sounds as though they were questioned by the police.”
“The colour may soften it.”
She smiled, but kept typing. “We can show both the number of representatives and the number of transfers. I want the board to see that teams are working across boundaries.”
“Some are. A few teams account for a lot of the movement.”
“Which few?”
I opened the register and sorted by originating unit. Engineering, Sales and Client Support appeared repeatedly. Several entries were repayments or linked to earlier agreements. I showed her how one permission could move between two units and later generate multiple promises, each of which appeared as another row.
“Are those duplicates?” she asked.
“No. They’re different agreements. They just don’t necessarily represent different people finding the programme useful.”
Corinne leaned forward. “Can you show me the chain?”
I traced one through three quarters. She asked where the approvals lived. I opened the emails attached to my notes, then had to search my inbox for a later amendment.
“And if you’re away?” she asked.
“I can give Gareth access to the mailbox.”
“And who will do your job?”
Outside, the man had stepped away from the mountain. It was still crooked.
I showed her the register’s history and the folder where I kept the approvals. Corinne asked what happened if two leads agreed to different terms, who checked the available balance, and whether anyone could change an offer after someone had relied on it. I could answer most of the questions. The answers involved me.
“The Book runs on an old development server,” she said. “Who maintains it?”
“Anneke’s team. Simon built the interface.”
“Is maintaining it part of anyone’s job?”
“Not formally.”
“Then we have a system people rely on, hosted by people who have other work, connected to a register held together by your inbox.”
“When you say it like that—”
“I want you to hear it like that.”
She was right about the server. Simon had already asked Anneke twice for help when it stopped displaying new offers, and I had once corrected a transfer while waiting for a dentist because two teams needed an answer before lunch.
Corinne pointed at the screen. “Build us something supported. Company login, recorded approvals, a proper history. We should know who agreed to what without sending you to the dentist with a laptop.”
“I didn’t take the laptop to the dentist.”
“Where did you take it?”
“The waiting room.”
She made a note. “I’d like you to lead the work.”
“With Engineering?”
“And People & Culture. Bettina can advise on the rules. Simon should be involved in the transition; he knows what people actually use.”
I looked again at the blue tile. “We still need to understand the side arrangements.”
“Yes. Bettina is collecting examples.”
“She’s collecting what people choose to tell us.”
“Which is more than we knew last week.”
I could have repeated what she had just said about my inbox. Information entrusted to one route was not necessarily complete. Instead, I asked what leading the work would mean.
“Define the requirements. Bring me a proposal for ownership and reporting. Gareth will be involved.” She paused. “You’ve built something people use, Delia. I’d rather have you deciding what happens to it than standing outside the room correcting the labels.”
The mountain finally came off the wall. Its owner held it at arm’s length, examined the back and disappeared from view.
“I’ll prepare a proposal,” I said.
“Good. And keep the corrected label.”
The Records room was behind Reception, past a door that tended to close on the heel of anyone carrying a box. I held it with my foot while a woman I recognised from the allocation list backed through with a trolley.
“Thanks,” she said. “It usually gets me.”
The trolley held six archive boxes and a plastic container of soup. The soup slid towards the edge as she turned.
“I’m Delia,” I said, catching it.
“Marisol. You’re here about Thursdays?”
“I was hoping to ask how the transfers have worked for you.”
“That depends which Thursday.” She took the soup from me and called into the room. “Glen, we’ve got a visitor.”
Glen sat at a desk beside a printer large enough to have its own weather. He was eating a sandwich over a sheet of paper. Three boxes waited on the floor beside him, each with a yellow request slip tucked under its lid.
Marisol put the soup in the microwave.
“We gave up our slot last quarter,” she said. “We weren’t using it.”
“Records has one permission per quarter,” I said. “For the team.”
“I know. I signed the form.”
“I’m sorry. I’ve been explaining it all morning.”
“Then sit down before you explain it again.”
Glen moved a box so I could take the spare chair. The printer started with a clunk and fed out labels. He took the first sheet before it could curl into the tray.
“We got a future promise for it,” he said. “I thought that was sensible. If we need a meeting later, we’ll have two.”
“Assuming the other team can deliver,” Marisol said.
“They signed.”
“So did the people who said the lift would be fixed by Tuesday.”
Glen stacked the labels. “I still think it was sensible.”
I asked what they would use the extra permission for.
“A proper review of retention dates,” he said. “We keep finding files marked three different ways.”
Marisol lifted the lid on one box and showed me folders bundled with elastic. “We can do some of it separately. The disputed ones need both of us, and we need someone on the desk.”
“Could Reception cover?”
“Sometimes,” she said. “Not when they’re short as well.”
The phone rang. Glen put down his sandwich and answered. A caller needed a file retrieved before a client visit; he wrote the reference on a yellow slip, repeated it, then asked when the visitor was expected.
“Twenty minutes,” he said after hanging up. “I’d better find it.”
Marisol stopped the microwave with eleven seconds left. “I’ll take the desk.”
“You haven’t eaten.”
“I can eat there.”
She carried the soup out. Glen looked at the three boxes on the floor, then checked the shelves for the new request.
“Does that happen often?” I asked.
“The phone? Yes.”
“I meant lunch.”
“We manage.” He pulled a folder from a shelf, opened it and frowned. “This one’s misfiled. Could be the next aisle.”
I followed him between the shelves. He found the file in a box marked with the previous year and checked its reference against the slip.
“I don’t mind the transfers,” he said. “Last quarter we had no use for a meeting permission. Now we might. I’d like the promise honoured.”
“And the desk?”
“I’d like cover for that too.”
When we returned, Marisol was at the counter with a visitor. Her soup sat open beside the keyboard. She gave Glen the visitor’s name, and he took the file through to Reception himself.
I waited until he came back.
“Would it help if I included the coverage problem in my report?” I asked.
“Yes,” Marisol said. “Include that we’ve asked for cover before. Otherwise it’ll sound like we’ve only just thought of it.”
“Who did you ask?”
“Reception first. They helped when they could. Then our manager, who said we should put dates forward.”
“We did,” Glen said. “Two were during leave, and one was when the printer needed replacing.”
Marisol touched the side of the machine. “It wasn’t this one. This one has never needed anything in its life.”
The printer produced another label.
I wrote down their dates and asked whether I could name them. Glen agreed. Marisol wanted to see the wording first, which seemed fair given my morning’s work on labels.
At my desk, I added a section to the report: Capacity to use permissions depends on operational coverage. Under it I described the desk, the retrieval requests and the postponed review. I sent the paragraph to Marisol and Glen.
Then I returned to Corinne’s proposal. I put coverage in the list of questions the new system should help us investigate. The first requirement was still a supported register with named approvals.
By the time I sent the document, Marisol had replied.
That’s accurate. My soup was cold, but you can leave that out.