I was sitting in a room yesterday with a group of technical leads. It was an industry event, and the conversation was around projects that kept looping. Work would be done, reviewed, then redone. Adjustments would be made, only for the direction to shift again. Not because new data had emerged, but because the decision around what was actually being solved wasn’t clear.

There was a point in the conversation where someone mentioned that a large external firm had been brought in at significant cost, somewhere in the range of what these firms typically charge for strategic engagements, which can easily run into hundreds of thousands, and in many cases into the millions depending on scope and duration. What was striking wasn’t the spend itself, but the fact that the presence of the firm hadn’t settled the work. The cycle continued. Work was still being reworked. Direction was still shifting.

Sitting with that, it becomes difficult to interpret the situation as a simple gap in capability. The people in the room clearly knew what they were doing.

The issue wasn’t that the work couldn’t be done properly. It was that the work was being done inside a decision environment that hadn’t stabilized around what the problem actually was.

At senior levels, there is a kind of pressure that rarely gets spoken about directly, but it shapes how decisions are made all the same. The expectation is not just to decide, but to appear certain while doing so, to move in a way that signals clarity even when the situation itself may still be unfolding, and that expectation begins to influence how quickly directions are set and how firmly they are communicated, sometimes before there has been enough space to fully understand what is actually happening.

And in that context, there isn’t always room to openly explore uncertainty or to move through a sequence of smaller, contained experiments that would allow the real issue to surface more accurately. So what happens instead is that decisions get made at a level of abstraction that feels appropriate for leadership, but may not be sufficiently grounded in what is actually happening on the ground.

When those decisions meet the reality of implementation, the gaps begin to show, and the work starts to loop. Adjustments are made, but because the underlying problem hasn’t been fully clarified, each adjustment only partially resolves what is being encountered. It doesn’t show up as a clear failure, but more as continuous activity that keeps shifting without ever fully resolving into something stable or complete.

What becomes interesting in that context is
how the involvement of a large firm functions
within the system.

It does not necessarily need to produce a fully resolved solution to be considered a valid step in the process. The firms presence carries a different kind of value. It signals that the problem has been taken seriously, that expertise has been brought in, that due diligence has been exercised at a level that can be recognized internally and externally. The decision to engage them settles the optics around the situation, even if the underlying work continues to shift without reaching a clear resolution.

A smaller contractor entering that same environment is often evaluated differently, even if their proximity to the work allows them to see more clearly what is actually happening.

They are expected to be precise, to be correct, to demonstrate that their recommendation will work, but they are doing so inside a situation where the problem itself is still being interpreted in different ways at different levels of the organization. The expectation placed on the answer is high, while the foundation required to support that answer is still unsettled.

What becomes clearer when you look at this through the lens of value is that larger firms are not being selected purely for the outcome of the work. Their advantage sits in how their value is perceived before the work is even experienced. That perception has been built over time, across multiple engagements, industries, and leadership teams, to the point where it no longer needs to be established in the moment. It is already assumed.

This is where scale comes in, not just in terms of size, but in terms of how widely that perception has been reinforced. The more often a firm is seen operating at high levels, the more its presence begins to signal competence, seriousness, and safety, regardless of what any single engagement produces. That signal becomes part of the value being purchased.

So when a company brings in a large firm, they are not only buying a solution. They are buying what that firm represents inside the organization. They are buying the ability to say that the issue has been handled at a certain level, that the right people have been involved, that the process has been thorough. That carries weight in ways that are not always tied to the effectiveness of the final outcome.

A smaller contractor, no matter how capable, does not enter with that same accumulated perception. Their value has to be established within the conversation itself, which places them at a disadvantage before the work is even considered.

The comparison is not happening on equal terms, because one is being evaluated in real time, while the other is being recognized based on what has already been established elsewhere.

This is why better solutions do not always get selected.

The decision is not being made on solution quality alone. It is being shaped by how much value is already assumed before the solution is presented, and how that assumed value reduces the perceived risk of the decision.

For smaller contractors, this shifts what needs to be understood. Competing on the quality of the work is not enough if the value of that work is not already legible at the point of decision.

The question becomes how to bridge that gap, not by imitating scale, but by making the value of the work easier to recognize, trust, and act on without requiring the client to do that translation themselves. I’ll answer this in tomorrow’s edition of the Strategic Alignment Journal.

Strategic Reflection Prompt:

Where is the value of your work requiring the client to interpret, validate, or translate it before they can trust it enough to make a decision?

About Giselle

I’m Giselle Hudson, a Business Diagnostic Specialist. I work with leaders when something feels off — where results, decisions, or team response don’t match what was expected. I examine what’s shaping outcomes beneath the surface, so the next move is grounded, not reactive.

If this feels familiar, don’t rush your next decision. We can look at your situation properly before you take action.