The Chair Theory

Cover image for Fully Occupied

Fully Occupied

The work would have to wait.

At 9:14 on Friday morning, Helen discovered that a software engineer was available.

She checked again. Twenty minutes, between two meetings. White space. Right there on the allocation dashboard, where a paying client should have been.

“Sam,” she said, appearing beside his desk. “What's happened?”

“I finished something.”

“Without telling me?”

Helen was Head of Resource Optimization at Crestmere Consulting. Her job was to ensure that no expensive person experienced an unassigned moment. The company had eleven overdue projects, but those were delivery issues. An empty rectangle was something she could actually fix.

She booked Sam into a capacity review.

The dashboard turned completely green.

At four o'clock, there would be cake.

Felix, the managing partner, had ordered it himself. 100% UTILIZATION, it said, in icing thick enough to conceal a small accounting discrepancy. Beneath this, at his insistence, the baker had added EVERY MINUTE COUNTS. The amendment cost forty pounds and arrived without affecting the delivery date, a performance Crestmere was considering turning into a case study.

“This,” Felix told the morning meeting, “is what operational excellence looks like.”

He gestured at the dashboard. Forty-three consultants, eleven engagements, every available hour assigned. His bonus was attached to this number, which gave him a deep and principled commitment to its scientific validity.

“And Northbank?” Helen asked.

“Ninety-six per cent complete.”

“It was ninety-six per cent last month.”

“Consistent delivery.”

Northbank Services repaired office equipment. It had hired Crestmere to build a portal through which customers could request repairs without three people copying the same email into different systems. Eight weeks later, the portal had a logo, a launch video, and an award nomination for its customer journey.

No customer had completed the journey. This had kept the feedback admirably consistent too.

Ruth, Northbank's operations director, arrived at ten carrying a laptop and the increasingly unfashionable expectation that software should do something.

“A customer has a broken printer,” she said. “Show me how they report it.”

Felix smiled. “Let's start with what we've achieved.”

“That's what I'm asking.”

He opened the delivery plan.

There were eight workstreams. Each had a lead, a colour, and an impressive percentage. All eight had begun on the same Monday because Felix had personally identified that eight things happening at once would be eight times faster.

It was difficult to argue with arithmetic delivered by someone who approved your salary.

“We parallelized delivery,” he explained.

“Where's the delivery?”

“We're at integration.”

Integration occupied a narrow grey strip at the end of the plan. It had been estimated at two days by someone who would not be doing it.

Sam would be doing it. He was also the shared technical specialist on five other engagements. Each project plan contained a small piece of Sam, and each project manager privately believed theirs included the head.

“Can we get him?” Ruth asked.

“He's in a meeting about his availability.”

They waited.

At Crestmere, waiting was unacceptable for employees. Work was allowed to wait indefinitely.

If a developer needed an answer, Helen assigned them to something else. When the answer arrived, the developer was busy. When the developer returned, the designer was busy. When the designer returned, the client had gone on holiday. The project then waited for a meeting to establish why everyone was so difficult to get hold of.

Nobody had been idle. Nothing had been delivered. Both facts were available, but only one came with a chart.

Sam eventually appeared with two laptops. One belonged to a bank, the other to Northbank. He opened the wrong one, swore quietly, and lost four minutes establishing which customer's problems he was currently authorized to have.

“How much work is left?” Felix asked.

“Perhaps a day, once somebody answers the approval question.”

“Excellent. Monday?”

“I can start in three weeks.”

Felix turned to Helen.

“He's fully utilized,” she said proudly, before remembering why they were discussing it.

She brought up the calendar. There had been a spare afternoon for corrections, but she had sold it to an insurance company. This was called eliminating waste. The insurance work had since overrun by an hour, displacing a bank review, which displaced Northbank's integration slot, which now required moving six people and explaining the situation to a man in Frankfurt.

The original one-hour delay had acquired international representation.

“Surely you allow for things taking longer?” Ruth asked.

“People provide estimates.”

“And when they're wrong?”

“We ask for better estimates.”

This had been the company's approach to uncertainty for seven years. So far, uncertainty had declined to improve its performance.

Felix borrowed two developers from another project. That project was also late, but its client wasn't in the room.

“They'll need access and an explanation,” Sam said. “And we still need the approval decision.”

“Give them each a separate task.”

“Based on which answer?”

“Whichever gets them started.”

By eleven, all three developers were busy. Sam was explaining the system to one while the other messaged him to ask whether the first explanation was available as a document. Helen's chart looked magnificent.

Ruth had still not reported the printer.

The approval question was six weeks old.

Who, exactly, was allowed to request a repair?

The brief said: Users should enjoy seamless self-service with appropriate oversight. Felix had written this sentence after a lunch. He remained very pleased with it. Sales had heard seamless, Operations had heard oversight, and neither had asked him an awkward question before dessert.

“You need to take ownership,” Felix had told Sam when he first asked for a rule.

“Fine. Existing customers can request repairs under their existing contracts.”

“You can't make that decision. It has commercial implications.”

“Then could you ask Northbank to make it?”

Felix had leaned back. This was his mentoring position. It allowed him to dispense wisdom while increasing his distance from the problem.

“Sam, we're a consultancy. Clients pay us for solutions. If we keep taking questions back to them, what does that say about our expertise?”

“That we don't know who they're willing to send an engineer to.”

“Are you comfortable working with ambiguity?”

“Am I allowed to resolve it?”

“Within your remit.”

Sam had become extremely familiar with ambiguity. He had implemented it three times.

The account team assumed that existing customers could submit requests immediately. The approval team assumed that every request needed a manager's permission. The notifications team assumed that submitting a request meant it had been approved.

All three had passed their tests.

Together, they produced a system that congratulated customers on repairs nobody was allowed to arrange.

“Why didn't the teams align?” Felix asked.

Sam displayed the unanswered question. It had been copied to Felix on seven separate occasions. The last reply said Let's avoid analysis paralysis and maintain momentum.

“You told us to keep moving.”

“I didn't say in different directions.”

Felix considered ambiguity a sign of mature leadership. It allowed him to retain every option while other people committed money, code, and weekends to mutually exclusive interpretations. If one proved inconvenient, he could reject it without ever having been wrong.

He called this empowerment.

The empowered people had other words, most of which were unsuitable for the engagement survey.

Lina, the designer, joined them carrying fourteen printed versions of the signup screen. She arranged them on the table like evidence at a particularly dull murder trial.

“Which one did customers prefer?” Ruth asked.

“Felix preferred number nine.”

“Customers.”

“We cancelled that part.”

Lina had requested half a day to try a rough version with three office managers. Among other things, she wanted to know whether they could supply the contract number the form required.

“Would the prototype go into production?” Felix had asked.

“No. We'd use it to find out what works, then build that.”

“So we'd pay you to make something and throw it away.”

“Before we pay everyone else to make the wrong thing.”

“Let's keep the language constructive.”

He had refused. Research would delay delivery. He objected to paying for things that would not be used.

Instead, he had approved fourteen finished screens, eleven of which would not be used, plus a training video explaining how to find the contract number.

The video had subtitles in three languages. In each language, it instructed the customer to contact Northbank.

“We built a self-service portal that tells people to call us?”

“Only if they need assistance,” Felix said.

“They need the number.”

“Then the assistance is relevant.”

Lina placed the cancelled research task beside the latest rework estimate. £480 saved. £38,400 to revise the affected screens, rules, and training materials.

“Those costs sit in different budgets,” Felix pointed out.

“The money still leaves the same company,” Ruth said.

“That's a very high-level view.”

Felix's own figures were impeccable. The saving belonged to him. The expense belonged to delivery. This was why his decisions were so consistently economical.

The unanswered questions had multiplied while everyone worked around them. What could once have been changed in a sketch now required three teams, a supplier, and a discussion about whose fault it was. Crestmere had saved money on learning and purchased the consequences in bulk.

There was, however, good news.

Productivity was up.

The welcome email had been written, rewritten to mention approval, and rewritten again to remove approval because approval sounded unfriendly. Three completed tickets. The team responsible had won a small internal award.

“You've given them an award for putting it back?” Lina asked.

“For their responsiveness.”

“The final email is identical to the first.”

“Then we already know it works,” Felix said.

It did work. It welcomed people with extraordinary reliability. Some had been welcomed nine times without ever gaining access to anything.

Rework was particularly valuable because it generated fresh tasks without requiring fresh clients. Managers had begun splitting corrections into smaller tickets so that the delivery figures would properly reflect their teams' tremendous effort. One developer closed seventeen tickets by changing a phrase across seventeen screens. The phrase was Almost there.

Helen suggested that Sam split the integration into smaller tasks too.

“Will that get me more time to do it?”

“It'll make the progress visible.”

“I haven't made any.”

“You could start by creating the tasks.”

He did. Then he closed the task for creating them. The dashboard congratulated him on breaking his streak of inactivity.

The completed-work counter climbed. The customer waited. Crestmere had confused counting activity with measuring progress, then built a reward scheme around its mistake.

By lunchtime, Ruth wanted a demonstration.

Felix summoned the latest version. “Iteration Six,” he announced.

“What did you learn from the first five?”

“We've substantially increased velocity.”

“About customers.”

He explained that Iteration One had been the database. Two, the screens. Three, the approval engine. Four had involved making the screens fit the approval engine. Five had involved making the approval engine fit the screens.

“And six?”

“We're bringing it all together.”

“So this is the first time any of it might work from beginning to end?”

Felix looked disappointed. “You can't expect perfection straight away.”

“I'm asking to report a broken printer. I'm not asking it to develop feelings.”

He handed her the mouse.

The system welcomed her. Then it asked for approval from an administrator who had not been appointed because nobody had decided who should appoint them.

The launch video began playing automatically.

Service. Simplified.

“An iteration,” Felix said over the music, “is an opportunity to learn.”

“Then learn this: I can't use it.”

“That's valuable feedback.”

“You had it six weeks ago.”

Felix suggested recording the issue for Iteration Seven. The team could meanwhile continue building the analytics dashboard, which was already scheduled and therefore important.

They had put numbers on stages of a plan and called it iterative development. The demonstrations rehearsed success; the feedback was filed; the assumptions remained intact. The process had repeated five times. The thinking hadn't moved once.

“We should test a smaller version,” Lina said. “See where people get stuck. Change it before we build everything around it.”

“We can't keep changing direction,” Felix said. “We're supposed to be agile.”

Ruth muted the video. Felix continued.

“We need to manage expectations,” he said. “I can't commit to a date while requirements keep emerging.”

“The requirement is still the printer.”

“The detail—”

“Has been getting more expensive while you've been avoiding it.”

She turned to Sam and Lina.

“Here's what happens next. Existing customers. Their account managers invite them under an approved contract. Start with one customer, one kind of repair, all the way through to my service desk. I'll sign off that rule. You two work on it together.”

Helen inhaled sharply.

“Other work will have to wait.”

“Other work is already waiting. You're just charging more people for the experience.”

Felix began to explain the cost of reserving capacity.

Ruth explained the cost of keeping two temporary staff to copy emails, of customers phoning twice, and of paying eight teams to produce a portal that could send congratulations but not a repair request.

Then she explained the cost of withholding the next payment.

This final estimate was sufficiently precise to support a decision.

The cake was served at four as planned. Felix asked the photographer to keep Ruth out of the picture. She was still on the phone explaining why Northbank's launch had become an experiment.

Two internal initiatives were paused. The bank was told when its next changes would actually arrive. Sam and Lina were given three days together, with time left for whatever the first attempt revealed. The additional developers checked customer records and tested request delivery once the approval rule was settled. Having compatible instructions made working in parallel considerably less exciting.

On Monday, Lina tried a rough invitation screen with an office manager. The invitation supplied the contract number automatically. The office manager immediately chose the wrong building because the company called two of them “Head Office.”

Lina added street addresses. The office manager tried again. Two more people tried it. One found another problem. They changed that too.

“Now you throw it away?” Felix asked.

“Now we know what to build,” Lina said.

He looked at the discarded screen with the expression of a man watching someone burn a banknote. Behind him, fourteen finished designs waited to be invoiced.

By Wednesday, the team had connected a small working service. An invited customer could report a printer fault and receive a reply from the right support desk. It lacked most of the promised features, but it possessed the unusual advantage of doing something promised.

The first live requests exposed a confusing confirmation message. Lina revised it. The next version also handled a second kind of repair. Customers could use the existing service while the team improved and extended it. For once, the version number came with a difference somebody outside Crestmere could describe.

Felix called this “the recovery phase.” He remained concerned that the team had completed fewer tickets.

Nobody had become eight times cleverer. They had made a decision, stopped starting things, and left enough time to find out what needed changing. The work spent less time waiting for busy people to become available.

Utilization fell. Delivery improved.

Helen put the two figures side by side. Felix asked her to use separate slides.

There were still invoices for discarded work. The wider portal was still late. Ruth approved the limited service and asked when the next useful part would arrive. She did not nominate anyone for an award.

Crestmere handled that internally.

At the following partners' meeting, Felix presented Northbank as a triumph of decisive intervention. The previous weeks were described as “necessary exploration,” including the weeks during which he had explicitly prohibited exploration.

He praised the team for doing more with less.

Helen noted that they had achieved it by allowing people to be less busy.

“Exactly,” Felix said. “More focused utilization.”

He approved a company-wide initiative to replicate the success. All eleven engagements would adopt the new approach simultaneously. Each would require workshops, revised templates, and a presentation from Sam, whose experience made him essential to every rollout.

Helen opened the allocation dashboard.

There was a white rectangle on Thursday. Twenty minutes. Sam had left it free in case Northbank needed a correction after its next release.

“What's that?” Felix asked.

“Capacity to respond.”

“Excellent. Book him to explain that to the other teams.”

The rectangle turned green.

The work would have to wait.