Chapter 4 - The Executive Room

The executive meeting room on the fourth floor was larger than the one David had used for their initial conversation, and arranged differently. A long oval table occupied the centre, seats for ten, with a screen at one end and a second display panel mounted on the side wall showing a live feed of the key financial metrics. The room was set up with the efficiency of a place that ran formal sessions regularly: presentation clicker on the table, water at each place, a printed agenda folded once in the upper right corner of every pad. The overhead lighting had been adjusted to the slightly higher level that rooms used for screens, which gave the whole space a quality of readiness, of things about to be formally addressed.

Sara arrived three minutes before the scheduled start and took a seat along the side of the table, one position back from the end, where she could see both the screen and the faces of the people who would be presenting. David had indicated she would be introduced briefly and then left to observe. She had no slides, no prepared remarks, nothing that would signal she was there to do anything other than listen. That was exactly how she intended to begin.

The others arrived in quick succession over the next two minutes. She had read biographical summaries and photographs in advance, but photographs were always partial—they recorded appearance without registering how people occupied a room, which was usually more informative. Elena Kovacs came in first, set her folder on the table with a decisiveness that said she had done this many times and was already, functionally, in the meeting. Mark Reynolds arrived at the same moment, still carrying a brief exchange with someone in the corridor that he concluded with a nod before pulling the door closed. Anita Desai was already seated when Sara noticed her, having arrived during the moment Sara had been watching the door. James Whitaker came in last, slightly preoccupied, phone in hand, which he put face-down on the table with the deliberate gesture of someone reminding himself to be present.

David opened at exactly nine o’clock. He introduced Sara in two sentences—her role, her mandate, the fact that she would be observing today and working alongside the team from the start of the following month. No one responded to this with more than a brief acknowledgement. The introduction had been handled efficiently, which told her that the room had been briefed in advance and that the level of disclosure in that briefing had been calibrated to the minimum necessary. She filed this without expression.

• • •

Mark presented first. He had twenty-two slides and moved through them with the pacing of someone who had presented this material before, not reading it, but narrating it, which was a meaningful distinction. The first section established context: the precision controls market, its rate of growth over the previous five years, MontaraTech’s historical position within it, and the current performance of the product line relative to its targets. The numbers were familiar to Sara from the management accounts. The framing was not materially different from the performance review she had read prior to arriving in Boston, which meant that the internal view of the problem had not changed in the interval between that review and this session.

The second section covered the competitive landscape. Mark described four named competitors, their recent moves, and MontaraTech’s relative position against each. Two were characterised as lagging, one as comparable, and one—the German firm whose exhibition stand Sara had not seen but whose behaviour Tim Carter had described in the materials she’d read—as actively expanding its market positioning. Mark noted this last point as a development to watch, used the word “emerging” in relation to their threat level, and moved on to the next slide.

Sara noted that he had spent forty seconds on the competitor that represented the most meaningful change and five minutes on the two that were least likely to close the gap. This was not carelessness. It was a natural property of how people assessed threat: they spent time on what they could compare easily and moved quickly past what they could not yet fully characterise. The German firm’s shift toward integration and adaptability did not fit neatly into a performance comparison. It was doing something differently, not just doing the same thing better, and that was a harder thing to frame for a structured review.

The third section was the recovery plan. This was where Mark’s presentation shifted from description to proposal. The plan had five workstreams: product update acceleration, commercial re-engagement with lapsed customers, a pricing review for the mid-market segment, a talent assessment in the engineering function, and an enhanced governance structure to track progress across all four. Each workstream had an owner, a timeline, and a set of milestone metrics. The structure was thorough and the ownership was clear. The board, Mark noted, had already reviewed and provisionally approved the framework pending confirmation of resourcing.

Sara listened to all of this and wrote two words on her pad. She did not look at them again during the presentation.

• • •

Elena spoke next, briefly, on the operational dimension. Her tone was different from Mark’s—less narrative, more declarative. She had reviewed the delivery timelines across the five workstreams and had two concerns about sequencing. The product update workstream assumed that engineering resource would be available from the first of the month, which conflicted with a pre-existing commitment in the same function related to a different product line. This had been flagged in planning but not yet resolved. She expected it to be resolved within two weeks, and she was tracking it.

Her second point was about the governance structure Mark had proposed. Five workstreams, each with independent ownership and independent reporting lines, would generate five separate status updates per cycle. She was recommending consolidation into a single programme report with a unified owner to avoid duplication and ensure that cross-workstream dependencies were visible in one place. Mark agreed with this in principle. The question of who the unified owner would be remained open.

The exchange between Elena and Mark was efficient, professional, and entirely focused on the mechanics of delivery. Neither of them mentioned the customers or the competitive environment that Mark had described in the first section of his presentation. The transition from diagnosis to plan had been clean and rapid, and the room had followed it without apparent friction. Sara watched the move and held it.

Anita’s contribution was short. She confirmed the financial parameters: a budget envelope that had been approved for the programme, a quarterly review mechanism to assess spend against outcomes, and a set of financial metrics that would be used to measure recovery. She noted, in the measured tone she applied to most things, that the metrics were output-focused rather than leading indicators, and that if the team wanted to add trajectory measures to the reporting, she was open to that discussion at the next cycle.

Sara registered the phrase “trajectory measures”. Anita had used it as a side remark, a suggestion for a future agenda item rather than a present concern. But the instinct behind it was precise. Output metrics told you what the programme had produced. Trajectory measures told you whether the organisation was moving in the right direction. The distinction was exactly the one the performance pack had not made. Sara looked at Anita with a slightly increased attention.

James spoke last, and briefly. The technology systems that supported the precision controls line had been a subject of discussion for two years, he said, and there were known constraints in the integration layer that affected how quickly certain product updates could be deployed. He had a team looking at options. He did not want to overstate the impact on the programme timeline, but he wanted it on record that architecture would be a factor in the product update workstream and that the timeline Mark had proposed assumed a degree of system flexibility that had not yet been confirmed.

Mark said he was aware of the technology question and had factored in a buffer. James said the buffer might be optimistic. David said the two of them should align on this offline before the next session. Both agreed. The issue was set aside.

• • •

The meeting had been running for just under an hour when David indicated that the floor was open for questions before they closed the session. Sara waited for a moment to see whether anyone else would speak. No one did. She set down her pen.

“The commercial re-engagement workstream,” she said, looking at Mark. “When a deal in that pipeline reaches the point of contract or configuration, which function owns the decision?”

Mark replied without hesitation. “Commercial leads on contract. Product on configuration.”

“And when the customer’s configuration requirement touches the technology platform?”

A brief pause. “That’s a conversation between product and technology.”

“Is there a defined process for that conversation?”

This time the pause was slightly longer. James answered. “We have an escalation process. If the configuration requirement is outside standard parameters, it comes to a joint review.”

“How long does that review typically take?”

James glanced at Mark. Mark said: “It varies. Two weeks in straightforward cases. Longer if it requires a technical assessment.”

“And in the customer conversations you’re planning to re-engage, how many are likely to have configuration requirements outside standard parameters?”

There was a longer pause. Elena said, quietly and without particular inflection: “Most of the lapsed ones.”

No one added anything to that for a moment. Sara did not press it. She had not asked the questions to create a problem in the room. She had asked them to establish, quietly and with evidence that the room had supplied itself, that the plan contained a dependency which the plan itself had not addressed. The two-week review process, applied to most of the commercial re-engagement targets, would not sit within the programme timeline as drawn.

David said they would pick this up in the workstream-level planning. Mark agreed. The moment moved on.

• • •

David closed the session at ten forty-five. He summarised the agreed actions in three clear points, thanked the team, and indicated the next formal session would be in two weeks. The room began to clear with the same purposeful efficiency with which it had assembled, conversations continuing into the corridor, the logistics of the working day reasserting themselves immediately.

Sara remained in her seat as the room emptied and turned her pad over to look at the two words she had written during Mark’s presentation.

They said: “assumed system.”

It was what she had seen in the plan and in the discussion around it. Not incompetence. Not poor analysis. A plan built by serious, capable people who had framed a problem carefully and proposed a structured response to it. The strategy was directionally sound. The workstreams were logical. The ownership was defined. The governance was, as Elena had already noted, being tightened to improve coordination.

But the plan worked only if the organisation behaved the way the plan described it. It assumed that product and technology could resolve configuration questions within a timeframe the plan required. It assumed that commercial re-engagement would not stall at the point where the customer asked something that required a cross-functional decision. It assumed that the engineering resource would be available when the timeline needed it to be. Each of these assumptions was reasonable in isolation. Together, they amounted to a picture of an organisation operating with more internal fluency than Sara had any evidence it actually possessed.

The question it had not asked was the one that would matter most: not whether the plan was logical, but whether the organisation was capable of executing it without the system slowing it down. That was a different question entirely, and it was the one the assessment would answer.

Elena appeared in the doorway. She had come back for something she had left on the table, and stopped briefly when she saw Sara still seated.

“Good questions,” she said, in a tone that was neither warm nor cold—simply factual, like most of what she said. Then she picked up her folder and left.

Sara looked at the blank screen at the end of the room and at the agenda still folded on the pad in front of her, and thought about what the morning had established. The plan was real and the team was competent and the intent was genuine. The plan made sense, as long as the organisation behaved the way it had been described. Whether it did was a question that no one in that room, including David, could yet answer. That was what twelve months was for.