How leaders make cross-functional prioritization calls without losing trust

When two departments want the same people, equipment, or budget, the worst move is to decide it on the spot, in the room, and under pressure to “just get it done.” That is how you lose both the schedule and the trust (of your team and of leadership) at the same time. Believe it or not, this is a basic governance challenge, which comes down to deciding the rule before the conflict, in the open, and applying it the same way every time.

My rule centers on the consequence of delay, not seniority, and not first-in-line. For each piece of work, I ask one question: if this slips, what does the organization actually lose, and how badly? The work whose delay does the most damage moves first. Not the loudest department, and not the one that escalated hardest. That single move strips most of the politics out, because the argument becomes about evidence instead of status.

The tie-breaker, when two pieces of work carry similar consequences, is recoverability. I move first the work whose delay is hardest to undo. A slip you can buy back later with overtime or a vendor is cheaper than a slip that closes a window you never get back. For example, a product launch targeted for a specific event (e.g., a holiday) that, if it slips, the event is gone forever.

Trust survives all of this for one reason: it’s visibly fair. The department that loses the round sees the same scoring the winner saw, with nothing hidden, and the work that waits gets a real date that I hold to. People can accept losing a priority call. What they cannot accept is a process they have no way to predict or audit.

The discipline came from FAA facility sustainment, where far more work competed for the same limited crews and dollars than any cycle could fund. We ranked by risk to the operational mission, which failure would degrade service or safety the most, and we showed the math. Departments that lost a quarter stayed at the table because the same scoring applied to everyone, and they could see it.

Customer-facing work moves first. That’s the rule and it’s non-negotiable regardless of what internal work is competing for the same hours.

Running a bootstrapped company with a small team means resource conflicts cost you immediately, not eventually. There’s no buffer. And the debate over which work moves first takes time nobody has while creating friction between people who have to keep working together. So we removed the debate by agreeing on the rule before any conflict started.

The clearest example of what happens when I ignored it was a three-week stretch where I pulled my attention toward an internal build and stepped back from the customer conversations that drive our content and pipeline. Prospects who had been engaging went quiet. Re-engaging them took longer than the original gap did, and the internal work I prioritized didn’t recover that lost ground.

Here’s what most people miss about cross-functional trust on small teams. It doesn’t come from better communication or more check-ins. It comes from knowing the rule before you need it. When everyone agrees upfront that customer-facing work moves first, nobody has to make the case in the moment. The decision is already made, and losing the resource battle doesn’t feel personal because the criteria were never about whose work was more important.

When two departments need the same people or bandwidth, someone has to make the call and “whoever asks loudest” isn’t a decision framework. My default is to figure out which work creates the biggest downstream impact if it slips. Not which team is more frustrated, but which work sits on the critical path for everything that follows.

We faced exactly this situation during a large cross-functional program. Two teams needed the same subject-matter expert during the same window. We pulled up the dependency map and it became pretty clear: one team’s output was a prerequisite for three other milestones. The other team had a few weeks of schedule flexibility and could continue parallel work in the meantime. Decision made.

What I’ve learned is that people don’t necessarily need to like the answer. They need to understand how you got there. We walked both teams through the logic, not just the outcome. The team that waited wasn’t thrilled about it, but they respected that the decision wasn’t arbitrary. That’s what preserves cross-functional trust. The same teams you’re asking to flex today are often the teams you’ll need to partner with again next quarter.

Transparency is the tie-breaker’s best friend.

We focus on opportunity cost. When we don’t have all the resources we need, we ask the question of which of the two decisions will add the most value to the company as a whole rather than to only one department. Optimizing one team’s work to the detriment of another creates a scheduling issue that takes days to fix.

The practical way to determine whose team will get priority is to look at how the decision will impact clients. Specifically, we will look at which job has a more urgent external deadline or has a business relationship with an associated cost if the job is not completed on time. This question creates clarity within all of the teams faster than any higher level of seniority could.

As an example, when we had an equipment conflict last month, the team with the commercial client on a fixed handover date moved first and the residential team was rescheduled for a half day later. Both teams knew the justification behind the decisions within one hour and neither team pushed back because the reasoning was clear rather than dictated to them.

I believe that this is the thing that keeps cross-functional trust through the years intact. Knowing the why behind something is what keeps resentments from festering quietly in the gaps between divisions.

Our marketing and development teams have worked side by side for more than six months and have reached very reasonable due dates with strong reasons to go first. We initially observed that the lack of priority decision-making would hold back all efforts.

I established a simple rule. If the project has an external dependence that must be delivered (partner, launch date, or contract), that project would go first without question. While we may be able to move internal dates, there is no possibility of moving a person who is expecting their solar savings product to function, using the installer API that is not yet live. In cases where the two projects had external dependencies, both department heads and I would meet in the same room for thirty minutes and prepare a revenue or cost impact analysis for each project’s delay. The numbers allowed them both to make the final decision, and there were no feelings of having been overruled. The decision was based on mathematical facts only. This way, we have continued to build each other’s trust.

I decide by applying a basic priority stack. The department that is causing the delay moves first if it is causing a downstream delay for the other department. Not the loudest voice in the room, not the most senior person asking. We draw the dependency chain and the work that would block the most hands if it fails gets the resource. That one filter eliminates a lot of arguments before they get going. Then, when teams are aware of the rule in advance of the conflict, they cease lobbying and begin to bring data.

When the chain is really equal, the tie-breaker we use is capital exposure. The project with the greater amount of sunk cost or external commitments moves to the top of the list. There is a greater cost to holding up something with a vendor deadline than holding up internal development work. That is done in the open, both teams in the same room, so no one is left wondering how the decision was made. It’s that transparency that helps maintain the working relationship. People don’t mind losing a resource call if they saw the reasoning in real time. They don’t like it when they are given an answer without any reasoning.

When two departments need the same limited resource, the best way to decide what moves first is to use a shared rule before the debate becomes political. The framework I prefer is simple: rank both requests by business impact, urgency, dependency risk, and cost of delay. If one project unlocks revenue, prevents a deadline slip, or removes a blocker for multiple teams, it should usually move first.

What protects cross-functional trust is transparency. I have found that tension drops when both teams are evaluated against the same visible criteria instead of who argues harder or has more seniority in the room. I like to put both requests in one document, score them side by side, and explain the tradeoff plainly. Even when a team does not get the resource, they can usually accept the decision if the process feels consistent and fair.

My tie-breaker when scores are close is this: prioritize the work that will be harder to recover from later. In other words, an irreversible delay beats a reversible one. If delaying one request creates rework, missed handoffs, or downstream delays across several functions, that should outrank a request that can wait a week with limited damage.

A practical way to apply this is to review competing requests on a fixed cadence rather than as one-off fire drills. That keeps the decision attached to a repeatable system instead of personalities. It also gives teams a chance to update assumptions if urgency changes.

Clear rules preserve trust better than heroic compromises. People can disagree with the outcome and still respect the process when they know the same decision rule applies to everyone.

One approach that’s worked well for us at 180 Engineering is prioritizing work based on the cost of delay rather than which department has the most influence or is asking the loudest. In engineering recruitment, where we focus, it’s common for multiple clients or internal initiatives to compete for the same recruiting, sourcing, or technical assessment resources. When this happens, we ask a simple question: what is the business impact if this work doesn’t happen this week?

To give an example, if one client needs a manufacturing engineer for a plant expansion that starts next month, while another has an opening that’s been vacant for weeks without impacting operations, we’ll allocate resources to the role with the more immediate business consequence. This isn’t based on who submitted the request first, but the measurable impact of a delay.

Whatever criteria you use, I think the key to maintaining cross-functional trust is making the decision process transparent before conflicts come up. People are more likely to accept a decision they don’t like if they understand the framework behind it. When the rules are applied consistently, they recognize that they could be the ones on the more favorable side of similar decisions in the future. When teams get frustrated, I’ve found it’s because priorities seem arbitrary. A clear, shared understanding of the cost of delay has helped us make difficult decisions regarding resource allocation while keeping critical projects on schedule and preserving trust.

When departments have competing needs for a shared and limited supply of resources, the first priority to be addressed should be the work that is aligned with the common business objective as opposed to the employees or team members who have the loudest voice or fastest need for completion. The criteria I have used the most to make resource allocation decisions is to look for the project that has the potential of creating the most risk if the resource is not available and to identify the project that will provide the largest organizational gain if completed in an appropriate timeline.

Providing transparency around the trade-off being made provides the greatest opportunity to develop trust in the decision-making process. For example, in a mentoring program, one department may require resources for launching a communication campaign and another department may require resources for developing a participant matching process and onboarding process for participants. If developing a participant matching process presents the highest risk to impacting participant satisfaction, the work associated with developing a matching process should be given the first opportunity for resource allocation. At the same time, the department requesting resources for launching a communication campaign needs to be informed about the reason for the trade-off, the date the resources will not be available for allocation, and the date that their project will receive resources for completion. Employees will accept a “not yet” message much easier than they will accept an ambiguous “no” message.

Most organizations treat resource conflicts as a people problem. They are not. They are a decision architecture problem.

When two departments fight over the same limited resources, it usually means the organization has not clearly defined which outcomes it is actually optimizing for right now. That ambiguity creates the real bottleneck.

We use a simple but powerful decision rule with our clients: whichever initiative is closest to a direct revenue-generating or major risk-reducing outcome moves first. Not who shouted loudest. Not seniority. Not politics.

The tie-breaker matters far less than transparency. When teams can see the logic why this work was prioritized, what criteria were used, and what the business is truly optimizing for, trust survives even when they lose the resource. When the decision stays invisible, resentment fills the vacuum.

Leaders who get this right are not necessarily better at managing resources. They are better at managing decision clarity.

Build that layer first, and resource allocation becomes dramatically easier.

The decision rule we use is simple: prioritize the work that unblocks the most other work. When two departments need the same limited resource, the team with the louder voice does not win. The project that removes bottlenecks, reduces downstream delays, or enables multiple teams to keep moving gets priority.

Most cross-functional conflict happens when priorities feel subjective. The fix is to agree on the decision criteria before there is a conflict. We make the reasoning visible and tie it back to company goals, timelines, and dependencies. People are far more likely to accept a decision they disagree with when they understand how it was made.

A useful rule is: “Optimize for organizational throughput, not departmental urgency.” That keeps decisions objective, protects schedules, and helps preserve trust between teams because everyone is operating from the same framework rather than competing for attention.

The first thing I typically ask both sides is: “What happens to this project/plan/effort if we wait a week?” not “Which side is the loudest?” or “Which effort has the largest dollar amount allocated?”

Rather, “What will happen to this project/plan/effort in that extra week?”

Most battles over resource allocation are about people not being given voice in an organization-wide decision-making process.

I have also found that by articulating the reasoning behind your decisions OUT LOUD (not just stating your conclusion), you create an opportunity for both parties to hear how you arrived at that determination.

Then most people can understand the underlying reasons supporting a particular decision and will likely be able to live with it as long as they see that you were fair and logical.

If you simply provide each party with the results of your decision, but do not articulate the rationale, you are creating an environment where those individuals may develop resentment.

I’ve run into this situation quite a few times, especially when multiple teams are pushing hard toward important deadlines, and there aren’t enough resources to go around.

My approach is usually pretty straightforward. I sit down with the people involved and get a clear picture of what’s driving the request. Sometimes a project feels urgent because it’s highly visible, but when you dig deeper, another initiative carries a bigger business risk if it slips.

I tend to look at what happens if we don’t do the work right now. Will it impact a customer? Delay revenue? Create problems for other teams downstream? Those answers usually make the priority easier to see.

What I’ve found is that the decision itself is rarely what creates tension. Most of the frustration comes from people not understanding how the decision was made. That’s why I explain my thinking, share the trade-offs, and make sure everyone knows the decision is based on business needs rather than personalities or department politics.

There have been times when a team didn’t get the resources they wanted, but they still supported the decision because the process was transparent and consistent. Over time, that consistency builds credibility. People know they’ll get a fair hearing, and they know the same standards apply to everyone. That’s been one of the biggest factors in maintaining trust while keeping projects moving forward.

Not every case is at the same stage on the same day. We may have a new intake that needs immediate review, a case manager waiting on medical records, a demand team preparing a settlement package, litigation facing a court deadline, or accounting finalizing a client disbursement. Every team plays a role in moving a case forward, which means priorities have to be evaluated in the context of the entire case lifecycle.

The tie-breaker we use is identifying where a resource will create the greatest forward progress for the client. We look at what happens if the work does not move forward today. Will it delay evidence preservation, hold up treatment documentation, prevent a demand from being sent, affect a court deadline, slow settlement negotiations, or delay funds reaching a client after a case resolves? The work that removes the most significant bottleneck or carries the greatest time-sensitive impact typically moves first.

What helps us maintain cross-functional trust is that the decision-making process is consistent and visible. Priorities are not determined by which department is the loudest or which request arrived first. They are based on client impact, legal deadlines, and overall case progression. When our intake, case management, demand writing, litigation, settlement, and accounting teams understand the reasoning behind a priority shift, there is usually far greater alignment because everyone can see how the decision helps move a client’s matter closer to resolution.

In a personal injury practice, clients often spend months or years navigating recovery, treatment, insurance disputes, and legal proceedings. Our goal is to allocate resources where they create the most meaningful progress for the client, not simply where the next request appears in line.

I use a simple rule: whichever project directly impacts the customer or a hard deadline moves first.

I don’t favor a single department when two departments want the same developer, designer, or tool. I prefer to schedule a short 30-minute meeting with the department heads to ask these questions: “What breaks if this gets delayed?” and “Who does this affect most?”

Both departments feel more represented. A priority list is also helpful. I maintain a list of the agreed-upon department objectives.

Both departments understand the criteria and, therefore, the process, and minimize unnecessary and counterproductive conflict.

Trust is maintained through transparency. When people understand why a decision was made, they accept it, even when they do not love it.

One way of prioritizing resources is by assessing if either department’s function impacts the company’s bottom line in revenue and/or the stakeholder relationships. Assess whether the resources are being used for a need or a want. Limited resources need to be directed to where optimal ROI will yield the greater benefit instead of blindly allocating them based on familiarity among personnel, or rewarding who’s been patient the most in receiving funds (resources included). Patience should be rewarded because funding initiatives are often accompanied by an intake process; yet credence should be given to time sensitive objectives, then to variables that can elevate the company as a whole.

Create a pipeline of priorities so the departments are recognized for the value they deliver while ensuring no one is overlooked over time. Unused resources and resources materializing on the horizon can be channeled to those next in need. There needs to be a healthy system of checks and balances to keep the general company population satisfied. This comes down to communication and setting realistic expectations. Those who apply their resources well will be given preference if there’s a future last minute need. Reward accountability as you expand the limited resource pool to those in need.

Great question. We navigate this a lot as a growing small-business across the region. We often have to look at the profitability and long-term goals of the company.

If we have particular customers that bring in more revenue, we will prioritize particular projects or departmental goals to make sure we meet those needs. The customers keep us in business, as a distribution and ecommerce and warehousing business, so we’ve got to keep them happy, efficient, and satisfied.

As a 3PL fulfillment provider, we navigate this a lot. It’s a constant game of tetris trying to navigate how to take care of distribution sites, customers, and navigating macroeconomic trends.