People don’t necessarily resist change. They resist feeling powerless. When employees closest to the work are excluded from decisions, organizations can move quickly while creating costly problems downstream. Learn why participation is not the same as consensus and how better listening can lead to better organizational change.
“Why are they resisting this?”
It’s a question leaders often ask when an organizational change that made perfect sense on paper begins struggling in practice. The strategy was sound. The business case was clear. The executive team aligned. The implementation plan was built. And yet, the people expected to make the change successful aren’t embracing it.
Throughout my career, I’ve led organizations through mergers, restructures, technology implementations, process improvements, and cultural transformations. One lesson has surfaced again and again:
People don’t necessarily resist change. They resist feeling powerless.
That distinction matters.
Years ago, I worked with a financial services organization under significant pressure to deliver technology solutions faster while reducing costs.Leadership developed what appeared to be a logical strategy: increase the use of offshore resources, consolidate roles, and streamline the delivery model.On paper, the plan made sense.But as the conversations progressed, something concerned me.
Most of the decisions were being made by a relatively small group of leaders behind closed doors. The conversations focused on budgets, timelines, efficiencies, and organizational charts. What was largely missing were the voices of the people who would actually have to make the new model work every day.
I recommended slowing down long enough to bring those people into the conversation. Not to hand over leadership’s responsibility for making difficult decisions. Not to require consensus on everything. But to explain the problem we were trying to solve, share the direction being considered, ask questions, listen, and learn from the people closest to the work. Because leadership may have had good ideas. But we didn’t have all of them.
The developers writing code, the teams testing software, the people gathering requirements, and those supporting customers understood realities that couldn’t always be seen from an executive conference room. They weren’t obstacles to the change. They were one of our greatest sources of insight.
The organization moved forward quickly. Roles were consolidated. Responsibilities shifted. Quality assurance functions were restructured. Offshore teams expanded. Initially, the speed looked like success. Then the cracks began to appear.
Communication became harder. Knowledge gaps widened. Technical debt accumulated. Teams became exhausted trying to keep pace. Eventually, the organization spent significantly more time dealing with unintended consequences than it might have spent involving people earlier. That experience reinforced something I’ve seen repeatedly:
Moving fast and moving well are not always the same thing.
Sometimes the time leaders believe they’re saving by limiting participation simply gets paid back later through resistance, rework, confusion, turnover, or lost trust.
This is where leaders can become uncomfortable. “If we involve everyone, we’ll never make a decision.” I agree. And that’s not what I’m suggesting.
Leadership still requires judgment. Leaders are responsible for making difficult decisions, setting direction, balancing competing priorities, and sometimes making choices employees will not like.
Participation is not the same as consensus.
People don’t have to make every decision to feel respected by the process. They need opportunities to understand the problem, contribute what they know, ask questions, raise risks, and see that their perspective was genuinely considered. And leaders need to be clear about where input can influence a decision and where a decision has already been made.
Inviting people into a conversation when there is no genuine opportunity for their input to matter isn’t participation. It's a theater. And people recognize the difference.
One of the easiest mistakes to make as our leadership responsibilities grow is assuming our broader perspective gives us a complete perspective. It doesn’t. Executives see things frontline employees cannot. Frontline employees see things executives cannot. Finance sees something Technology doesn’t. Operations sees something HR doesn’t. Customer-facing employees may see problems and opportunities that never appear on an executive dashboard.
The objective isn’t to determine whose perspective is right. The objective is to build a more complete picture from all of them. That’s why listening isn’t simply a “soft” leadership skill. It’s a source of business intelligence. The earlier leaders listen, the more opportunity they have to identify unintended consequences before those consequences become expensive problems.
Over the years, I’ve come to see every organizational change as having two equally important dimensions: the process change and the human transition. Leaders ignore either one at their own risk.
You can announce a new organizational structure in a meeting. You can launch a new technology platform on a particular date. You can change reporting relationships in an HR system. You can introduce a new operating model with a beautifully designed presentation. Those are changes. Transition is different.
Transition happens through conversations. Questions answered. Concerns acknowledged. New skills developed. Trust built. Old habits released. New behaviors practiced and reinforced.
A change may have an implementation date. The human transition rarely does. And that’s one reason organizations sometimes declare a transformation complete while employees are still trying to figure out how to operate within it.
Before the executive team puts the finishing touches on the next transformation, restructuring, technology implementation, or operating-model change, ask these five questions.
1. Have we talked with the people closest to the work? Not simply informed them. Really talked with them. There’s a meaningful difference between communicating a decision and seeking insight before making one.
2. What do they know that we don’t? Ask where the proposed model could create friction, risk, unintended consequences, or opportunities you’ve overlooked. Then listen carefully enough to be willing to adjust the plan.
3. Have we clearly explained the problem we’re solving? People are much more capable of engaging with a difficult solution when they understand the problem behind it. Don’t communicate only what. Explain the why.
4. Where can employees genuinely influence the outcome? Be clear about what has already been decided and where input can still shape the solution. False participation destroys trust faster than no participation at all.
5. What will people need after the announcement? Communication is not complete when the town hall ends. Think about what managers will need to reinforce the change. Consider training, new responsibilities, unanswered questions, feedback loops, decision rights, measures of success, and the support required to make the new way of working sustainable.
The best change leaders aren’t simply good communicators. They’re good listeners. They understand that communication isn’t something you do to an organization after making a decision.
It should also be part of how you make better decisions in the first place. They recognize that listening doesn’t diminish leadership authority. It improves leadership judgment. And they understand something else:
The people affected by change aren’t an obstacle standing between you and transformation. They are the people who will ultimately determine whether the transformation works.
That doesn’t mean every suggestion gets implemented. It means meaningful perspectives are heard, considered, and respected.
Organizations today face enormous pressure to move quickly. Markets change. Technology changes. Customer expectations change. Business models change. Sometimes leaders genuinely don’t have the luxury of months of deliberation. But involving people doesn’t necessarily have to slow an organization down. Done well, it can prevent the organization from having to go backward later.
A few thoughtful conversations early can reveal a dependency no one considered. A frontline employee can identify a process problem before it becomes an implementation problem. A manager can surface a capability gap before a new responsibility is assigned. A team can identify customer impact before the customer experiences it. That isn’t slowing transformation. That is improving it.
At GSD Coach & Recruiting, we work with organizations during moments when people decisions matter. Growth. Leadership transitions. New roles. Organizational change. Recruiting. Team development. Those moments often create pressure to move quickly. But speed without understanding can be expensive.
Sometimes the fastest path to a better organization is to spend a little more time listening before deciding. Because people support what they help create. And when people understand the why, see how their contribution matters, and believe their experience has been respected, change has a much better chance of becoming something more than an announcement. It has a chance to become the new way the organization actually works.
GSD Coach & Recruiting helps leaders navigate the people, organizational, and talent decisions that turn strategy into sustainable results. Talk With GSD
Get more expert advice for SaaS founders on sales hiring, recruiting strategies, team leadership, and building high-performing sales teams.
Get started today with a free, no-obligation discovery call. Just fill out the form and share your revenue goals. We’ll be in touch within 24 business hours to show you how our proven systems can accelerate your hiring process.
.avif)
Our proven methodology has helped SaaS companies across every growth stage build revenue teams that drive predictable, scalable results. Connect with us to discover how we can accelerate your hiring process and deliver the A-Player talent your company needs to reach its next milestone.
