Consider a manager who moves all supply purchases through one person. Duplicate orders cost money, and nobody has a reliable picture of what's already on the shelf. The change makes sense.

A maintenance supervisor objects, insisting replacement parts need to be ordered quickly and that another approval could delay a repair. The manager hears the concern, decides the savings justify the change, and puts the process in place.

Two weeks later, the supervisor reports that a repair has been held up while a purchase waits for approval. Before they can explain what happened, the manager starts talking about duplicate orders again.

The supervisor came to discuss a part. Now they're back to arguing about the policy.

The decision didn't settle everything.

A leader can make a reasonable decision and still need to hear about the trouble it causes. Almost any change worth making has some cost attached to it. Work lands differently on different people, and some problems only become visible once the change is underway.

That doesn't automatically make the decision wrong.

But when every report of a problem gets met with another defense of the decision, people have to spend time proving they're cooperating before they can explain what needs attention.

In this example, the manager may wonder whether the supervisor is trying to reopen an argument they already lost. That's possible. People do sometimes persist in pushing after a decision has been made. Still, suspicion won't tell the manager how long the order waited or why nobody approved it.

Those facts deserve attention either way.

The person who questioned a change may also be well placed to notice its weak spots. Treating their earlier objection as a reason to discount everything they say afterward leaves you with less information from someone doing the work.

What are you asking them to prove?

At some point in these conversations, the subject can shift without anyone naming it. The leader stops asking about the repair and starts asking whether the employee understands why the new process matters.

They may understand it perfectly. They still need the part.

Repeating a sound explanation won't resolve a practical problem the explanation doesn't address. And pressing someone to acknowledge the benefits again can turn a useful conversation into a test of agreement.

If you're the manager, ask a more precise next question: "Where did the order get held up?"

Let the person answer before returning to the policy. Find out whether the request was submitted correctly and whether the approver was available. You may discover that someone skipped a required step. You may discover that the process has no backup when the approver is out.

Either finding gives you something to address. Another round of defending the savings doesn't.

It also helps to say what remains open for discussion. For example: "We're keeping centralized purchasing. I want to know whether we need a different way to handle time-sensitive parts."

That gives the supervisor a useful place to put the concern. They don't have to overturn the whole decision to fix one problem.

Leave room for the next report.

Listening fairly doesn't require an endless debate. Once you've heard the objection and made a legitimate decision, you can expect people to follow it. If someone refuses, address that conduct directly. Don't treat reporting a delay as the same thing as refusing to cooperate.

Before the conversation ends, make sure you agree on next steps. In this case, that might mean naming a backup approver and checking whether any pending repairs can move forward. Ask the supervisor to bring the request dates if another order gets stuck. Make it ordinary work to report what happened.

If you've already cut them off, you can correct that without making a speech: "I started defending the process before you finished. Tell me what happened with this order."

Then let them finish. The value of that sentence depends on what you do after saying it.

A leader's response teaches people which problems are worth bringing forward. If every difficulty becomes a debate they have to survive, some will wait until the consequences are too important to ignore. By then, you have fewer choices and a more expensive problem.

???

The purchasing change may save money. It may be exactly the decision the organization needed. You'll still need someone willing to walk into your office and tell you a repair is waiting.