Chapter 6 - The Assessment Decision

She had asked David for an hour with his direct leadership team. Not the full executive session from the previous week—no screens, no prepared materials, no agenda circulated in advance. Four people around a table: David, Elena, Anita, and Mark. The request had been noted without comment. The meeting had been arranged for eight-thirty on a Thursday, using a small room on the third floor that was, Sara suspected, chosen precisely because it had no glass wall facing the atrium.

She arrived before the others and did not sit down. She stood at the window, which faced a narrow internal courtyard, until she heard the door open and the four of them came in more or less together—a coincidence of corridor timing rather than coordination. They took their seats with the contained alertness of people who had been told the meeting was important and had formed their own views about why.

Sara sat. She did not open a folder or place anything on the table. She looked at the four of them for a moment and then began.

“I want to tell you what I’m going to do and why, and then I want to hear your questions.” She paused for a moment to let that framing settle. “I’m not going to begin with the programme. I’m not going to begin with workstreams or milestones or a governance structure. I’m going to begin with a diagnostic. Specifically, a Five Levers assessment across the organisation.”

Mark spoke first. “We’ve already done significant analysis on the product line. We know where the issues are.”

“I’ve read that analysis,” Sara said. “It’s thorough within its scope. The question is whether the scope is right.”

“We were brought in to fix the product line,” Mark said. Not aggressively, but with the precision of someone drawing a boundary they considered legitimate. “If the scope expands, that changes what the programme looks like and how long it takes."

“I’m not expanding the programme,” Sara said. “I’m understanding the system before the programme begins. Those are different things. If the assessment confirms the product line’s issues are self-contained, the programme proceeds as planned. If it doesn’t, we’ll have evidence to that effect, and we’ll be able to act on it rather than finding out twelve months from now.”

Anita had been listening with the focused stillness she brought to conversations involving budget implications. “What does the assessment involve, practically?”

“Structured conversations across senior leadership and a layer below. Document review. Observation where it’s relevant. The Five Levers assessment is a recognised instrument—I’ve used it in eight engagements. It covers strategy, leadership, culture and people, execution, and architecture. It gives the organisation a clear picture of how it functions across all five dimensions, not just the one that’s currently in the frame.”

“How long?” Anita asked.

“Three weeks to complete the fieldwork. One week to assemble the findings. Readout at the end of week four.”

Anita glanced at David briefly, then back to Sara. “That’s a month before the programme begins. The board’s expectation was visible progress within ninety days.”

“I know what the board’s expectation is,” Sara said. “Spending a month understanding what’s actually constraining the product line before acting on it is not a delay. It’s the difference between acting on the right problem and acting on a description of the problem. At month four, I’d rather have lost a month to clarity than have a programme running fast in the wrong direction.”

• • •

Elena had not spoken yet. She was watching Sara with the attentiveness of someone forming a view rather than waiting for a turn to speak. When she did, her question was precise.

“When you say across the organisation—how far does that extend?”

“All the functions connected to the precision controls line, directly or through dependencies. Product, commercial, technology, operations, finance. Senior leadership in each. Some depth below that where it’s relevant.”

“That’s most of the business,” Elena said.

“Yes,” Sara said. “The product line touches most of the business. That’s part of what we need to understand.”

Elena was quiet for a moment. Her concern was not about the assessment’s scope in principle, Sara judged, but about what it would produce in practice—which parts of the organisation’s operation would come into view, and what the implications of that visibility might be for work already in progress. This was a reasonable concern. It was also not a reason to proceed differently.

“The assessment isn’t an audit,” Sara said, addressing the concern without being asked to. “It’s not looking for failures or assigning accountability for historical decisions. It’s mapping how the system operates so we can understand what’s constraining the product line’s performance. The output is a picture, not a verdict.”

Elena gave a slight nod. Not agreement, exactly—more a confirmation that the distinction had been registered.

• • •

Mark had another question. “Who’s involved in the conversations? If this is going to senior leadership across multiple functions, people will start to form views about what it means. That creates noise.”

“It will create questions,” Sara said. “That’s different from noise. People will ask what the assessment is for, and they should be told: it’s to understand how the organisation operates in relation to the product line recovery. That’s accurate and it’s sufficient. What I’d ask is that none of you pre-frame the purpose beyond that. The assessment works because people answer what they’re asked, not what they think the questioner wants to hear.”

“What if people are uncomfortable?” Mark asked.

“They usually are,” Sara said. “It passes. The discomfort comes from being asked to describe the organisation as it actually operates rather than as it appears in reporting. That’s informative in itself.”

Anita set down her pen. “I want to be clear about the cost envelope. If this runs to four weeks and involves the level of senior time you’re describing, the cost is non-trivial. Is that within the contracted scope?”

“The assessment is within my engagement terms. The cost to the organisation is senior leadership time—two to three hours per person across twelve to fifteen individuals. I’d ask you to treat that as a programme cost.”

Anita absorbed this without further comment. Her concern had been financial and it had been answered financially. She would not object further until the numbers gave her a reason to.

• • •

David had not spoken since Sara had opened. He had listened to the exchange around the table in the manner of someone who had already made a decision and was allowing the conversation to reach its own conclusion. When the questions had settled, he looked at each of the others in turn before he spoke.

“The assessment proceeds,” he said. Not as a resolution of the discussion, but as a confirmation of a position he had already held. “Mark, I’d ask that the programme planning continues in parallel—no delay—but we don’t commit formally to the workstream design until we’ve seen the findings. Four weeks is manageable. If the assessment confirms the current framing, we’ve lost nothing. If it changes it, we’ll have avoided building on the wrong foundation.”

Mark gave a brief, composed nod. The response was controlled—the nod of someone who had registered the decision and was already recalibrating rather than continuing to resist it. Sara had seen this before. Mark was not someone who fought decisions once they were made. He would work within the new frame and make it his own. That was, in its way, a useful quality.

“I’ll need confirmed diary time from each of you within the next three days,” Sara said. “Two-hour sessions, individually. My first conversations will be with the four of you. After that I’ll move to the broader leadership group and connect functions as the picture develops. I’d ask that the conversations remain confidential until the readout—not because the content is sensitive, but because I need people to speak freely without calibrating their answers to what they think others have said.”

Elena spoke. “What do you need from operations specifically?”

“Access to the team leads in your area who touch the controls line directly, and to any process documentation covering the handoffs between operations and product. I may also want to sit in a working session—not to observe formally, but to see how the team operates in practice rather than how it’s described.”

“I can arrange that,” Elena said. This time there was no qualification in it. She was, Sara observed, someone who made decisions cleanly once the information was sufficient. Her hesitation at the start of the meeting had been about what she did not know. The questions had reduced what she did not know, and she had adjusted accordingly.

• • •

The meeting ran to fifty minutes and ended without a formal close—the conversation simply reached the point where the decision was clear and the remaining questions were logistical rather than substantive. People gathered their things and left in ones and twos. Mark paused briefly at the door and said, without particular emphasis, that he would send his availability by end of day. Anita left without additional comment. Elena and David exchanged a few words in the doorway that Sara did not attempt to overhear.

When the room was empty, Sara opened her tablet and began building the interview schedule. She had the four of them first, in the sequence that would give her the most useful context for each subsequent conversation. Then the layer below: function heads, programme leads, the people who sat closest to the cross-functional boundaries where the constraints were most likely to show themselves clearly. She estimated twelve conversations before she would have enough to see the full pattern, and possibly three or four more to test it.

She had run this process enough times to know how it would go. The first few conversations would be cautious—measured answers, careful language, the instinct to present the organisation at its best. By the middle of the second week, as people understood she was not evaluating individuals but mapping a system, the conversations would open up. They always did. People inside an organisation always knew more about what was constraining it than they had been given a formal opportunity to say. The assessment gave them the opportunity, and they took it.

By the end of week three she would have a picture. It would not be complete—assessments never were—but it would be structured, evidence-based, and assembled from the organisation’s own account of itself. That was what made it difficult to dismiss. Not because she would argue for it, but because the people inside the organisation had effectively built it.

She confirmed the first four slots in the schedule, flagged them to David’s assistant, and closed the tablet. The room was quiet and the courtyard outside the window was grey with mid-morning cloud. The work had not started with change. It had started with something quieter and, in her experience, considerably more difficult: the process of making an organisation visible to itself, before it had decided whether it wanted to look.