The Break Can Start Before the Outcome Changes


Earlier this year, across a few deal reviews, I kept noticing a similar kind of situation. The details here combine several conversations rather than describe one customer account, but the pattern was consistent enough to stay with me.
The deal was still active.
Nobody had said no. Meetings were still happening. Technical questions were being answered. People were positive about the problem. Senior people were involved. There were actions after every call and enough activity to make the opportunity look healthy from a distance.
But it was taking more work to keep the same level of confidence in place.
An issue that had felt important early on had become one priority among several. Ownership moved as more people entered the discussion. The explanation changed slightly depending on who was repeating it. A timetable that had once sounded like a date became something closer to “once we have alignment”.
None of those things, on their own, meant the deal was failing.
Then one week it was marked as stalled.
The interesting part was that almost nothing happened that week.
The stall gave a name to something that had been getting harder for a while.
For a long time, I tended to start at the visible event. If a deal stalled, I looked at the late-stage conversations. If a customer lost confidence, I looked at what had just been said. If more senior scrutiny appeared, I assumed the important question was why the deal now needed more scrutiny.
I am less convinced by that starting point now.
Sometimes the outcome is not where the break begins. It is where the break becomes visible.
When the outcome finally gets a name
Once the outcome is visible, everyone has something concrete to agree on.
A deal moves or it does not. A deadline is met or missed. A customer escalates. A system alerts. A project needs intervention. At that point everyone has something concrete to point at.
Before that, the picture is usually less tidy.
One person sees a normal delay. Another sees procurement. Someone thinks the technical case needs more work. A senior seller thinks the customer simply needs another conversation. Each explanation can be reasonable.
And the work keeps moving.
Another call is booked. Another document is produced. Somebody senior joins. The technical team answers more questions. The forecast is reviewed again.
That activity can make it difficult to see that something underneath it has changed.
That visible failure is often the first moment everyone agrees there is a problem. So it is easy to treat it as the beginning.
But sometimes it is simply the point where an earlier weakening can no longer be carried by the people around it.
What was already getting harder?
This is the question I find myself asking more often now.
Not just: when did the result fail?
What had already started requiring more effort before the result failed?
In a commercial situation, that might be the movement of meaning. Something that made sense in the first conversation has to pass through more roles, priorities and interpretations. Each handoff is manageable, but someone has to reconstruct a little more of the original context each time.
Ownership can be where the strain shows up. The people closest to the problem are not always the people who can make the decision, and the decision-makers do not feel the consequence in quite the same way.
Or it can show up in confidence. The underlying case is still there, but keeping the same level of belief now takes more proof, more qualification or more senior involvement.
And sometimes experienced people are quietly holding the whole thing together. They know how to explain the issue, restore context, answer the awkward question or reconnect the discussion when it drifts.
None of those conditions proves that failure is coming.
Senior involvement can be exactly the right thing. A buying group may simply be doing proper diligence. Specialist mediation may be the operating model. Complex work often needs more explanation as it progresses.
So the useful signal is not “more effort equals failure”.
The question is whether the extra effort is adding necessary substance, or repeatedly rebuilding something that used to carry itself.
That is a much less dramatic moment than a stalled deal.
It is also much easier to miss.
Earlier does not mean predictable
A very different piece of work sharpened this for me.
In the Preventing the AI Black Swan material, we explored a technical argument that an alert can arrive after instability has already formed and moved through parts of a system that were difficult to see at the time.
That was a technical argument, and I do not want to stretch the analogy. A buying process is not a distributed software system.
But it changed the question I was asking.
The visible event and the beginning of the condition do not always have to be the same moment.
But none of this gives us a reliable way to see failure coming.
Hindsight is very good at making the past look organised. Once something has gone wrong, every delayed response, awkward meeting, change of owner or technical anomaly can suddenly look like an obvious warning sign.
Some of those things will have mattered. Some will have been noise.
And some failures really are sudden. A budget disappears. A competitor changes the decision. Leadership changes. A component fails. A regulation alters the situation. Yesterday’s reasoning can become irrelevant very quickly.
So I do not think the answer is a longer checklist of early warning signs.
The better question is where the work started to require more reconstruction than it had before.
The work of compensation
This is where I think it becomes easier to spot in practice.
More explanation.
More artefacts.
More senior involvement.
More specialist interpretation.
More reviews.
More effort to keep the same thing moving.
I would not over-read that. Compensating behaviour tells you that support is being provided. It does not tell you why.
If a deal only moves when one senior person is in the room, that person is carrying something important. The reason could be weak messaging, a new category, poor qualification, insufficient proof, a genuinely complex decision or simply the customer’s preference for senior access.
If an operational issue is repeatedly restored by the same expert, that expert is carrying judgement the current process depends on. Whether that is fragility, deliberate specialism or sensible escalation still has to be understood.
The compensation is not the diagnosis.
But it is often worth noticing before the final outcome becomes the only thing anybody examines.
Before you fix the result
When something finally goes wrong, the natural response is to repair it.
Recover the deal. Stabilise the service. Rebaseline the project. Change the message. Add the control. Escalate ownership.
Sometimes that is exactly what is needed.
The danger is that the visible result grabs all the attention, so nobody goes back to the point where the work first became harder to carry.
A deal gets rescued, but nobody asks why it needed progressively more rescue.
A system is restored, but nobody asks when the operational picture stopped being as stable as it looked.
A project is rebaselined, but nobody asks when activity stopped being a useful indication that the underlying decision was actually moving.
That is what I now want to understand before reaching for the fix.
When did the value still move without somebody having to reinterpret it?
When was ownership still clear without another alignment meeting?
When did the operational picture still make sense without somebody reconstructing the context?
None of those questions gives you the cause. They simply show you where it is worth looking more closely.
So when a result moves unexpectedly, I would not ask only, “When did this fail?”
I would also ask:
What had already stopped holding before we were forced to call it failure?




Comments