We make assumptions every day. Most of them are based on
experience, familiarity, and what we believe we know about the people around
us. In business, though, assumptions about how customers or employees will
react to a decision can create problems that leadership never anticipates.
Never imagine that you know exactly how your customers or
employees will react to change. Just because a decision makes sense in a
boardroom or leadership meeting doesn’t mean the logic behind it will land the
same way with the people affected by it.
Business leaders will always be faced with difficult
decisions. Prices have to change, policies need to be updated, processes become
outdated, and sometimes organizations have to restructure the way work gets
done. There will also be times when the right business decision isn’t
necessarily the decision customers or employees would choose for themselves.
Making those decisions is part of leadership. Assuming you already know how people
will react to them shouldn’t be.
Understanding the Decision Isn’t the Same as Experiencing
It
By the time a decision is announced, leadership may have
spent weeks or months discussing it. They’ve looked at costs, operational
challenges, alternatives, risks, and long-term consequences. They know what
prompted the change and why the final decision was made.
Customers and employees usually don’t have that same
background. They experience the decision from a completely different
perspective. A customer may see a new policy as making it harder to do business
with you. An employee may see a process change as creating more work or taking
away flexibility. Something leadership views as a minor adjustment may affect a
routine that someone has relied on for years.
That doesn’t necessarily mean the decision was wrong. It
means the impact looks different depending on where you’re standing.
We Expected Some Pushback
One of the easiest assumptions to make is that people simply
don’t like change. When customers complain or employees object, it can be
tempting to dismiss the reaction as predictable resistance. Sometimes it is.
Sometimes it isn’t.
There is a difference between someone resisting change
because it’s unfamiliar and someone identifying a consequence leadership didn’t
anticipate. If every negative response is written off as resistance, an
organization can miss valuable information about how a decision is actually
working.
The same is true when leadership assumes a change will be
welcomed. A new system may appear easier to use. A revised policy may seem more
flexible. A restructuring may look more efficient on paper. None of those
things guarantee that the people affected will experience it that way. You
don’t really know until the change reaches them.
Ask Before You Assume
When possible, leaders should create opportunities to
understand how a decision may affect people before it’s finalized. That doesn’t
mean every decision has to be made by committee or that customers and employees
get a vote on every business choice. It simply means there is value in asking
questions before assuming you already know the answers.
Talk to the employees who will have to implement the new
process. Ask customer-facing teams what questions or objections they expect to
hear. Consider testing significant customer changes with a smaller group before
rolling them out broadly.
Most importantly, listen for concerns that weren’t part of
the original discussion. The people closest to the work and the people closest
to the customer often see consequences that aren’t obvious from a leadership
position.
Communication Can’t Fix Everything
Good communication matters, but leaders should also be
careful about assuming that a negative reaction is simply the result of poor
communication. Sometimes people understand a decision perfectly well and still
don’t like it.
Explaining the business reasons behind a change can provide
context and help people understand why it was necessary, but explanation
doesn’t eliminate impact. If a new policy creates an inconvenience for a
customer, explaining why the company needs the policy doesn’t make the
inconvenience disappear. If an organizational change makes an employee’s job
more difficult, a well-written announcement doesn’t make the additional
difficulty less real.
Communication should help people understand a decision. It
shouldn’t be used to convince leadership that the reaction would have been
positive if only the message had been delivered better.
Pay Attention to What Happens Next
Some of the most important information comes after the
decision has been made. Watch what customers actually do. Are calls increasing?
Are complaints centered around something you didn’t anticipate? Are customers
finding workarounds? Are employees spending more time on a process that was
supposed to save time? Are people consistently asking the same questions? Those
reactions are information.
Leaders don’t have to reverse a decision every time someone
complains, but they should be willing to reconsider assumptions when the
results don’t match what they expected. Sometimes a small adjustment can
resolve an unintended problem without changing the original decision. Other
times, the reaction may reveal that the organization underestimated the impact
entirely.
Leave Room to Be Surprised
Experience gives leaders the ability to anticipate problems,
and that experience has value. But experience can also make us overly confident
that we already know what people are going to think. We don’t.
Customers and employees bring their own experiences,
priorities, and expectations to every change an organization makes. You can
anticipate their reaction. You can prepare for it. You can even make a very
educated guess about it. But you shouldn’t mistake that prediction for
knowledge.
Make the best decision you can with the information
available. Explain it clearly. Give people an opportunity to respond. Then pay
attention to what they tell you, particularly when their reaction isn’t the one
you expected. The goal isn’t to make every decision popular. It’s to make sure
that leadership never becomes so certain of how people will react that it stops
listening when they actually do.