She had already submitted the bids by the time we talked about it, and there wasn’t anything in front of her that required a reaction. The work had already started on two of the projects, and the third had gone a different direction. Nothing about it carried urgency. There wasn’t a problem to solve in that moment, which is part of what made it harder to see.
From the outside, it looked like a normal stretch of business. Work had been won. Jobs were moving. Nothing had stalled or fallen apart. If you were only looking at outcomes at a surface level, there wouldn’t have been a reason to stop and question anything. It didn’t present itself as a situation that needed to be reexamined.
She walked through how she had approached the bids, and the way she described it didn’t feel uncertain or defensive. It sounded like something she had done enough times that the process no longer required much effort to explain. She had reviewed the plans, worked through the numbers the way she always had, made adjustments based on what she was seeing, and submitted them. There wasn’t hesitation in how she talked about it. It followed a path that had worked for her repeatedly, and she moved through it the same way she always had.
Nothing in that explanation felt off. There wasn’t a point where you would have interrupted her or pushed her to rethink something. It made sense inside the way she had been operating, and it matched the results she had been getting up to that point. If anything, it reinforced that she was doing what she knew how to do well.
The shift didn’t show up in how the decisions were made. It showed up in how they held once they were moving.
Two of the bids were accepted, and the work moved forward without friction at the start. Crews were scheduled, materials were ordered, and everything stepped into motion the way it should when something has landed correctly. There wasn’t resistance from the client side, and there wasn’t anything that would signal that something had been missed. It looked like a clean transition from decision to execution.
As the projects progressed, the space inside them started to feel different than what she was used to. It wasn’t obvious in a way that would cause alarm, and it didn’t create a situation that forced immediate correction. It showed up in smaller ways that didn’t point back to a single cause. There was less room inside the work than she had expected, and things that would normally absorb themselves started requiring attention.
It didn’t disrupt the projects, but it changed the way they felt to operate inside.
The third bid didn’t create a disruption either. It was declined without much explanation, and the client moved forward with someone else. There wasn’t a disagreement to work through or a negotiation that would bring clarity. It just shifted away from her without leaving anything behind to analyze directly.
None of this forced a moment where something had to be addressed. The business continued forward, and the work kept moving. If you stayed at the level of activity and output, it all looked intact. There wasn’t anything in the results themselves that demanded a deeper look.
What changed didn’t show up in the work first. It showed up in how she experienced it.
She said it in a way that didn’t try to make it significant. “I’m starting to second-guess myself.”
There wasn’t tension behind it, and it didn’t come with an explanation. It was more of a recognition than a reaction. The same way of making decisions that had worked for her before no longer felt as stable once the work was underway. The process hadn’t changed, but the way it held inside real conditions had.
That’s where most people would start trying to fix something, because that’s the first place it feels like there’s something to correct. The instinct is to go back into the decision itself and refine it. Rework the numbers, adjust the approach, build more structure around how it gets done so it produces a more predictable outcome next time. All of that sits right there as an obvious next step.
But none of that actually explains what happened.
The decisions themselves didn’t fall apart once they were made. They were accepted, and they moved directly into execution. There wasn’t a breakdown between the moment of decision and the start of the work. Everything transitioned the way it should if the decision had been solid.
And still, they didn’t hold.
There wasn’t a point where something failed in a way that you could isolate and correct. There wasn’t a moment you could return to and say that’s where it shifted. The bids didn’t collapse under pressure, and they didn’t trigger anything that forced them to be revisited.
They simply didn’t carry the way they needed to once they were inside something larger than what she had been operating in before.
That kind of problem doesn’t present itself clearly, because it doesn’t interrupt anything. It sits underneath what is happening and changes how it behaves over time. It creates a difference between what the decision was supposed to produce and what actually happens once it is in motion, and that difference doesn’t demand attention right away.
What makes it harder to see is that everything around the decision continues to function. The team doesn’t push back on it, and they don’t reinterpret it in a way that would expose a gap. They take what has been decided and move forward with it. The work continues, and nothing about it signals that something is off if you’re only looking for disruption.
There isn’t resistance to point to.
There also isn’t anything underneath the work that is reinforcing the decision once it leaves the person who made it.
No one is actually carrying it.
Not in the sense of responsibility on paper or roles inside the organization, because those are still there. People are assigned, and the work is being managed. The structure that should hold the work is in place, and nothing about that structure appears broken.
What’s missing is something else.
The reasoning behind the decision, the way it was meant to function as conditions changed, the understanding of what it needed to produce and how it needed to be held as the work moved forward, didn’t exist anywhere outside of her. It stayed with her at the point the decision was made, and it didn’t transfer into the work in a way that allowed it to be maintained once it was underway.
So once the projects moved past the point of the initial decision, nothing was actually holding that decision in place. It wasn’t being revisited against what was happening in real time, and it wasn’t being strengthened by someone who understood it deeply enough to keep it aligned.
It continued forward, but it wasn’t being carried. It was being followed.
Following something allows work to continue without interruption, but it doesn’t preserve what the decision was meant to do once conditions start to shift. It keeps things moving in the direction that was set, even if that direction no longer fits what is happening inside the work.
Carrying something requires a different level of involvement, because it means someone is staying with the decision as it moves, not just executing against it. It means someone is paying attention to whether it still fits, whether it still produces what it was intended to produce, and whether it needs to be adjusted in order to hold under pressure.
Without that, the decision doesn’t break.
It drifts.
The effects of that drift don’t show up all at once, and they don’t point back to a single cause. They accumulate in ways that are easy to miss if you are looking for something obvious. The work becomes tighter than expected, and the pressure inside it becomes more constant. Outcomes start to feel slightly off, but not enough to create a clear correction point.
That’s when something internal starts to shift.
Not because something failed in a visible way, but because what used to feel stable no longer does. The same approach that had worked before doesn’t create the same confidence once it is exposed to a different level of complexity. The ground underneath it starts to feel like it can move, even if nothing has actually broken.
That’s a difficult place to recognize for what it is, because it looks like the answer should be better decisions.
More accurate. More informed. More structured.
That response assumes that the strength of the decision itself is what determines whether it holds.
In her situation, the decisions did exactly what they needed to do at the moment they were made. They created movement, they were accepted, and they produced work. Nothing about them failed at that point.
What they didn’t have was anything that could carry them once they were in motion at that level.
So the problem wasn’t in how the decisions were made.
It was in what existed around them after.
That doesn’t get solved by refining the decision-making process, because that only strengthens the moment the decision is made. It doesn’t change what happens once that decision leaves that moment and enters into something that requires it to be held over time.
That changes when decisions stop existing as something one person arrives at and everyone else operates under, and start becoming something that is actually understood and carried by more than one person once they are put into motion.
That shift doesn’t show up clearly when it happens, and it doesn’t present itself as a change in process. It shows up later, in whether what was decided actually holds when it is exposed to real conditions.
Most of the time, when it doesn’t, nothing points back to that. It just feels like something that used to work doesn’t work the same way anymore, and the instinct is to fix what was done instead of looking at what was missing.
And if that doesn’t get seen, the next decision gets made the same way. It moves forward the same way.