What to Do When a Senior Employee Pushes Back on Everything

By VICKY BROWN

There’s a moment a lot of founders hit, usually a few years in, once the business has actually grown a little and there are people around who’ve been with you a while. And it’s a strange moment, because it doesn’t feel like a crisis. It feels like a meeting. Just another meeting where your most experienced person has, once again, found a reason your idea won’t work.

The first time, you think, good, that’s useful, that’s why I hired someone this sharp. The tenth time, you start to wonder.

So let’s talk about that. Because the honest answer is, it depends. It depends on whether what you’re dealing with is genuine disagreement, the kind that makes your decisions better, or something that’s turned into a pattern, the kind that just slows everything down and quietly puts someone else in charge of your company without you ever agreeing to it.

Pushback isn’t the enemy

Let’s start here, because it matters. You do not want a leadership team full of people who just nod along. A strong senior employee sees things you don’t. They know how a decision is going to hit your clients, your systems, your timelines, in ways you genuinely can’t see from where you’re sitting. An idea that sounds clean on paper might be a nightmare to actually execute, and the person who’s been doing the execution for years is exactly who’s going to know that.

So no, the goal was never zero disagreement. The goal is learning to tell the difference between the kind of pushback that sharpens a decision, and the kind that’s just resistance wearing a business-casual outfit.

Here’s what the healthy version actually sounds like, in practice. The person explains the concern clearly. They bring facts, they name the actual risk, maybe they even offer another way to do it. And here’s the part that really matters, the part that tells you everything. They understand that raising a concern doesn’t guarantee they get their way. They can say “I disagree, and here’s why,” and then, once the call is made, they move forward. You’ll hear things like “here’s the risk I see,” or “have we thought about this,” and eventually, “I still have concerns, but I understand the decision, and I’ll move forward.” That last sentence right there, that’s the whole ballgame. That’s what separates a valuable voice from a problem.

What the other version looks like

Now, chronic resistance is trickier, because it almost never shows up looking like resistance. It shows up looking like caring. A lot.

It’s less about any one decision and more about how this person relates to authority generally. They don’t raise the concern once and let it go, they keep reopening it, sometimes weeks later. They weigh in on things that aren’t remotely their department, because they’re senior, because they’ve been around, because they know things. And they cooperate fully only when the decision happens to go the way they wanted.

Here’s how you know it’s crossed a line, and this one’s worth sitting with for a second. You start managing around them. Delaying an announcement because you don’t want the reaction. Over-explaining a call that never needed their sign-off to begin with. Looping them into conversations that aren’t theirs, just to keep the peace. That right there is the warning sign. Once someone’s anticipated reaction is shaping how you actually run your company, they’ve picked up authority the org chart never gave them.

Look at the pattern, not the moment

You don’t label someone “difficult” because they pushed back hard once. That’s not fair, and honestly it’s not accurate either. What you’re looking for is the shape of it over time. Do they push back on nearly everything, or only the stuff that genuinely matters? When you hand them new information, does their position ever actually move? Do they seem to understand the difference between giving input and making the final call? Do they keep lobbying after a decision is already settled? And when they say they’ll do something, do they follow through, or comply just enough to say they technically didn’t refuse?

The pattern is the diagnosis. Not any single moment.

“… you may need to just say the actual rule out loud“

You might have built this yourself

Now here’s the part that’s a little uncomfortable, so bear with me. A lot of the time, founders create this dynamic without meaning to.

Someone can genuinely know more about their function than you do, and that’s real, that deserves respect. But knowing one part of the business better than you doesn’t hand them authority over the rest of it. And if you’ve spent years being the inclusive leader, inviting discussion, asking everyone’s opinion, well, somewhere in there, that invitation might’ve quietly gotten reinterpreted as shared control.

So you may need to just say the actual rule out loud. Something like: I want your perspective, I expect you to raise concerns, I’ll take your recommendation seriously. But once we’ve had that conversation, the decision is mine, or it belongs to whoever’s accountable for that part of the business. That’s not harsh. That’s just clarity, and clarity is what keeps resentment from building up around a rule nobody ever bothered to state.

Compliance is not the same thing as support

This distinction trips people up constantly, so let’s name it plainly. “Fine, I’ll do it,” delivered with a sigh everyone in the building can hear, is not support. Real support looks like executing competently, communicating the decision the right way, and not pulling other people into the disagreement through side conversations or a certain tone in a meeting. Nobody’s asking anyone to pretend they loved the idea. But undermining a decision quietly, that’s not compliance. That’s resistance, just dressed a little nicer.

Whether you’re an entrepreneur jumping into a leadership role, a seasoned business pro with new HR responsibilities, or just starting your HR career – we’ve got the right path to guide you through your HR hurdles.

Check out the Leaders Journey Experience. 

Having the actual conversation

Don’t do this in the middle of the latest disagreement, that’s the wrong moment. Schedule a separate conversation about the pattern itself, and bring specific examples. Something like: “I value your experience, and I want you to keep raising concerns. But I’ve noticed a lot of decisions turning into extended debates, some outside your area, and in a few cases the conversation kept going after the decision was already made. That slows us down, and it creates confusion about who’s actually responsible for what.”

Then tell them plainly what you need going forward. Bring the concerns, the recommendations, the facts. Once the decision is made, support it and help the team execute it, even when it’s not the call they’d have made.

And watch your own part in this too. If the same objection gets raised five times and gets five more meetings, you’ve just taught someone that persistence eventually wears you down. Once they’ve genuinely been heard, close the loop. “I understand you disagree, we’ve considered it, the decision stands, let’s talk about execution.” That might feel uncomfortable with someone who’s been loyal a long time. But without that boundary, every decision in your company stays permanently up for debate.

A strong senior employee should make your thinking better. They should flag risk, challenge assumptions, tell you the thing you don’t want to hear. Challenge without discipline turns into resistance, though, and that’s the line worth watching for, because once you can see it, you can actually do something about it.

Spread the word

This website uses cookies to ensure you get the best experience on our site.