Recognizing a problem and deciding to solve it are two different things.

The most puzzling stalled opportunities are not the ones where the customer disagreed.

They are the ones where the customer agreed with everything. The equipment is genuinely inefficient. The savings calculations hold up. The proposed solution is technically sound, and the customer said so. And then the project never received approval — not rejected, just never scheduled.

When that happens, the explanation is usually not in the solution. It is in everything around it.

A problem exists inside a portfolio of problems

Organizations do not evaluate problems one at a time; they allocate scarce attention and budget across all of them.

A production manager recognizes the downtime. Engineering confirms the alternative is superior. Finance accepts that the return is reasonable. And in the same building, another production line needs immediate attention, a facility expansion has consumed this year's budget, and management has committed resources to a different strategic objective.

The improvement can be worthwhile without being the most worthwhile use of the organization's money and attention at that moment.

Sales conversations naturally magnify the one problem the supplier can solve, because that is the frame the conversation was built around. The customer has to weigh it against everything the supplier cannot see.

The same problem, different urgency

Two manufacturers experience the same level of downtime. For the first, each failure threatens contractual delivery commitments on capacity that is already stretched. For the second, interruptions are inconvenient but plannable.

Both calculate similar savings. Both may have good reasons to invest. What differs is how much waiting costs them.

The urgency of a problem is not a property of the problem. It is a property of its position.

Finding the actual position

A useful question in these conversations: what happens if the customer does nothing?

Not as a pressure technique — as calibration. If postponement creates real costs, rising risk, or blocks another objective, the problem will likely rise on the agenda. If the current situation can continue indefinitely without meaningful consequence, it will keep losing to things that cannot wait.

One of the clearest indications of priority is rarely stated in conversation. Where it is visible, it sits in budget sequencing: who requested the money, when the budget cycle resets, and what the organization actually spent its initiative budget on this year.

Sometimes the most important question is not whether your solution solves the customer's problem.

It is whether solving that problem matters enough, relative to everything else, to justify taking action.

From the book

Priorities, timing and the circumstances that decide whether a recognized problem becomes an actual project are explored in more depth in Chapter 15 of Sales Between the Lines, alongside the wider role of decision environments in understanding why apparently similar opportunities move at different speeds.