Why priority disputes stall delivery
Two teams can be fully booked and still disagree about which request should go first. The dispute is rarely about the work itself; it is about who has the authority to change the order and what evidence counts. When that authority is unclear, coordinators escalate to the most senior available person, which produces a decision but not a repeatable rule. The same argument then returns with the next competing request.
This is not the same as a capacity shortage. A shortage means the work cannot fit in the available hours, while a priority dispute means two valid requests cannot both be first. The distinction matters because a shortage calls for hiring, deferral, or scope reduction, and a dispute calls for a decision rule. Coordinators who confuse the two spend meetings negotiating hours instead of settling order.
Separate a conflict from a capacity shortage
Ask each team to state the work it cannot move and the date it is protecting. If both teams could finish on time with a small reordering, the problem is priority. If neither can finish even after reordering, the problem is capacity and belongs in a planning review. A short test keeps the dispute from becoming a general complaint about workload.
Record the test result in the request record so the next reviewer can see why the item was routed one way or the other. Capacity issues should carry an estimate of the missing hours and the date the gap appears. Priority issues should carry the competing commitments and the decision date. Mixing the two in one queue makes both harder to resolve.
Write the claim in one shared format
A useful claim fits in four lines: the commitment at risk, the competing commitment, the consequence of slipping, and the date a decision is needed. The coordinator writes the claim, not the requesting team, so the language stays comparable across disputes. Each side then adds one piece of evidence, such as a contract date or a dependent team's start date. The format forces the argument toward facts rather than volume.
Keep the claim short enough to read at the start of the meeting. Long narratives invite advocacy, bury the actual choice, and make the meeting longer than it needs to be. If a team cannot state the consequence in one sentence, the coordinator should ask for the downstream commitment that would break. That question usually produces the specific date or deliverable the decision needs.
Define who decides each class of dispute
Not every dispute needs the same judge. Routine reordering between two peer teams can often be settled by the coordinators using an agreed tie-break rule. Disputes that change a customer commitment or a contractual date need the owner of that commitment. Disputes that require new spending or overtime belong to the budget holder. Write the classes down so people know where a claim goes before it becomes urgent.
A named decision maker is better than a committee, because a committee tends to defer until the date is already lost and then meet again to explain the delay. Name a fallback with the same authority for holidays and travel. Publish the decision rights where teams plan their work, not only in a policy document. The goal is to route the claim correctly the first time.
Set a tie-break order the teams accept
Agree on a small order of precedence before the next dispute arrives. A common sequence is a fixed external commitment first, then work that blocks another team's start, then work that protects a recurring service, then internal improvement. The order is not a law of physics, but it gives the coordinator a defensible default when the evidence is close. Teams accept the rule more readily when they help set it.
Test the order against three past disputes and ask whether it would have produced the decision the group eventually made. If it would not, adjust the order now rather than during a live conflict. Publish one example so teams can see how the rule applies. A tie-break order that no one can explain in a sentence will not be used under pressure.
Run the fifteen-minute resolution meeting
Hold the meeting only when a claim is ready, and invite the two requesting owners plus the decision maker. The coordinator reads the claim, confirms the facts, and asks each side for one new piece of information. The decision maker then chooses, and the coordinator records the outcome before the meeting ends. Fifteen minutes is usually enough when the claim format is followed.
Do not reopen the underlying project plan in this meeting. If the decision depends on information that is not in the claim, assign the missing fact to a named person and set a new decision date. That step prevents a priority meeting from turning into a planning workshop. It also keeps the decision maker focused on the choice rather than the history.
Record the decision and its expiry
Every decision needs a date, an owner, and a review point. Write what was decided, what was displaced, and when the losing request will be reconsidered. A decision without a review point quietly becomes permanent, and the team that lost may route around it. Set the review date close to the next planning cycle so the trade-off can be revisited with fresh capacity data.
Tell both teams in the same channel where the claim was discussed, and link the decision to the affected requests. If the decision changes a commitment, update the cross-team commitment log rather than leaving the old date in place. The record should be short enough to read in a later audit. A clear decision is more useful than a perfect one that no one can find.
Publish the pattern every month
Count disputes by requesting team, by decision class, and by the rule that resolved them. Look for one team that repeatedly loses the same kind of claim, because that pattern may point to an intake problem or an unrealistic plan. Also track how often decisions were reopened, since a high reopening rate suggests the decision rights or evidence are wrong. Share the pattern without naming individuals.
Use the monthly review to adjust the tie-break order and the decision rights, not to relitigate individual calls. A small number of repeated conflicts usually explains most of the escalation load. When the same two teams collide every cycle, the fix may be a standing capacity reservation rather than another meeting. The rulebook should get shorter as the pattern becomes clearer.
Keep the rulebook usable
Store the rulebook beside the intake form and link it from the weekly review agenda. Review it once a quarter and remove rules that no longer match how work is planned. A rulebook that grows without pruning becomes another document nobody reads, trusts, or updates. The test is whether a coordinator can resolve a routine dispute without asking for permission.
Train new coordinators on the claim format and the tie-break order in their first week. Give them one worked example and one practice claim before they run a live meeting, then review their first real claim together. The weekly blocked-work review is a natural place to reinforce the same discipline. Consistency across coordinators is what makes the rulebook credible to the teams.
Sources
- U.S. Government Accountability Office, Standards for Internal Control in the Federal Government, reviewed November 10, 2026.
- Project Management Institute, PMBOK Guide, reviewed November 10, 2026.
- U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Project Management Specialists, reviewed November 10, 2026.
