Project Management

Please login or join to subscribe to this thread

How do you navigate resource conflicts with Delivery Managers?

linkedin twitter facebook   Resource Management  
avatar
Srikana Ray
Community Champion
Project Professional, PMP

As a Project Manager, how do you handle resource conflicts with Delivery Managers when multiple projects are running simultaneously?

I have encountered situations where shared resources are stretched across several projects, making it challenging to meet project commitments and timelines. Balancing competing priorities while ensuring successful delivery can be difficult.

What processes, governance models, prioritization frameworks or escalation mechanisms have worked well in your organization? How do you align stakeholders and make resource allocation decisions when demand exceeds capacity?

Would like to hear about your experiences, lessons learned and best practices.

Sort By:
< 1 2 >
avatar
Srikana Ray
Community Champion
Project Professional, PMP
Jun 06, 2026 1:16 PM
Replying to Luis Branco
...
This is a question I have seen repeatedly across organizations, and over time I have come to believe that resource conflicts are rarely resource problems.

More often, they are symptoms of a deeper alignment problem between strategy, portfolio commitments, and organizational capacity.

When multiple Project Managers and Delivery Managers compete for the same resources, the immediate discussion tends to focus on who gets the resource.
However, the more important question is: who has the authority and criteria to make trade-off decisions when demand exceeds capacity?

In my experience, the most effective organizations address this through portfolio-level governance rather than project-level negotiation.

Key elements typically include:
• A transparent view of demand versus available capacity.
• Explicit prioritization criteria linked to strategic objectives and expected value.
• Clear decision rights for resource allocation and escalation.
• Regular portfolio reviews to reassess priorities as business conditions evolve.

One lesson I learned is that resource conflicts often reveal hidden assumptions.
Many organizations approve projects as if capacity were unlimited, only to discover later that commitments exceed what the system can realistically absorb.

In those situations, escalation should not be viewed as a failure of collaboration.
It is a governance mechanism that forces explicit decisions about priorities, value, risk, and timing.

Ultimately, successful organizations do not eliminate resource conflicts.

They create transparent and coherent ways to navigate them.

The real challenge is not deciding who gets the resource.

It is preserving organizational coherence when demand exceeds capacity.
Thank you for sharing your valuable insights. I agree that organizations need to have a strategy, be more transparent and coherent in resolving resource conflicts. While many a times it is solely a challenge for the project manager who has limited authority over resources to maintain adequate balance and prioritize projects.

I think a collaboration between business, delivery and project management can adequately create a strategy and governance to navigate resource conflicts and deliver projects successfully.

I’d focus on learning the underlying concepts rather than trying to master every tool — scheduling, dependencies, resource allocation, dashboards, risk tracking and reporting. Once you’re comfortable with those, moving between platforms becomes much easier. I’d probably get hands-on experience with one traditional scheduling tool and one modern collaborative PM platform, then build a sample project in each rather than just watching tutorials.

One thing I’ve seen make a big difference is separating project priority from resource availability. A project can be high priority, but that doesn’t mean the required people suddenly have more capacity.
When the same resource is requested by multiple projects, it helps to make the conflict visible before the assignment is confirmed current workload, upcoming commitments, capacity and business priority should all be part of the decision.
I also think this is where task-based planning alone can fall short. Knowing who is assigned to a task is useful, but knowing what else that person is already committed to across projects is just as important.
Ideally, conflicts should be resolved through agreed portfolio/business priorities first, with escalation only when the competing demands genuinely can’t be reconciled.
Curious how others handle this do your PMs and Delivery Managers have a shared view of resource capacity, or is it still largely discussed project by project?
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

I have made good judgements in the past. I have made good judgements in the future.

- Dan Quayle

ADVERTISEMENT

Sponsors