Project Management in a Matrix Organization

What changes when you manage a project in a matrix?

In a matrix organisation, people contribute to projects while also working within a function, department or professional group. The exact arrangement varies. A project manager may coordinate delivery but have limited authority over people’s workload, priorities or formal performance review.

That can be confusing when several people believe they are setting the priority. The practical answer is not to guess who has the “real” authority. Agree how work, decisions and capacity will be managed for this project, then use that agreement when priorities conflict.

A matrix can bring together specialist skills without moving everyone into a separate project team. It can also make coordination harder. The structure alone does not guarantee flexibility or efficiency; the way people agree and honour commitments matters.

Start with a working agreement

Before the plan depends on shared people, ask the sponsor, project manager and relevant functional managers to agree a few things. Keep it proportionate to the size and risk of the work:

Outcome and boundaries: what the project needs to deliver, what is in scope and what remains uncertain.
Project authority: what the PM can decide, coordinate or escalate, and which decisions need a sponsor or governance forum.
Functional responsibility: who confirms people’s availability, professional standards, line management and formal performance processes.
Capacity commitments: which roles are needed, how much effort, during what period, and who confirms the commitment.
Priority conflicts: who will decide when project work competes with operational or other project work, and how quickly that decision is needed.
Delivery and escalation: where plans, decisions, actions and dependencies are recorded, and how a blocked hand-off is raised.

Write down the agreed boundaries in a short project initiation note or team working agreement. A RACI chart can help with a complicated set of responsibilities, but it will not create authority or capacity that the organisation has not agreed.

1. Responsibility is clear on paper but unclear in practice

A project manager may be accountable for coordinating a milestone but depend on a team member whose line manager sets their day-to-day workload. If the plan says “Alex owns the analysis” without confirming time, decision rights and acceptance, the plan records a hope rather than a commitment.

What helps: Confirm who performs the work, who provides direction, who accepts the result and who can resolve a conflict. Use the organisation’s governance and delegation rules. For each significant deliverable, name an owner who agrees to the work and the capacity needed. If responsibility is disputed, ask the sponsor and functional manager to settle the boundary before the date becomes critical.

2. The same specialist is needed by several projects

A shared specialist may be listed on three plans. That does not mean all three projects can receive the person’s full capacity at the same time. Unplanned meetings, operational work and urgent requests may also use that time.

What helps: Make a specific resource request. Include:

the capability or decision needed, rather than only a person’s name;
the deliverable and why it matters to the project outcome;
the expected effort and dates or time windows;
the dependency or milestone affected if the support is unavailable;
the person or manager who can confirm the capacity.

Ask what work would be displaced. If the manager cannot commit the requested time, update the schedule or take a choice to the sponsor. Do not build the baseline around an unconfirmed allocation and then treat every conflict as an individual performance problem.

3. Functional and project priorities compete

“The project is the priority” is not enough if the project manager cannot explain which work should move, and who can approve that trade-off. A team member may be trying to meet two reasonable commitments.

What helps: Show the impact in plain terms and offer realistic choices. For example: move a milestone, sequence the work, reduce or defer scope, secure temporary capacity, or accept a documented impact. Ask the person with the agreed authority to decide. Record the result and update the plan so other projects and operational teams can see what changed.

4. People attend different meetings and hear different versions

Matrix projects often cross functional boundaries, which can create duplicate reporting, missed decisions and hand-offs nobody owns. Adding another recurring status meeting may not solve that.

What helps: Use one agreed place for the current plan, key decisions, dependencies and actions. Give meetings a clear purpose and say whether each item is for information, discussion or decision. Send relevant information to people who cannot attend, and name who will communicate a decision to affected teams. For an important hand-off, agree what is being supplied, what “ready” means and who accepts it.

5. Delivery feedback and formal performance review get mixed up

The PM may see a person’s project contribution but not their full workload, professional responsibilities or work on other initiatives. The line manager may see the wider picture but not every delivery detail.

What helps: Agree how project feedback will be shared. Give specific evidence about the agreed deliverable, quality, collaboration or a constraint; avoid broad character judgements. The formal performance process remains with the role and manager assigned by the organisation. Where contributions are strong, make them visible to the person’s manager. Where work is blocked, first establish whether the commitment, priorities and support were clear.

6. Team members feel like borrowed resources

People can lose context when they move between project and operational work. If they only receive task instructions, it may be difficult to make good decisions or spot a dependency early. At the same time, project managers cannot assume that every team member can attend every meeting.

What helps: Give people enough context to understand the outcome, the work they own, the decisions they can make and who can help. Invite them to planning conversations that affect their work. Keep handovers concise and make it easy to find the latest decision. Respect their functional standards and workload instead of treating them as interchangeable capacity.

Example: one analyst, two important commitments

This is an illustrative scenario. An analyst is needed to validate data for a customer service change and to support an operational audit in the same week. Both commitments matter. The analyst tells the PM that completing both by Friday is unlikely.

The PM should confirm what the project needs from the analysis, which parts are needed first and what decision or milestone depends on it. The analyst’s line manager can explain the capacity and other commitments. Together they can identify whether the work can be split, resequenced or supported by someone else. If there is still a choice between two organisational priorities, the sponsor or agreed portfolio authority decides. The PM then updates the delivery forecast and tells affected people what was agreed.

That conversation is better than asking the analyst to “manage their time” when the actual problem is two commitments competing for the same hours.

A short agenda for resolving a capacity conflict

Confirm the outcome and the work that is genuinely needed.
Check the current capacity and other commitments with the functional manager.
Show which dates, dependencies or acceptance points are affected.
Offer feasible options and explain the consequences of each.
Confirm who has authority to choose, record the decision and update the plan.
Tell the people whose work or dates have changed.

Common matrix-management traps

Assuming the PM can assign anyone’s time. Confirm capacity with the appropriate manager or resource owner.
Escalating every disagreement. First clarify the work, impact and decision route; escalate a real trade-off to the right authority.
Making the team absorb the conflict through overtime. Show the capacity gap and ask what should change.
Using a RACI to avoid a conversation. A chart can clarify roles, but people still need to agree the decisions and commitments.
Keeping separate plans for every reporting line. Maintain a shared current view, with role-appropriate access to information.
Blaming an individual for a missed commitment that was never confirmed. Check the capacity, priority, inputs and acceptance criteria first.

What to do this week

Choose one important deliverable that depends on a shared team. Ask the delivery owner and functional manager to confirm the outcome, effort, dates, acceptance and decision route. If there is a conflict, bring the impact and options to the right sponsor early. Record the commitment and update the plan.

Project management in a matrix can be challenging because authority and capacity are shared. It becomes more manageable when people know which decisions belong to them, what time they have committed and how the organisation will resolve competing priorities.

Navigating Project Management in a Matrix Organization: Challenges and Solutions