Chapter 5 - The Five Levers Lens

The hotel room was twelve floors above the street and quiet in the way that well-constructed rooms in business hotels are quiet—not silent, but buffered, the city audible only as a low, undifferentiated hum that registered as atmosphere rather than sound. Sara had eaten at the desk while reviewing her notes from the day and had moved to the chair by the window when the notes were finished, her tablet balanced on her knee, the city lights below her providing the kind of ambient presence she found useful when she needed to think without distraction.

She had been doing this for eleven years—working through a new organisation in her mind in the hours after the first substantive day, building the picture before the details accumulated and made the pattern harder to read. The picture was always clearer at the beginning, when the signals were fresh and before the daily motion of an engagement began to close off the wider view. Later there would be data, interviews, documents, meetings, more meetings. Now there was only what she had seen and heard, which was often enough to understand the essential shape of a problem, even if the shape still needed verification.

She opened a blank document on her tablet and began.

• • •

She started, as she always did, with strategy. Not because it was always the most important lever, but because it was the one organisations found easiest to articulate and therefore the one most likely to appear more coherent than it actually was.

MontaraTech’s strategy was clear. That was not the question. David had described it accurately, and Mark’s presentation had confirmed it: a precision controls business serving industrial customers who valued engineering quality and technical depth, differentiated by the sophistication of its products and the depth of its customer relationships. The direction was logical, the market real, the positioning historically effective. There was nothing obviously wrong with any of it.

But clarity was not the same as distinctiveness, and distinctiveness was not the same as sustained distance. What Sara had heard in the strategy was a description of where the company had been positioned, not an account of how that position was being actively maintained against a field that was moving. The German competitor that had shifted its framing toward integration and adaptability had not done so carelessly. It had read the same market signals MontaraTech’s customers were sending—the same questions Tim Carter had been carrying since the exhibition—and had reorganised its offer around them. MontaraTech had not. Its strategy was sound as a static position. As a maintained position, it had begun to drift.

She typed a single line under the heading and moved on.

• • •

Leadership was harder to assess from a single session. She had seen David facilitate, and she had seen the others respond to him. What she had not yet seen was how leadership functioned when the formal structure was not in the room—how decisions were actually made at the boundaries where functions met, where accountability was less clean, where the question of who owned a problem was genuinely ambiguous.

What she had observed gave her a starting position. David was measured and deliberate, a facilitator by temperament and probably by choice—someone who created space for others to operate rather than filling it himself. This was not a weakness. In some contexts it was exactly the right model. In an organisation where alignment was genuine and execution was fluid, a CEO who held direction without micro-managing it was an asset. The question was whether the space he created was being filled purposefully or whether it was simply filling itself with the path of least resistance.

The exchange between Mark and James that David had resolved by deferring to an offline alignment suggested the latter. When two senior leaders disagreed about a dependency that sat directly on the critical path of the programme they were discussing, the correct response was not to schedule the conversation for later. But the room had accepted the deferral without friction, which meant it was a familiar pattern rather than an exception. Decisions that crossed boundaries were not being made in the room where the boundary was visible. They were being moved to bilateral conversations that happened downstream, out of sight, resolved in ways that the wider team could not see or adjust to.

In a fast-moving organisation, that pattern created invisible drag. Decisions deferred became decisions delayed. Delays accumulated. The programme ran behind its own timeline before it had properly started, and nobody could explain exactly where the time had gone.

She typed another line.

• • •

Culture was the lever that organisations were most likely to underestimate and most likely to describe incorrectly. When people described their culture, they described their aspirations or their self-image, not always the actual pattern of behaviour that the organisation reproduced daily. The two were rarely identical.

She had not had enough exposure to MontaraTech to characterise its culture precisely. But she had observations. The performance review Tim had attended—which she had read about in the briefing materials—had discussed the precision controls underperformance in terms of timing, transition, and contained causes, and the room had received that framing without challenge. The executive session had proposed a five-workstream programme and received it with the composed agreement of a team that was more comfortable with structure than with uncertainty. Elena’s concern had been about consolidating governance, not about whether the plan itself was correctly aimed. Mark had answered questions about execution mechanics without once returning to the customer signals he had presented at the start of his own slides.

These were not failures. They were cultural preferences, operating invisibly as a set of defaults. The preference for containment over expansion. The preference for structured response over open inquiry. The comfort with familiar tools, familiar language, familiar problem shapes. Organisations that had been successful for a long time developed these preferences naturally, because the tools and language and problem shapes that had worked before were the ones people reached for instinctively. They worked, until the environment changed faster than the instinct updated.

She typed her third line and moved on.

• • •

Execution was where the visible symptoms were located, and also the area most likely to be misdiagnosed as a result. When organisations experienced delivery problems, the instinct was to look for execution failure—poor planning, under-resourced teams, unclear ownership, insufficient governance. The response was usually more governance. More tracking. More accountability structures layered over the existing ones.

MontaraTech’s plan had added a governance layer. Elena’s suggestion to consolidate the five reporting lines into one was sensible at the margin. Neither would change the underlying pattern, because the underlying pattern was not about visibility or accountability. It was about how work actually moved across the organisation when it crossed functional boundaries.

The questions she had asked in the session had exposed a specific version of this. A customer configuration requirement that was non-standard—which, as Elena had noted, applied to most of the lapsed accounts they were planning to re-engage—passed through commercial, then product, then technology, at each handoff entering a new function with its own priorities, its own backlog, its own definition of what constituted urgency. The escalation process James had described was real. The two-week review timeline was probably optimistic under realistic conditions. And nowhere in the programme plan had anyone assigned clear ownership to the cross-functional path itself, as opposed to the individual functional steps within it.

This was not a failure of intent. The people involved were capable and motivated. It was a failure of design. The organisation had been structured around functions, and functions had been optimised to manage their own performance. End-to-end performance—the speed and reliability with which work moved from customer requirement to delivered outcome, across all the functions it touched—was not owned by anyone in particular. It was the residual of everyone doing their part reasonably well. And when everyone doing their part reasonably well still produced slowness and friction, the system looked for individual causes rather than structural ones.

She typed her fourth line.

• • •

Architecture was, in her experience, the lever that took the longest to acknowledge and the one that caused the most consistent underestimation. Technology systems were not visible to most of the people whose work they shaped. They were infrastructure in the truest sense—present only when they worked, conspicuous only when they failed. The people who understood them best, like James, tended to operate in a register that was too technical for most leadership discussions. The people who needed to make decisions about them, like Mark, tended to treat architecture as a constraint to be managed rather than a variable to be addressed.

James had said the right things. He had flagged the integration constraints clearly and without overstating them. He had noted that the product update timeline assumed system flexibility that had not been confirmed. He had not, she observed, proposed a solution—because the solution to a several-years-old technology constraint was not something that could be committed to in the context of a product line recovery programme. It required a different conversation, a different level of investment, a different frame for what architecture was for.

The technology systems, as James had framed them, were capable. They functioned. They had been built to support an earlier version of the organisation’s operating model, and they did that adequately. What they did not do was enable the organisation to move at the speed or with the flexibility that the current strategy required. Every time the business needed to respond quickly to a customer requirement, or integrate two functions that had previously operated independently, or adjust a product configuration faster than the update cycle allowed, the architecture became a constraint. Not a catastrophic one. A frictional one. Something that slowed everything down by a small amount, which at scale and over time became something that slowed everything down by a significant amount.

She typed the fifth line.

• • •

She read back what she had written. Five lines. Each one a sketch of a pattern rather than a conclusion, deliberately held at the level of hypothesis rather than diagnosis. She had learned the hard way, early in her career, the cost of arriving at conclusions before the evidence was gathered. It was not that the conclusions were usually wrong—they were often right, and that was part of the problem. Arriving at the right answer too early was indistinguishable, in an organisational context, from arriving at any wrong answer: the people who needed to act on the conclusion had not been part of building it, and so they had no particular reason to believe it.

What she had in front of her was a picture of an organisation experiencing what she thought of simply as viscosity. The term had no formal status—it was not in the literature she had read or the frameworks she had trained in. It was simply the word she used, privately, for the property of a system that resisted movement. Not dramatically, not catastrophically, but persistently. A system where friction accumulated at the boundaries, where handoffs slowed, where decisions diffused rather than resolved, where good people operating competently still produced outcomes that were slower and harder than the effort warranted. The organisation was not broken. It was viscous. And viscosity, left unaddressed, was sufficient on its own to close the distance between a company and its competitors.

She looked at the five lines again and thought about the recovery plan the executive team had agreed to pursue. Five workstreams, clear ownership, enhanced governance, ninety-day milestone targets. Each of the workstreams would make a difference at the local level. The product update would improve the product. The commercial re-engagement would generate pipeline. The pricing review would recover margin in the mid-market. All of it was real work that needed doing.

And none of it would change the system the work had to move through. The product update would still encounter the architecture constraint. The commercial re-engagement would still stall at the cross-functional configuration handoff. The governance enhancement would produce better reports without producing better flow. The plan would generate activity, and the activity would generate some improvement, and the improvement would be reported as evidence that the programme was working, and then at some point—six months in, eight months in—the rate of improvement would plateau, and the team would begin the familiar process of looking for additional causes within the boundary of the plan they had already agreed.

She had seen this before. Not once, but many times. The local fix applied to a systemic problem produced local improvement and systemic persistence. The system absorbed the fix. The underlying constraint remained, and so the underlying problem remained, expressing itself in whatever area the fix had not reached.

• • •

The question was not whether she was right. She had enough experience to hold her current read of MontaraTech with reasonable confidence. The question was what to do with it. And the answer to that was not complicated, though it was sometimes difficult to execute: she needed the organisation to be able to see what she could see. Not to be told it. Not to be presented with her conclusions in a way that invited debate about whether her conclusions were correct. To see the evidence itself, gathered systematically, and to arrive at the picture through their own confrontation with it.

This was what the assessment was for. It was not, in her usage, a diagnostic exercise in the sense of an investigation by an external party that then delivered findings. It was a structured process for making a system visible to itself. The Five Levers gave it shape: a consistent set of questions applied across all five dimensions, with enough breadth to capture the whole organisation and enough depth to find the pattern beneath the function-level explanations. The output was not opinion. It was evidence—gathered from the people inside the organisation, using their own words and their own examples, assembled into a picture that was difficult to dispute because the organisation had effectively produced it itself.

She closed the document, set the tablet on the table beside her chair, and looked out at the city for a moment.

The precision controls line was underperforming because the organisation could not yet move at the speed the market required. The organisation could not move at that speed because it had been built for something else—for a more stable environment, a slower competitive field, a customer base that valued what the company had always offered rather than what it was being asked to become. None of this was a failure of the people inside it. It was the organisation behaving exactly as it had been designed to. The design was the problem, and the design would not change without a clear account of what it was producing. That account needed to begin tomorrow.