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.
This is one of the challenges for delivery. Often it requires multiple regular meetings with stakeholders to not only set the timelines and work allotment for the resource across various projects, but to also provide updates on the progress. I have had a single QA assigned to 3 teams and hence Scrum Masters had regular discussions / ongoing chats on managing dependency on the QA from one sprint to the next. Transparency amongst POs, SMs and the QA and building in buffer time into the tickets helped to some extent - but delivery for all the teams involved was a challenge, until the organisation hired an additional resource Saving Changes...
When I was last in this situation, we didn't handle it at the project level - it affected all project managers and operations, so we had a separate delivery coordination meeting that all project managers and operations leads attended to present changes and get them on the schedule. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
I've found that resource conflicts are usually easier to resolve when priorities are transparent and agreed upon at the portfolio or leadership level rather than negotiated project by project. When demand exceeds capacity, we can focus on making the trade-offs visible: what gets delayed, what risks increase, and what business impact each option creates. That helps stakeholders make informed decisions instead of treating it as a resource discussion alone.
...
1 reply by Kwiyuh Michael Wepngong
Jun 06, 2026 7:57 PM
Kwiyuh Michael Wepngong
...
Insightful
Saving Changes...
Meerim SeiitovaGraduate Student| University of ArkansasFayetteville, AR, United States
In my experience, the key is transparency and a shared priority list. When demand is higher than capacity, I use a simple priority framework (like a numbered list of projects). We sit down with a team members, review the priorities together, and agree on what gets done first. As we have X people, Y tasks, and Z time, so something must move. Also, a weekly resource meeting (15–30 min) helps a lot. Everyone shares what is done, upcoming needs, and we adjust before things break. So, based on my experience, my key lesson learned is that no need to wait until a delay happens; plan together, communicate daily, and say "no" or "not yet" when there’s too much on one person’s plate.
...
1 reply by Srikana Ray
Jun 09, 2026 3:35 AM
Srikana Ray
...
Thank you for sharing your insights. I agree, collaboration and prioritization is key in resolving resource issues, while at times it can be quite challenging.
@Srikana , resource conflicts with Delivery Managers rarely get resolved at the project level - they get resolved at the organizational level. What I’ve found works is getting all competing demands visible to everyone at once, because transparency kills the politics fast. The key is having the resource conversation during planning, not when it’s already a crisis. And when you make the case, tie it to business outcomes, not just deadlines. If a resource is shared across three projects, plan accordingly - they’re never fully yours. The hardest part honestly isn’t the process. It’s the relationships you build before the conflict even happens.
...
1 reply by Srikana Ray
Jun 09, 2026 3:31 AM
Srikana Ray
...
Thank you sharing your valuable insights.
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
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.
...
1 reply by Srikana Ray
Jun 09, 2026 3:48 AM
Srikana Ray
...
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.
Financial Management Specialist | US Peace CorpsYaounde, Centre, Cameroon
Jun 05, 2026 4:53 PM
Replying to Lissette Indhira Pimentel Sosa
...
I've found that resource conflicts are usually easier to resolve when priorities are transparent and agreed upon at the portfolio or leadership level rather than negotiated project by project. When demand exceeds capacity, we can focus on making the trade-offs visible: what gets delayed, what risks increase, and what business impact each option creates. That helps stakeholders make informed decisions instead of treating it as a resource discussion alone.
@Srikana , resource conflicts with Delivery Managers rarely get resolved at the project level - they get resolved at the organizational level. What I’ve found works is getting all competing demands visible to everyone at once, because transparency kills the politics fast. The key is having the resource conversation during planning, not when it’s already a crisis. And when you make the case, tie it to business outcomes, not just deadlines. If a resource is shared across three projects, plan accordingly - they’re never fully yours. The hardest part honestly isn’t the process. It’s the relationships you build before the conflict even happens.
In my experience, the key is transparency and a shared priority list. When demand is higher than capacity, I use a simple priority framework (like a numbered list of projects). We sit down with a team members, review the priorities together, and agree on what gets done first. As we have X people, Y tasks, and Z time, so something must move. Also, a weekly resource meeting (15–30 min) helps a lot. Everyone shares what is done, upcoming needs, and we adjust before things break. So, based on my experience, my key lesson learned is that no need to wait until a delay happens; plan together, communicate daily, and say "no" or "not yet" when there’s too much on one person’s plate.
Thank you for sharing your insights. I agree, collaboration and prioritization is key in resolving resource issues, while at times it can be quite challenging. Saving Changes...
Community Champion
