Resolve Ownership of a People Decision Across Matrix Lines

A matrix org gives an employee access to more support than a single reporting line ever could, but it also creates a real risk. Two leaders can each believe they own a decision about that employee's future, and if they act on that belief separately, the employee ends up with conflicting instructions in the same week. As the HR business partner sitting between them, your job is not to pick a side. It is to slow the moment down long enough to separate what each leader observed from who actually holds the authority to act on it.

Why this conversation goes wrong

In a matrix structure, a project leader watches the daily work and sees problems first. A functional manager owns the formal record, the goals, the feedback history, and the process steps required for any performance action. Both roles are legitimate. The trouble starts when the project leader, frustrated by a missed deadline or a quality problem, acts on that frustration directly, telling the employee about a reassignment or a performance plan before the functional manager even knows there is a problem.

Once that happens, the employee hears two different stories from two different authority figures, and neither story is complete. The project leader has real evidence but no formal standing to open a performance process. The functional manager has the standing but was not in the room when the problem happened. If you let this play out without stepping in, the employee loses trust in the organization, the functional manager gets blindsided, and any documentation that follows looks reactive instead of considered.

This same pattern shows up whenever authority is split by design. The confusion looks a lot like the one covered in Address Repeated Interruptions During Team Meetingswhere nobody had named who was responsible for enforcing a norm in the room. The fix is the same in both cases. Name the decision, name the owner, and get everyone talking about the same thing at the same time.

How to prepare before you step in

Do not walk into this conversation cold. Pull up whatever the organization treats as the source of truth for decision rights, whether that is a documented chart, a matrix charter, or last year's precedent for a similar case. Know which of four things is actually in dispute before the meeting starts. Assignment, meaning who does what work, usually sits with the project leader. Work priorities are typically shared between the project leader and the functional manager. Performance feedback belongs to the functional manager, with input from the project leader. Formal people action, such as a performance plan or a role change, almost always sits with the functional manager and HR together.

Turn those four items into a simple map before you meet as a group. For each one, write down the accountable manager, who else contributes evidence, what evidence is needed, and who will communicate with the employee. Review that map with both leaders before either one talks to the employee, not after.

Talk to each leader separately first if you can manage it. Ask the project leader what they observed, what evidence they have, and what they think should happen next. Ask the functional manager what they already know and what they still need. This way you walk into the joint conversation already knowing where the overlap sits, instead of discovering it live while both leaders get more entrenched in front of you.

What to say

Kim, the project leader, opened the meeting fast. "I want to pull Devin off the project and start a performance plan today. This has gone on long enough."

Ezra, the functional manager, pushed back right away. "I own Devin's performance record, and nobody told me there was a problem until this call. I need the project facts before anything moves toward a formal plan."

You stepped in before the two of them turned it into an argument. "Let's split this into two separate pieces so we are not mixing them up. Kim, tell us what happened with the delivery and what the project needs from here. Ezra, once you have those facts, you own the conversation about performance, and I will support you on the process side. Before we end this call, I need to know who tells Devin about the project change, and exactly what that person will say."

Kim answered first. "I can tell Devin about the reassignment today. I will keep it to the project scope, nothing about performance."

Ezra followed. "I will set up a separate meeting this week to talk about expectations, and I want you in that room with me."

Kim tried to fold the two conversations back together. "Can we not just tell Devin everything at once so it does not feel like two hits in one week?"

You held the line. "That would put you in the position of speaking for a process you do not own. Two shorter, honest conversations beat one that mixes project feedback with a formal record. Devin will handle two clear conversations better than one confused one."

That exchange does three things at once. It separates fact from process, it names an owner for each message, and it stops either leader from speaking for a decision that is not theirs to make.

Mistakes to avoid

A few habits sink this kind of conversation almost every time.

1. Letting the person who talks first set the outcome. Urgency in someone's voice is not the same as authority over the decision.

2. Agreeing to a combined message before the facts and the process are actually separated. A combined message usually means someone is speaking outside their lane.

3. Skipping the decision map because the situation feels obvious. The cases that feel obvious are exactly the ones where a leader later says nobody told them.

4. Letting the meeting end without a named person for each communication. If you leave without answering who tells the employee what, someone will fill that gap on their own, usually the wrong way.

5. Treating this as a one time fix. New questions come up as the situation moves, and each one needs the same quick sorting into fact, feedback, or formal action.

How to practice and score it

This conversation is hard to get right the first time you face it live, because it asks you to referee two people who each have a legitimate claim while an employee's standing is on the line. Rehearsing it before the stakes are real changes how steady you sound when it matters. Run the scenario with an AI counterpart playing the project leader who wants to move fast, and score yourself on three things. Did you separate fact from formal action within the first two minutes. Did you name a single owner for each piece before the meeting closed. Did you avoid promising an outcome to either leader before the process actually ran its course.

DealSpeak builds scenarios like this one so you can rehearse the specific push and pull of a matrix disagreement before you sit down with two real managers who disagree with each other. The same approach works for other split authority situations, including the one covered in Discuss a Missed Deadline After a Dependency Changedwhere the instinct to assign blame fast needs the same kind of pause. If your team handles matrix reporting often, browse the full set of HR and Leadership practice conversations and build the habit before the next disputed decision lands on your desk.

Where this leaves the employee

The employee never needs to know how much sorting happened behind the scenes. They just need two clear conversations from the right people, in the right order, saying things that match. Get the ownership settled first, and the rest of the conversation takes care of itself.