Chapter 10 of 35

AI-generated book by Felix FinchBook rights and permissions

Chapter 7: Two for One

Anneke sent me an invitation to a migration rehearsal for the following Thursday.

I checked Engineering’s balance before I accepted. Zero.

I walked over to her desk.

“You’ve used all thirteen.”

“We’ve scheduled all thirteen.”

“You’ve sent the invitation.”

“Yes. That was how I intended to attract the people.”

She moved her chair aside so I could see the calendar. The migration involved a customer’s queue data, a new server and several people whose names appeared in nearly every available square.

“We can rehearse Wednesday,” she said, “but the customer’s test file won’t arrive until late afternoon. The migration is Friday morning.”

“Can you use an older file?”

“We could practise being successful with information we already understand.”

“What happens if the file is late Thursday?”

“We have a different problem.”

She had declined to state that one because it was not yet my problem. I admired the discipline.

“Can the migration move?”

“The customer has arranged a weekend closure. We asked.”

She pointed at the invitation. “I haven’t sent this outside Engineering yet. I wanted to see your face first.”

“My face says ask Gareth.”

“Your face says you’re going to check the register.”

I checked the register. Several teams had unused permissions, though an unused permission was not the same thing as an offer. I called two leads; one needed hers for a discussion with a supplier’s internal account team, and the other was waiting for a decision about December.

Then Kirstie emailed me.

Reception can’t spare its slot after all. Fair enough. We’ve looked at our own plans, though, and Marketing could give up one this quarter if someone can help us in January.

Her sign-off ended with an x. Kirstie put it on messages about campaign budgets, delayed artwork and once, in a reply to Doug, an invoice dispute. I had never seen him return it.

I took my laptop back to Anneke.

“Marketing has one now,” I said. “Kirstie wants help in January.”

“What kind?”

“I’m going to ask.”

Anneke leaned towards the screen. “Tell her we have thirteen next quarter.”

“They haven’t been issued.”

“Tell her we expect thirteen.”

I wrote to Kirstie: What are you proposing?

She called instead.

“We have a campaign launch in January,” she said. “There’s a review we can probably hold on Wednesday, but the product people won’t confirm their dates. I’d like a bit of room if we need it.”

“One future slot?”

“Two would be useful.”

“For one current slot?”

“Yes.”

I looked at Anneke, who was pretending not to listen with considerable physical effort.

“Kirstie wants two next quarter,” I said.

Anneke held up one finger.

“Engineering would offer one,” I told Kirstie.

“I’ve only got two for the whole quarter now, and I’d be giving one up. In January we may need more than our allocation.”

“You don’t know what the allocation will be.”

“Neither does Anneke.”

Anneke held up two fingers, then lowered one.

“She says one,” I said.

“I heard her chair,” Kirstie said. “Tell her I hope the rehearsal goes beautifully.”

The line went quiet. Kirstie had not hung up; I could hear someone asking her where a file had gone. She covered the phone to answer, then came back.

“Delia, I’m not trying to make this difficult. If Engineering can’t do two, we’ll keep ours. I can find a use for it.”

I muted the call.

“She’s serious,” I said.

“So am I. I have other meetings in January.”

“You could move one.”

“I could also move two. That doesn’t mean I want to.”

She studied the rehearsal invitation. A message appeared on her screen from her deputy: Need to tell the client team today.

“Ask when she needs them,” Anneke said.

I unmuted. Kirstie wanted the promises available throughout the next quarter, for meetings Marketing would specify later. Engineering could not promise to make Marketing’s colleagues attend; Kirstie understood that. What she wanted was agreement to transfer two permissions once Engineering received them.

Anneke took the phone from me.

“Kirstie, if we do this, you’ll release the current slot for the rehearsal on Thursday?”

“Yes.”

“And you’ll tell me as soon as you know your January dates. I don’t want to find out on the morning of a launch.”

“You’ll know before then.”

“Two future slots,” Anneke said. “Subject to us getting them. If the allocation changes, we’ll have to talk.”

“Agreed.”

Anneke returned my phone. I sent both leads a message setting out the terms: Marketing would transfer one unused current-quarter slot to Engineering for the specified rehearsal. Engineering promised to transfer two next-quarter slots to Marketing when allocated, for meetings Kirstie would later identify. Both replied with their approval.

I entered the current transfer in THURSDAYS. Marketing’s remaining balance fell by one; Engineering’s rose by one. The total stayed at forty-two.

Below it, in a separate row, I recorded the future promise. There was no balance to subtract yet. I added a Terms column so the two rows could refer to each other without pretending that January’s permissions had already arrived.

Anneke watched me type.

“Does the warning still apply?” she asked.

“Yes.”

“That the sheet doesn’t create a right?”

“Yes.”

She considered it. “Kirstie will still expect her two.”

“She should. You promised them.”

“I know. I was checking whether you’d found a clever way out for me.”

The rehearsal invitation went to the client team ten minutes later. Anneke’s deputy accepted immediately. Another person proposed a different time, then withdrew the proposal after Anneke called him.

At four, Kirstie sent me a thumbs-up beneath the confirmation, followed by an x. I did not know which part of the transaction deserved the kiss.


The following week, I took the register upstairs to Gareth.

He was at his desk cleaning his glasses with a cloth he kept in a small leather case. The cloth looked cleaner than most of the company’s windows.

“Good news,” he said. “The migration went ahead.”

“It did. Anneke says the rehearsal caught a problem with the customer file.”

“That’s exactly the kind of work we wanted to protect.”

“Engineering used a Thursday slot for it.”

He paused with the glasses in his hand. “Yes. Well, protect or permit, as appropriate.”

I showed him the two linked rows. He read them, put on his glasses and read them again.

“Marketing gave up one and gets two later.”

“If the allocation is issued as expected. They’ve agreed to talk if it changes.”

“That seems enterprising.”

“It’s a rate, Gareth.”

“It’s an agreement between two leads.”

“It’s both. Kirstie had something Anneke needed this quarter. Anneke agreed to give her twice as much next quarter.”

Gareth took off his glasses again. I had brought the wrong kind of problem; he had already cleaned them.

“Was anyone pressured?” he asked.

“Kirstie was prepared to keep her slot. Anneke wanted the rehearsal. They negotiated.”

“And the rehearsal prevented a problem for a customer.”

“Yes.”

He spread his hands. “I’m trying to see what you would have me do.”

I had been hoping he would supply that part. I opened the meeting report instead. Scheduled internal meeting hours had fallen against the original calendar query Gareth had used at the all-hands. The decline was substantial, though the query counted invitations, not whether a meeting was useful or whether its work had moved elsewhere. It also could not tell us how many people had read a document after a meeting disappeared and then called one another about it.

I pointed out those limits.

“Of course,” he said. “But the reduction is real?”

“In scheduled hours, on the same measure, yes.”

He smiled at the graph. “People are getting time back.”

“Some are. We haven’t measured what happens to the work.”

“And we should. But we can’t dismiss the improvement because it doesn’t measure everything.”

I could not argue with that, particularly since I had made the graph. The line fell cleanly. I had chosen a scale that allowed the whole period to fit on one screen, and Gareth was leaning forward to look at it.

“The terms are visible to every lead,” I said. “Someone else will see that one current slot went for two later.”

“Would that be so bad?”

“I don’t know yet.”

“Then monitor it. Let’s see whether people use the arrangement.”

“They may already be using it because they saw the first agreement.”

“Then we’ll learn from that too.”

He asked me to include the exchange in the quarter-end report. I agreed, though a report seemed a slow way to catch something that could be copied in an email.

Back at my desk, I found a message from Field Services asking whether Finance would consider “the Marketing terms” for a December permission.

Doug had replied before I opened it.

Which December permission?

Nikhil answered: I was hoping you had one.

I added their exchange to my notebook, then opened the register. The new Terms column was wide enough to show two next-quarter slots without anyone having to click into the cell.

I left it that way. Anyone relying on the agreement needed to see what had been promised.