The person who approves a purchase is not necessarily the person who lives with its consequences.

An investment is approved in principle. Management supports the project, purchasing accepts the commercial terms, engineering confirms the equipment meets specification. Everything appears ready to move.

Then operations objects. They want another evaluation and question whether the solution can be integrated into the existing process. To everyone focused on the approval, this looks like an obstacle appearing at the worst possible moment.

From operations' perspective, it is not an obstacle. It is the first time anyone has asked what the decision looks like from where they stand.

Approval and exposure are distributed unevenly

Every stakeholder in a purchase decision evaluates it through different consequences.

Management weighs the financial return. Purchasing weighs cost and contractual terms. Engineering weighs technical suitability. Operations will be responsible for keeping the equipment running after everyone else has moved on to the next decision.

All of these perspectives are legitimate. They are not exposed to the same risk. If the system performs, the organization benefits collectively. If it fails, the consequences land disproportionately on the people closest to it — production, maintenance, implementation.

Risk flows downhill — operationally

The pattern is worth naming, with a scope. Decision-making authority and operational risk do not just differ between stakeholders; they often sit in different parts of the organization entirely.

On the operational side, risk tends to flow downhill — toward the people who cannot delegate it. If the new component causes unexpected downtime, maintenance gets the 2 a.m. call, and no amount of committee authority restarts the line. On the other side, risks run the other way: financial exposure, contractual liability, and reputational consequence concentrate with the people who approved the investment. A failed project is not painless for management — which is exactly why the two groups evaluate the same decision with different eyes.

That asymmetry explains why the objection near the end of a decision so often comes from a department with no vote in it. They are not misunderstanding the value of the proposal. They are pricing an operational risk that rests on them more heavily than on the people who sign.

Why that caution may be rational

Consider a manufacturer evaluating a new component that promises efficiency gains. The financial case is convincing and the engineering checks out. But the maintenance team has limited experience with the technology — so they emphasize reliability, service availability, familiarity. To the rest of the organization, this can look like unnecessary conservatism.

It is a reasonable response to the consequences they personally carry.

Reading resistance accurately

When stakeholders oppose a proposal, a common assumption is that they have not understood its value. The alternative assumption is more useful: that they understand it, and are describing the part of the value calculation that lands on them.

A solution that reduces operating costs may increase maintenance complexity. A performance gain may require training the same team that will be blamed for downtime.

Finding the person who can approve the expenditure matters. Understanding a complex decision also means understanding who has to live with it afterward — because that is where the consequences concentrate, and therefore where the most careful questions tend to come from.

Related: Your Best Contact May Not Be Your Strongest Champion — about who can move a decision, rather than who absorbs it.

From the book

The risks stakeholders carry, and how unevenly those risks can be distributed, are explored in more depth in Chapters 5, 6 and 13 of Sales Between the Lines, including how stakeholder responsibilities and perceived risk can change what resistance actually means.