You Were Hired for Your Expertise. Just Not Given the Authority to Use It.

I have lived this more than once. And each time, I could see the damage forming and I raised the flags — but it took time until the right changes were made. Time resulting in damages, costs and a lot of frustration.

The first time, the company was entering a new territory and needed to build the local operations and supply chain setup from the ground up. HQ Operations was assigned to lead it. That made sense. The function had the professional ownership, the expertise, and the broader view of how the operation needed to be built.

But the local GM wanted everything under his control, including the local operational people.

We advised against that. We were clear that if the people responsible for execution were not professionally aligned with the function leading the build, the result would be conflicting priorities, different ways of working, and no real discipline around the workplan.

That is exactly what happened.

The operation did not pull off the way it should have. Not because the need was unclear, and not because the capability was missing, but because the structure itself was misaligned. There was no real alignment on ways of working, no shared ownership of the workplan, and no clear authority over execution.

Only later was the decision changed. Boundaries were finally set. The people were moved into a matrix structure with professional reporting into us. In other words, the organization eventually created the structure that should have existed from the start.

The second time looked different on the surface, but the underlying problem was the same.

A local business had been acquired by a global company, and I was brought in to integrate the local supply chain into the global model. Professionally, the reporting line was clear. My boss was in another country, and my team and I were no longer reporting to the local site manager.

But the local reality did not follow the formal structure.

The site manager either could not accept — or did not fully understand — that the reporting relationship had changed. He continued to treat me and my team as if we were still part of his local structure, and he kept pulling me in directions that did not fit the global model or the integration work that needed to happen.

So again, the issue was not ambiguity on paper. It was the gap between what the structure said and what local authority continued to do in practice.

One case failed because the structure was wrong from the beginning. The other because the structure changed on paper, but not in practice.

The Setup Nobody Talks About

These are not isolated stories. This dynamic plays out across organizations every day — and it has a name: authority without influence, and influence without authority.

When a company assigns an expert to lead a project, build a function, or drive a transformation — whether internal or external, whether a regional lead, a subject matter expert, or a global function owner — they are making an implicit promise: we need your expertise, and we are giving you the mandate to apply it.

What they often fail to provide is the one thing that makes that mandate real: authority over the people and decisions the outcome depends on.

The real problem is structural: the expert is given responsibility for the outcome, but not the authority needed to shape the behavior of the people responsible for execution.

Without that, the expert is operating in a vacuum. They have the knowledge. They have the goal. They may even have the title. But the people they need to move are loyal to someone else — someone with day-to-day authority, history, and direct influence over their priorities, evaluations, and careers.

In that situation, expertise alone does not drive execution. Existing authority does.

Why This Isn't About Hierarchy

What makes this dynamic particularly frustrating is that it does not matter whether the expert is senior to the local manager or not.

Seniority on an org chart does not automatically translate into authority on the ground. A global function lead can be overruled — not formally, but practically — by a site manager who simply continues to behave as though nothing has changed. No confrontation is required. Just continued involvement, continued local presence, and the quiet signal to the team that the old authority still applies.

The expert sees it happening. They raise it. They are told to work through it, build the relationship, bring people along.

All reasonable advice — in a system that had actually been designed to support them.

But in a system where the structural misalignment was never fixed, those suggestions just place the burden back on the expert to solve a problem they did not create.

And when it does not work out, the narrative writes itself: the expert could not get buy-in. Could not adapt. Could not deliver.

The system, meanwhile, stays exactly as it was.

That is not a people problem. It is a design problem.

What the Expert Can Do — Realistically

There is no clean fix when the system was not designed to support you. But there are ways to protect yourself and improve the odds — without pretending the problem is yours to solve alone.

Before you accept the mandate, ask the hard questions. Who has authority over the people you will be working with? What happens when your direction conflicts with theirs? Who arbitrates, and how fast? Vague answers at this stage are a signal, not a detail. The time to surface the misalignment is before you are standing in the middle of it.

Document the conflict early, and frame it as a risk — not a complaint. The moment you see competing direction undermining the work, put it in writing and escalate: "The team is receiving conflicting guidance. This will affect the outcome unless we resolve it. Here is what I need from you." This is not politics. It is professional clarity.

Scope your commitment honestly. If you do not control the inputs, do not guarantee the output. "I can deliver X if I have Y. Without Y, the realistic outcome is Z." This feels uncomfortable, especially for experts who are used to finding a way. But overpromising in a broken system does not serve anyone.

The point is not to cover yourself. It is to force a real conversation about what success actually requires — before failure becomes the only way to have it.

What Senior Leaders Need to Hear

If you are the person who assigned the mandate and moved on — this is the part worth reading carefully.

Mandate without alignment is not a real mandate. It is a setup.

The gap does not usually come from bad intentions. It comes from assuming that defining the structure is enough — that the organization will naturally fall in line once reporting lines are drawn. It rarely does.

Especially when there is a local or site manager with an existing team, existing habits, and no clear instruction — delivered directly, by leadership — that things are supposed to work differently now.

Documenting the structure is not the same as enforcing it. An org chart that nobody is willing to back in practice is just a diagram.

Before you send an expert into a region, a team, or a transformation, a few conversations need to happen — and they need to happen with you in the room, not delegated to an email.

The local manager needs to hear directly from you what has changed, what has not, and where the expert's direction takes priority in practice. The team needs to understand how the model now works and what is expected of them. And everyone needs to know what happens when there is a conflict — who resolves it, how quickly, and with what authority.

If those conversations have not happened, you have not finished the job. You have handed someone a goal and left them to negotiate a power structure you created but never properly defined.

The expert you chose was chosen because they are good at what they do. The least they deserve is a real chance to prove it.

The Bottom Line

Being an expert means you were chosen for your knowledge and capability. It should not mean being dropped into a system where the conditions for success were never built — or were defined on paper but never actually enforced.

If you are living this right now, what you are experiencing is real. It is not a reflection of your expertise. It is a reflection of an organizational gap that existed before you arrived, and that only the people above you have the authority to close.

Name it early. Document it clearly. Escalate it as a risk, not a grievance.

And if you are the leader who created the mandate - finish the job. Align the people, clarify the authority, and back the expert you chose.

Because if you do not, you are not setting someone up to succeed. You are deciding in advance who to blame when it does not work out.

The HR & Organizational Excellence Toolkit gives professionals the structure to make authority clear — including Role and Responsibilities templates that define who owns what.