# How Leaders Resolve Competing Project Priorities - Published: 2026-10-19 - Author: [Economist Zone](https://economistzone.com/author/economistzone-com.md) - Topics: [Q&A](https://economistzone.com/qa.md) - Source: https://economistzone.com/qa/how-leaders-resolve-competing-project-priorities/ - Publisher: Economist Zone ### Standardize 90-Day Tradeoff Reviews When teams at Simply Noted fight over priorities, it is almost never because someone is wrong. It is because every project is being judged on a different scorecard. Sales wants the feature that closes a big account, operations wants the fix that stops robot downtime, and marketing wants the launch it already announced. What fixed it for us was forcing every competing project onto one page with the same three questions: what revenue or cost does this move in the next 90 days, what breaks if we wait a month, and who is blocked without it. Each team lead fills it out for their own project, and then we compare them side by side in a single 30 minute meeting. No slide decks. The second rule is that I make the call at the end of that meeting if the group cannot. Delays spread when decisions float. A clear no on Tuesday is far better than a maybe that lingers for three weeks while two teams quietly work on both. Once people saw their project evaluated honestly against the same criteria, the arguments got shorter. They did not always win, but they understood why, and that is what keeps alignment from turning into resentment. Rick Elmore, Founder and CEO, Simply Noted --- ### Limit Focus to Three Accountable Priorities I force the group to cut the list to three priorities, no more, each with an owner, a metric and a deadline. Three quarters ago I dropped a twenty-slide strategy deck for a single page with just that information, and it changed how well priorities stuck. If something doesn't fit in those four columns, it waits for next quarter. Anyone can see who owns what and by when, so the argument gets shorter. --- ### Quantify the Cost of Inaction When product, marketing, and engineering leaders all present convincing arguments for why their project deserves top priority, open debates in executive meetings almost always devolve into political maneuvering or analysis paralysis. The framework that brought discipline to our roadmap was enforcing a one-page strategic decision brief framework centered around the 'Cost of Inaction.' Before any initiative is scheduled, the project owner must answer three questions: What is the measurable financial or customer churn impact if we do nothing for 90 days? Which core metric will this demonstrably move within 14 days of launch? And what existing project will be paused to staff it? Forcing teams to quantify the downside of waiting rather than just painting optimistic growth scenarios quickly weeds out low-leverage pet projects, allowing the organization to focus resources on the initiatives that actually protect stability and revenue. --- ### Expose Tradeoffs and Pilot Close Calls At Ascendant NY, our commitment to individualized, client-centered care provides a clear anchor. I resolve competing priorities by requiring each team to state the tradeoff it asks the organization to accept. For each discretionary project, the sponsor identifies the outcome, the people affected, the capacity required, and which planned work would move later if the project starts now. That final question matters because several proposals can appear equally valuable until their practical costs are visible. I compare options against one near-term objective and available capacity, preventing departments from arguing their own importance. If two options remain close, I favor the one that can be evaluated through a limited, low-risk initial phase without committing the full organization. The decision is complete when everyone knows what begins, what is deferred, and how much capacity the initial phase may consume. When several worthwhile operational ideas compete, I recommend asking which one most directly helps each client feel seen, valued, and supported, while remaining realistic for the team to carry out. That gives different functions a shared basis for the choice and keeps departmental ownership from determining the order. It applies after required clinical, safety, privacy, licensure, and documentation responsibilities are accounted for. Those responsibilities should be handled according to established requirements before discretionary projects are prioritized. --- ### Map Handoffs Before You Rank Tasks When teams disagree, I recommend mapping dependencies before ranking projects. In our organization, one approach that helped was dividing a mission-critical project into distinct areas of ownership so team members could make decisions within their domains. This approach clarified responsibility across team members and made cross-team coordination clearer. Ask each project lead to state the next concrete deliverable, what another team must provide first, and the consequence if that handoff moves. That often reveals that the real choice is not between whole projects. It is between a few near-term decisions that either release or block later work. Sequence those decisions, assign each one to the appropriate person with the role and authority to own it, and set a deadline for the handoff. Keep the conversation focused on the next commitment rather than defending an entire project. If a conflict does arise, the accountable leader should choose based first on client care and safety, required regulatory or operational obligations, and then existing commitments, and communicate the resulting sequence to everyone affected. For priority disputes, I would use the same structure: each owner identifies the first decision their area needs and any dependency crossing into another area. Leadership then resolves those cross-team conflicts and sets the handoff sequence. People do not need to agree on every project at once. They need clarity about who decides, what comes next, and where coordination is required. --- ### Separate Commitments From Stretch Goals We use quarterly goal planning to make competing priorities comparable before the calendar makes the decision for us. At Ronas IT, we shape proposed goals through NCT: Narrative, Commitment, Tasks. The narrative gives the business reason for the goal, the commitment says what the team is taking responsibility for, and the tasks expose the work behind it. A proposal isn't ready for the quarter while those parts are still vague. We also record the result we commit to deliver separately from the more ambitious result we're aiming for. That distinction matters when two teams both have persuasive requests. If one proposal depends on every stretch result landing, it can't take the same place in the plan as work we've committed to deliver. The discussion becomes concrete: which outcome must happen this quarter, what work does it require, and what can wait if the time isn't there? A bounded choice preserves the ambition without treating it as a promise. During planning, we also look at current commitments and available time. If too many projects land on one person, we revisit priorities and redistribute work. We treat staffing as a separate check on the chosen commitment, because a clear goal still needs available people behind it. My advice is to put rival proposals into the same commitment-and-stretch format before debating whose project is more important. Decide which committed outcome takes precedence, name the work that follows it, and leave the ambitious outcome conditional on capacity. The next project starts with a recorded priority and an explicit capacity condition. --- ### Prioritize Customer Harm Over Department Demands The quickest way to resolve competing priorities is to stop debating which project matters most and start looking at which delay creates the biggest problem. As Director of Technology at 7aSavvy, I'd focus on three things: customer impact, operational urgency and dependencies between teams. In SBA lending, for example, fixing a borrower application issue that prevents document submissions should take priority over adding a new dashboard feature. One directly affects the borrower's ability to move forward, while the other can usually wait. One approach I find particularly useful is **having teams agree on the problem and success criteria before discussing solutions.** Instead of letting every department defend its preferred project, ask what happens if the work is delayed and who gets affected. This makes trade-offs easier to explain and keeps discussions focused. I've found that teams align more quickly when priorities are tied to real workflow problems rather than individual department preferences. --- ### Govern ROI Through Shared Value Metrics Resolving project prioritization deadlocks requires shifting the focus from departmental features to a unified definition of operational ROI. Stakeholder friction usually stems from siloed protectionism and a lack of shared success metrics for the organization as a whole. In enterprise systems delivery, the most effective resolution is forcing leadership-specifically the operations and IT directors-to agree on a measurable "definition of done" before a single line of code is written. This is not a standard requirements list; it is a commitment to the specific business process improvement that justifies the capital investment. A Value Realization Framework managed by a cross-functional governance board provides the necessary structure to maintain this alignment. Every initiative must be scored against three non-negotiable pillars: direct impact on the primary value chain, departmental readiness for change, and long-term technical scalability. In manufacturing environments, this often surfaces as a conflict between procurement's desire for better vendor management and the warehouse's need for faster inventory tracking. A governance-first lens deprioritizes any project that cannot prove a measurable improvement to a core metric, such as total lead time or cost per unit. This approach replaces subjective departmental wishlists with objective priorities focused on the enterprise's financial health. When the decision criteria are tied directly to the bottom line, the political friction tends to evaporate because the data makes the decision for the team. Success is no longer about which project sounds more important, but which one effectively moves the needle on the organization's primary value chain. --- ### Make Requesters Name What Slips 14 requests reached our marketing team in a single week last month. Every one of them was marked urgent. We keep one shared sheet now. Anyone who adds a request has to write down which existing item moves back to make room. The arguments stopped landing on me, because people were negotiating with a colleague's line on the sheet instead of with marketing. In a firm of about 60, the sales team and the analysts who pair founders with investors know each other well enough to settle it in a message. You would expect more friction. There is some, but it happens on Monday instead of on Thursday when the deadlines start slipping. My own requests, I notice, are the ones that keep drifting back to the top. --- ### Score Proposals and Assign Final Authority When teams disagree on priorities, the fastest way to get to a decision is to stop debating projects in the abstract and force every option through the same scoring lens. What has worked best in my organizations is a short prioritization framework with four factors: expected business impact, urgency, implementation effort, and strategic fit. Every project gets discussed against the same criteria, and one person is clearly responsible for making the final call after input is heard. In practice, this removes a lot of emotional or political bias. A project that sounds exciting can lose priority if it has weak near term impact or pulls resources away from a more urgent bottleneck. On the other hand, a less flashy project can move to the top if it solves a clear operational problem or unblocks other work. As a founder working across SaaS products, content systems, and automation workflows, I have found that the most useful shift is separating ideas into three buckets: must do now, schedule next, and not now. That sounds simple, but it prevents teams from treating every request like an immediate priority. Once people see that saying "not now" is different from saying "never," alignment gets much easier. One approach that helped us was requiring each proposed project to include a one sentence goal, the metric it should improve, and the cost in time or resources. If those three things were unclear, the project was not ready for prioritization. That alone reduced delays because the team stopped spending meetings debating vague initiatives. The key is consistency. If priorities are reviewed with the same criteria every week or every two weeks, teams trust the process more, and disagreements become shorter and more productive. Alignment usually breaks down when the decision method changes from project to project. --- ### Plot Urgency Against Impact I've watched teams burn three weeks debating while our main competitor launched two features. My solution is blunt: I draw a grid - urgent vs impact - and force everything onto it. Did this at 28 different companies working on content intelligence. Your favorite project that you've been nursing? It lands at spot #7. Revenue drivers shoot to the top right. The grid doesn't lie and people stop fighting when they see the numbers. This saved us in AI search where delays kill you. No perfect consensus exists anyway. Someone decides and the visual makes it clear which way to go. --- ### Empower a Decision Owner A decision owner helps determine priorities without necessarily being the most senior person in the room. This person gathers input from finance, commercial, and operational leaders, identifies the main constraint, and recommends a sequence. The role is to review the evidence before making the final call. This approach ensures that decisions are based on facts rather than seniority alone. This structure also makes meetings more productive. Instead of leaving with several agreements but no clear commitment, teams leave with a decision, a reason, and a next step. Leaders who disagree are asked to explain what evidence would change their view. This keeps discussions constructive and allows decisions to be revisited when facts change, preventing the search for consensus from causing delays. --- ### Let Guest Check-Ins Set Order The approach I rely on is a ranking rule everyone agrees to before a disagreement ever starts. In turnover cleaning, that rule is the next guest check-in time. A unit with a 3 p.m. arrival goes ahead of a unit with a Saturday arrival, whoever is asking and however loud the ask. When two teams want the same crew, I check one thing: which unit has the earlier check-in. That settles it in minutes, usually the same morning. The team that goes second still gets a firm start time, so they can plan around it and tell the host what to expect. Delays spread when a priority question sits open. One undecided hour pushes back every job after it that day, and crews end up idling in their cars waiting for word. A rule that already exists removes the waiting, because nobody has to ask me what the answer is. I keep the rule written down where everyone can see it, and I give the reason each time I apply it. Ties go to the longer job first, since it needs the most runway. --- ### Test Urgency Through Delay Consequences I use deadlines as diagnostic tools, not just delivery dates. When every project is described as urgent, asking what specifically changes if it misses a particular date reveals which deadlines are real, which are negotiable, and which were inherited without examination. A deadline challenge session helped create alignment by requiring each project owner to explain the consequence of a one-week, one-month, and one-quarter delay. Projects with little difference between those scenarios moved lower, while work tied to genuine windows or cascading dependencies moved higher. The exercise was surprisingly effective because it replaced emotional urgency with evidence. Teams gained permission to defer noncritical work, and the resulting plan contained fewer priorities, clearer owners, and far less last-minute reshuffling. --- ### Fast-Track Reversible Calls We separate reversible decisions from irreversible ones. Teams often spend too much time discussing work that can be adjusted later while delaying choices that limit future options. We start by asking whether a project creates a one-way door or a two-way door. This helps us understand how carefully we need to consider the decision. For reversible decisions, we set a short deadline and move forward. For choices that are difficult to undo, we take more time and assign one owner to make the final call after hearing the team's views. This keeps consensus from becoming an excuse for delay. We improve speed by acting quickly on low-risk choices and saving deeper discussion for decisions that need leadership attention. --- ### Clear Obligations, Then Remove Bottlenecks I resolve disagreement before project advocacy begins by separating core requirements from discretionary priorities. Work required for patient safety, licensure, privacy, regulatory or other established obligations is handled according to the applicable requirements before discretionary projects are ranked. For the remaining projects, I ask the team to identify three things: the decision each project enables, the other work that depends on it, and the consequence of waiting 30 days. That comparison exposes sequencing issues that broad labels such as urgent or strategic can obscure. I then name an appropriate decision owner with authority for that type of decision and set a firm decision deadline. The owner considers input from the affected teams, makes the decision within established responsibilities, and records what starts now, what follows, and the conditions that would justify revisiting the order. Agreement is useful, but unanimous agreement should not become a prerequisite for action. A clear decision, with a defined basis and review trigger, keeps debate from becoming an open-ended delay. One approach that has helped in multi-location operations is a dependency-first review. Each project sponsor identifies the next concrete deliverable and whether another team is unable to proceed without it. Projects that remove a genuine dependency can move ahead of projects that can advance independently, after required clinical and operational responsibilities are accounted for. This changes the discussion from whose proposal is more persuasive to which sequence allows the organization to move responsibly. It also gives teams a clear explanation for the order and a specific point when deferred work returns for review. --- ### Choose What Serves More Charities I try to lead with questions before opinions. When priorities compete, one question helps settle most decisions: Which project solves a real problem for the organizations we serve? Disagreements often drag on when teams focus on their own goals. Bringing the conversation back to the customer gives everyone a shared basis for making a decision. Our goal is to get Pledge It into the hands of as many people as possible so we can do the most good. That means prioritizing projects that help charities solve problems they couldn't address before, especially those that make a meaningful difference for smaller organizations. For example, one team might propose a feature requested by a large prospective customer, while another wants to simplify setup for nonprofits where one person manages an entire event alongside their regular job. The first opportunity is exciting, but the second could benefit many more organizations. Looking at both through the same lens makes the decision clearer. Once we agree on a direction, I give the team clear guidance and let them execute. Making a sound decision early gives everyone more time to focus on the work. --- ### Tie Requests to Named Revenue Stakes When we were building Pageloot and Closer AI simultaneously, we hit the exact moment you're describing. The AI team wanted resources for the hackathon push, the QR platform had paying customers waiting on features, and our small group couldn't do both at full speed. We had to choose. What stopped the spiral was stopping the debate. Instead of another meeting about priorities, we tied every request to a named customer or a specific revenue consequence. Not "this feature is important," but "DeLonghi's campaign goes live in 14 days and we're the tracking layer" or "we don't ship the payment agent, we forfeit the hackathon slot." Once the cost of each choice was named and real, not abstract, the decision made itself. You can't argue with a deadline that has a customer's name on it. The thing that actually worked wasn't a framework, it was killing the permission to debate a priority twice. First discussion locked it in. If someone opened it again without new information, we said no. That sounds harsh until delays start compounding and suddenly six weeks of work is at risk because you never actually committed to a direction. We committed, owned the cost of the other path not taken, and moved. Most teams skip that last part. They want the decision to feel fair, so they reopen it. It never does. The unfairness is the point. One project wins because it has a real deadline or real revenue attached. That's not a bug in your process, it's the signal that your process is working. --- ### Honor Fixed Client Promises I bring the disagreement back to a fixed date and a fixed promise. In production, the calendar does a lot of the deciding. A shoot date, a client delivery, or a live event does not move because two internal teams prefer different projects. So when producers or departments pull in different directions, I ask three things out loud: What did we already promise a client? What has a hard date this week? What can wait without breaking trust? Writing that down ends most of the debate. The project with a shoot tomorrow beats the nice-to-have internal piece. The open client commitment beats the internal idea that still has no owner. The approach that helps us align is a short priority list owned by one person for the week, usually the producer running the busiest jobs. Everybody can see what is first, what is second, and what is parked. If someone wants to jump the line, they have to say which commitment gets delayed. That keeps the argument about tradeoffs instead of volume. It is not always tidy. Sometimes two client dates collide and we add crew or reset a delivery. At least the choice is named before the delay spreads quietly. --- ### Preserve Options Across Connected Claims Priority alignment improves when related files are viewed as one risk picture rather than separate assignments. A workplace injury can involve a compensation claim, a third-party investigation, proof, and deadlines that do not move together. I have found that assigning each piece independently invites duplication and can leave the consequential gap unnoticed. The practical fix is a review focused on overlap. The team identifies which facts serve multiple tracks, which deadline cannot be extended, and what action might affect another recovery. For example, liability investigation may come first when records are perishable, although compensation continues separately. The first task should preserve options across the matter, not serve the busiest desk. --- ### Convene Focused Evidence Reviews I stop delays by carving out dedicated decision time to separate true emergencies from items that only feel urgent. During that session I ask the team to present evidence, risks and the long-term consequences so we can weigh trade-offs without daily distractions. That focused process makes it easier for everyone to agree which projects deserve attention first and to turn the decision into clear, realistic actions. It is a practical, honest approach that reduces back-and-forth and keeps the organization moving. --- ### Center Choices on the Meal-Log Moment The approach I use is one question every project has to answer before it gets any attention: what does this change for the person holding the phone at the moment they log a meal? In a food-scanning app that moment is where people either keep going or quit, so it works as the ranking for everything else. A model upgrade, a new regional dish list, a faster offline queue and a nicer weekly report all sound urgent when each team pitches its own. Put them next to that one question and the order mostly sorts itself within a single meeting. The work that touches the logging moment goes first. Everything else gets a written date for when it will be looked at again, so nobody feels dropped. Two habits keep delays from spreading. Every item leaves the room with one named owner, and the decision gets written down in a sentence anyone on the team can read later. When a team reopens the argument two weeks on, you point at the sentence and ask what changed. A concrete case of the pattern: when someone proposes adding more dishes, the question is whether a person in Medellin or Bogota would see their own plate recognized the first time they scan it. That answer is usually clear fast, and it settles the debate without anyone having to win it. --- ### Cap Concurrent Initiatives When teams disagree, I make tradeoffs explicit by asking anyone proposing that a project move forward to identify what would receive less attention as a result. Leadership should name the constrained resource, the decision owner, and the deadline for deciding. I have each project lead state the immediate outcome, the consequence of waiting, and the minimum commitment needed to make progress. The decision owner then sets a limited number of active priorities based on available capacity and places the remaining initiatives on a "not now" list, defining clear conditions for when those deferred projects can be reconsidered. Required security, privacy, contractual, and operational work remains scheduled. The final decision should be communicated promptly, including what was selected, what was postponed, and when the choice will be reviewed. If the available information is incomplete, I recommend choosing the smallest reversible commitment that can resolve the uncertainty rather than starting several projects at once. One approach that has helped us is using a fixed work-in-progress limit. Before another major project enters active production, the team confirms that there is capacity for it or identifies which existing project will be completed, intentionally paused, or moved out of the constrained stage. A shared board should show only approved active work, its owner, and the next deliverable. New requests can still be captured, but they don't quietly become active assignments. This keeps capacity visible and makes priority changes deliberate. If an urgent project enters, leadership can identify which current project changes status and communicate that decision to everyone affected. --- ### Pair Every Yes With a Pause I bring competing priorities to a decision with one rule: nothing new goes on our project list until the person championing it names which current project will wait to make room. That turns a broad argument about what matters most into a choice between two specific pieces of work, and the choice is made openly with whoever owns the project that would be paused. In my view, delays spread from work that has been half-dropped rather than deliberately paused: no one ever decided it should stop, so everyone keeps planning around something that isn't really moving. Once a project is put on hold on purpose, the people who rely on it can adjust the same day instead of discovering the stall weeks later. Every yes comes with a 'not yet' attached, and the sooner you say which one, the less it costs. --- ### Compare Outcomes, Risks, and Effort When teams disagree about priorities, I'd bring the discussion back to two questions: What outcome matters the most right now, and what happens if each project waits or gets blocked? That helps move the conversation beyond each team's workload to the consequences for the business. One practical approach is to compare competing projects in a short, shared priority list. For each project, capture the expected benefit, the consequence of delaying it, and the effort required. A deadline tied to a customer commitment, for example, should carry different weight from an internal target that can move. There also needs to be one person in my case, POD leads, accountable for making the final call. Teams should have the opportunity to explain their concerns, but agreement from everyone shouldn't be a condition for moving forward. The decision should make clear what comes first, what will wait, and when those choices will be reviewed. That gives teams a usable plan and prevents the same disagreement from reopening every week. --- ### Related Articles - Make Better Tradeoffs on the Product Roadmap When Capacity Is Tight: Advice for Digital Product Teams - Team Meetings: Leaders Share How They Cut Time Without Losing Alignment - Centralize or Decentralize Operations: One Decision Rule That Actually Improved Results