Chapter 3 - Boston - The Contract

The building was newer than she had expected. MontaraTech’s Boston headquarters occupied the upper floors of a glass and steel tower on the edge of the financial district, the kind of structure that had been built in the last decade to signal permanence without requiring it. The lobby was high-ceilinged and quiet, with a reception desk positioned at a distance that discouraged approach without invitation. Two security barriers stood between the entrance and the lifts, their lines clean and their function clear. The whole space communicated an organisation that had organised itself deliberately, that understood how environments shaped behaviour, and that had spent money to make the message architectural rather than verbal.

Sara Mitchell stood in the lobby for approximately thirty seconds after the receptionist had taken her name and directed her to wait. She used the time the way she always used it in a new building: reading the room’s details before anyone arrived to manage her impression of them. The visitor chairs were positioned facing the entrance rather than each other, which told her something about the priority placed on individual arrival over relationship-building in transit. The internal signage used function titles without names, suggesting a culture that valued role over individual. The security process was smooth and unremarkable, which indicated that external visitors were a regular occurrence rather than an occasion.

None of this was conclusive. But she had learned over many engagements that buildings told you things that briefing documents did not, and that the things they told you were often the things that mattered most: how an organisation thought about itself, what it signalled to the outside world, where it had and had not exercised discretion.

A young woman from the executive assistant team arrived at the barrier two minutes ahead of the scheduled time and took her up to the fourth floor. The executive floor had the same controlled quality as the lobby, slightly compressed in scale but no less precise. The carpet was a shade darker than the floors below. The lighting was calibrated at a level that was professional without being clinical. Through the glass wall of the main meeting room she could see a table set for eight, with a jug of water, pads, and pens positioned at each place with the symmetry of a room that had been laid out by someone who knew exactly what it was for.

She was taken instead to a smaller room at the end of the corridor—a private office that had been configured as a meeting space, with two chairs at a low table rather than a desk between them. This told her something too. David Mercer had chosen to have this initial conversation in a room that was not primarily his, and in a configuration that removed the physical marker of authority. She registered the choice without drawing conclusions from it. It was consistent with what she had understood about him from the preliminary material, but consistency was not confirmation.

• • •

David Mercer was fifty-one, lean in the way of someone who had managed time carefully for a long time, with the composed alertness of a person who had spent years in rooms where the ability to read a situation quickly was more useful than being the most prepared person present. He had come from consulting, Sara knew—a decade at one of the large strategy firms before moving into industry, first as a transformation lead at a manufacturing conglomerate, then as COO at a mid-sized engineering group, and then here. He had been at MontaraTech for twelve months. Not long enough to have been responsible for the situation, long enough to have understood it.

He stood when she entered and shook her hand with a directness that skipped the preliminary pleasantries without being brusque. They both sat.

“I appreciate you being here,” he said. “I know the timeline we’ve put around this is tight.”

“Twelve months is workable,” Sara said. “If we’re clear about what we’re using them for.”

He gave a slight nod, the kind that acknowledged something without endorsing it. “The board has framed this as a programme. The precision controls line is underperforming relative to target, and relative to the other lines. The expectation is that we treat it as a contained improvement initiative, restore performance, and move on.” He paused. “Those are the terms of the mandate as it was agreed.”

“I’ve read the board papers,” Sara said.

“Then you know what they’re expecting.”

“I know what the papers say. I’m less certain the papers reflect what’s actually happening.” She said it without emphasis, as a statement of working position rather than a challenge. “Tell me what you think is happening.”

He was quiet for a moment. Not hesitant—she did not get the impression he was uncertain about what he was about to say, but rather that he was confirming the framing before he said it.

“The product line is the symptom,” he said. “The company is not staying ahead the way it was. Not dramatically. Not in a way that will show up in this year’s numbers in a way that frightens anyone. But the trajectory has changed, and I’m not sure the organisation can see it from inside its own reporting structures.” He looked at her directly. “That’s why you’re here, and it isn’t the reason I gave the board.”

Sara listened to this with the stillness she brought to all early conversations in a new engagement: receiving information without responding to it yet, holding it against the picture already forming from everything else she had gathered. She had read the performance data, the board papers, the strategic plan, and three years of management accounts before arriving. She had looked at the market positioning and the competitor landscape. She had read two analyst reports and one piece of sector research that the company had not commissioned but that described the segment accurately.

None of what David had said was inconsistent with what she had read. All of it was consistent with a pattern she had encountered before in organisations at a specific inflection point: not failing, not in crisis, but no longer moving forward at the rate their advantage required. The gap between them and the competitive field was narrowing, and the organisation’s systems and routines had not yet registered it in the form of a signal that anyone knew what to do with.

• • •

“The contract terms,” she said after a moment. “Twelve months, fixed engagement, starting from first of next month.”

“Correct. The rate structure is as agreed. The board expects visible progress within ninety days. Tangible improvement in the product line by mid-year. A recovery plan in place by month eight at the latest.” He paused briefly. “I’m going to be honest with you. The board is expecting a programme outcome. Targets hit, team realigned, line restored. That’s what they’ve committed to in the language they use.”

“And what are you expecting?”

He considered the question. “I’m expecting you to tell me what’s actually wrong. And I’m expecting that answer to be more complicated than what we’ve framed.”

“It usually is,” Sara said. “The presenting problem is almost never the whole problem. It’s just the part that became visible first.” She let that sit for a moment. “What you’re describing is a company that was ahead and is no longer as far ahead as it was. The instinct is to treat that as a performance problem. Fix the underperforming unit, restore the numbers, move on.”

“That’s what the board has approved.”

“I understand that,” she said. “And we’ll start there. But performance is a result. The question is what’s producing it.” She shifted slightly. “Most organisations think advantage is something they achieve. A strategy is set, it’s executed, and if it’s good, the company moves ahead. The mistake is treating that position as something you hold. It isn’t. Competitive advantage requires continuous maintenance. The moment you stop actively maintaining it, the field begins to close. Not dramatically. Quietly. Exactly as you’re describing.”

David was listening in the way of someone who had thought along similar lines and was interested in how someone else articulated the same ground.

“If you need to stop and reset your strategy every year,” Sara continued, “you’re already behind. The reset is the symptom. It means the organisation isn’t built to maintain position continuously—it’s built to achieve position episodically. Those are very different operating models, and they require very different structures to support them.”

“And you think that’s what’s happening here.”

“I think it’s worth testing. Which is what the assessment will do.”

He leaned back slightly. “The board won’t accept a broad diagnostic as the first deliverable. They want to see action on the product line within ninety days.”

“I’m not proposing to delay action. I’m proposing to understand the system before acting on one part of it. Those aren’t the same thing.” She looked at him steadily. “We’ll start with the product line. That’s the mandate and I’ll work within it. But the assessment will tell us what’s actually constraining it, and some of those constraints will sit outside the product line’s boundary. When they do, we’ll need to be able to talk about that.”

“Will the board be ready for that conversation?”

“They’ll be ready if the evidence is clear enough,” David said. “That’s your job.”

“Yes,” she said. “It is.”

• • •

They covered the practical structure of the engagement in the following thirty minutes: the access she would need, the individuals she would be meeting in the first week, the governance arrangement that would position her formally within the existing programme structure while leaving her genuinely independent of it. David was precise about the political topology. Certain leaders would be cooperative. One or two would be cautious. The CFO would be sceptical of scope and budget until the evidence made scepticism harder to sustain than belief. The Chief Product Officer had defined the product line problem as a set of execution issues within his domain, and would need careful handling at the point where the assessment suggested otherwise.

Sara noted all of this. She did not comment on any of it. She had heard similar versions of the political landscape in most of the organisations she had worked in, and she had learned that the description of the landscape and the landscape itself were never quite the same thing. The actual topology only became visible through behaviour, and behaviour only became visible over time.

What she was listening for, beneath the practical briefing, was the shape of the organisation’s thinking. Where leaders placed emphasis, what they treated as given, what they were unwilling to hold as a question. The strategy, David had made clear, was not in doubt. The company understood its market and had a clear direction. Leadership was broadly aligned around that direction. The culture was professional and stable. Execution, in his view, was the variable—fragmented in places, slower than it needed to be, with too many handoffs between functions that each managed their own performance independently.

She absorbed each of these as coordinates on a map she was building as he spoke. She did not have enough information yet to know whether the map was accurate, but the outline was forming. A company whose direction was clear but whose ability to move in that direction had accumulated friction. Where the friction came from, and how deep it ran, was the question the next several weeks would answer.

When David had finished, she asked three questions. The first was about the architecture of the technology systems and how recently they had been materially updated. The second was about how performance was measured at the senior leadership level and whether those measures were individual or shared. The third was about the last time the organisation had made a significant structural change and how it had been received.

David answered each one. His answers were candid and more specific than she had expected at a first meeting. The technology systems were several years behind a meaningful update, a situation everyone understood and that had been subject to multiple business cases, none of which had secured full funding. Performance measurement was primarily individual, with team-level metrics added two years ago but not yet embedded in how leaders actually thought about their role. The last major structural change had been eighteen months prior, a reorganisation of the commercial function that had taken longer to settle than planned and left residual confusion about accountability in two areas that were still being resolved.

She listened, and did not tell him what the answers suggested to her. That was not what this conversation was for.

• • •

They agreed the engagement would begin formally on the first of the following month. Sara would have access to the full senior leadership team from day one. The assessment would be framed internally as due diligence for the product line recovery programme. She would work alongside the existing programme structure without being inside it. David would provide cover for the scope of her conversations wherever it was needed.

“One thing I’d ask,” David said as they reached the end. “The board session next week. I’d like you to attend. Not to present—just to observe. They’ll have the formal programme overview from Mark. I want you to hear how they frame the problem themselves.”

“Yes,” she said. “That will be useful.”

He stood and shook her hand again. The meeting had taken fifty-five minutes and had covered, she judged, roughly half of what needed to be established. The other half would surface over the coming weeks as the gap between the stated problem and the actual problem became more precisely visible.

• • •

She took the lift down alone and crossed the lobby without stopping. Outside, the late-morning air was cold and flat, the city moving at its usual pace around the building. She paused on the pavement for a moment and opened the notes application on her tablet.

She had done this at the start of every engagement for the last eleven years: a brief record of first impressions before the detail of the work began to revise them. Not conclusions—she did not draw conclusions from a single meeting with a CEO—but structural observations. The shape of what she had seen, before she had the language to explain it precisely.

She wrote four things. Strategy directionally clear, execution fragmented. Measurement individual, not systemic. Architecture several years behind the operating model it is supposed to support. Leadership generally aligned, incentives not tested.

She paused, then added a fifth: Board expects programme. Problem is structural.

She closed the application and flagged a car. The engagement was twelve months, fixed, with a mandate that had been drawn around one product line and a CEO who understood perfectly well that it would not stay there. They had hired her to fix a product, but the problem was already larger than that, and they both knew it, and neither of them had needed to say so directly. That was, in her experience, the best possible way to begin.