How Operations Leaders Resolve Cross-Functional Priorities

When sales, finance, and operations all want the same limited capacity, the fix for me has been to stop debating requests and start debating one shared question: what moves the company forward most this quarter?

With a team of 11, we cannot afford politics. So when a tradeoff gets hard, I put the options side by side with the same three things: expected revenue or cost impact, effort required, and what we lose by waiting. Then one person owns the call, and everyone else gets to be heard before it is made, but not after. A decision process only keeps priorities clear if people know who decides and that the decision will hold.

The lesson from a hard tradeoff is that alignment comes from visible reasoning, not from compromise. When a team sees why one request went first, they accept the "not now" much more easily. Splitting capacity evenly to keep everyone happy usually leaves everyone shortchanged. I would rather say a clear no today than a vague maybe that eats the team's focus for weeks.

Rick Elmore, Founder/CEO, Simply Noted (simplynoted.com)

What keeps priorities clear for us is putting every request in the same currency, which in a company our size is usually engineering time.

Eprezto is a digital insurance broker, so a lot of what sales, finance and operations want ends up on the same small group of programmers. The clearest tradeoff we made was on carriers. The natural push is to connect as many insurers as possible, because more options feels like more sales. We had eight connected. Each one connects to us differently, with its own API quirks, and each one needs ongoing maintenance. So every carrier was quietly taking capacity away from everything else.

We cut the carriers we show from eight to between four and five. On paper that looks like offering less, but it helped on two fronts. One, it freed a lot of the engineering overhead that had been going to upkeep. Two, customers decided faster, because they had fewer options to compare. It also changed how we describe ourselves. We became more of a recommender than an aggregator.

What I took from it is that a tradeoff is much easier to align on when the hidden maintenance cost sits right next to the expected benefit. Each team can still argue for what it needs, but the conversation is about the same numbers.

My advice is to make the shared constraint visible first and then discuss priorities. A lot of fights over capacity are really disagreements about a cost nobody has written down.

Limited capacity should be allocated according to the constraint that governs the business, not the loudest executive request. If delivery talent is the bottleneck, every new initiative should be measured in units of that talent, including rework, meetings, and management oversight. Finance can then price the decision, sales can understand the tradeoff, and operations can protect the system.

I learned this while scaling quickly and discovering that apparent spare capacity was actually resilience. Filling every available hour increased short-term output, but it eliminated room for quality control and unexpected client needs. We began reserving capacity deliberately. That decision initially felt inefficient, yet it reduced escalations and made commitments more dependable across every department.

The decision process that keeps priorities clear is putting every competing request into the same unit, usually crew hours and cash collected, and making each leader argue in that unit. I'm a business coach, and construction and trades are my strongest area, where sales, finance and operations fight over the same people constantly. I'll call one client Brent. He runs an electrical contracting company with about 25 staff. Sales wanted crews on new jobs to keep customers happy, finance wanted crews finishing work that could be invoiced, and operations wanted time to fix callbacks. Whoever shouted loudest on Monday morning won, which meant new jobs kept starting while finished work sat uninvoiced and cash got tight. The hard tradeoff was pushing back the start date on a new job Brent really wanted, so crews could close out three jobs that were almost done. It felt like turning money away. In practice those invoices went out weeks sooner and payroll stopped being stressful. After that we built one weekly sheet showing crew hours available, jobs ready to invoice and new work requested, and every leader made their case against it. I learned the same thing running my own telecom contracting company with about 30 staff: work that is finished but not billed is the most expensive work you have. Alignment gets easier when nobody can win by being loudest, only by showing what the hours return.

1. A picture of shared capacity is that of a family car. Everyone in the family wants to use it for their errands on the Saturday morning. The issue isn't whose errands matter most to them. Instead, it is a matter of setting out the rules of the road as to who gets to use the car when before someone grabs the keys. At CheapForexVPS we set out the rules of the road for shared capacity at the start of every quarter when we're all less emotional. First the promises to existing customers are honored, then the issues that affect cash flow, and then those that help grow the pipeline. All the teams come to one monthly meeting and each brings all of the tradeoffs for their requests. Each request must state what else it will displace.

2. The hardest trade-off decision I made was pulling a deeply discounted onboarding promotion that the sales team was hot to launch. It was to be a loss-making product for the support and provisioning teams, but marginally cash positive for the finance team. In the end, I was the department head for the department whose number was on the line. Ops and finance have since begun bringing their issues to my attention well before they become problems, because they know that I will give something up to ensure that the customer experience is protected. This has the effect of frameworks (for alignment), but only because people follow the person who has sacrificed something for them.

I want sales, finance and operations to agree on available capacity before anyone promises delivery or approves a budget. At Ronas IT, our capacity check includes mentoring, interviews and reviews alongside project work. A schedule can show an open slot while the person in it still owes time to colleagues. For a proposed commitment, I'd ask the project manager and department lead who will own the new work and which assignment would move.

A decline in commercial workload showed us why recorded hours don't settle that discussion. Some colleagues said their projects had no tasks for them, although they hadn't checked with department leads about work elsewhere. We made the weekly checks with project managers and department leads more rigorous, applying the allocation procedure we already had. The difficult tradeoff was whether to treat an empty project queue as spare capacity or first confirm other available work. We chose verification. When someone reports a gap, the assigning leads need to check it and escalate the allocation question explicitly; a time sheet only describes hours already spent.

I'd carry that check into the next conversation between functions. If a person appears free, the people responsible for assignments should confirm their availability before sales makes another commitment. Name the owner of the new work and identify the existing priority that would have to move if the capacity doesn't fit. With those two answers in front of them, sales can discuss a promise and finance can assess its cost against the same operational choice.

We decide by asking one question: which choice gets cash back fastest without putting another project at risk?

In our business, those three pressures are buying more houses, keeping enough cash on hand, and how many rehabs our crews can actually handle. Chris will have a great deal ready to go, I'll have houses already under renovation, and our cash only stretches so far.

Last spring we said yes to too much. We had five houses under construction with crews that could really handle three, and everything slowed down. Holding costs piled up, and two houses hit the market weeks later than planned.

Since then we follow a simple rule. We don't buy a new project unless a current one is within about a month of listing, or the new one is light enough that it won't need our main crew. Every week we look at one shared list showing each house, its stage, and the cash tied up in it, so the tradeoff sits in front of both of us.

The lesson: limited capacity is easier to manage when you agree on the rule before the hard choice shows up, not during it.

In a GPU cloud, limited capacity isn't a metaphor. It's a fixed number of physical machines, and every team sees them differently. Sales wants to commit capacity to close deals, operations wants a buffer for failures and maintenance, and finance wants every GPU earning money. Without a clear process, each team optimizes for its own number. What helped most was a single shared view of capacity that everyone works from, reviewed together on a regular cadence, instead of three separate spreadsheets. The rule that came out of it is simple: we only commit capacity that is physically online or confirmed by a supplier, never capacity we expect to have. That rule came from seeing how risky the alternative is in a market where hardware deliveries slip. Promising something that arrives late damages a customer relationship far more than telling them honestly when you can deliver. Once all three teams agreed that a broken commitment was the most expensive outcome for everyone, tradeoff conversations got much shorter.

When sales, finance, and operations are all pulling on the same limited capacity, I make the tradeoff visible instead of letting the loudest team win. We score every competing request against the same two or three criteria, like revenue impact, cost to deliver, and how reversible the decision is, and we write the call down in one place so nobody is guessing why something got deprioritized. The hardest lesson for me came when we had to pause a new survey-matching feature that sales-minded partners wanted because the ops team was already stretched thin on support and quality review. Saying no cost us a short-term opportunity, but because everyone could see the reasoning, the same people brought sharper requests the next quarter. Alignment doesn't come from everyone getting a yes. It comes from everyone trusting the process that produced the no.

Prioritize by impact on customer experience and cash flow, not by department. We rank requests by expected revenue or retention effect and by operational cost to deliver, then reserve a fixed share of capacity for urgent ops, a share for high-revenue sales, and a small buffer for experiments.

At Cyber Techwear we once delayed a major marketing push because order fulfilment was at limit. Sales would have spiked but returns and support load would have doubled.

We chose a smaller, phased launch and improved coordination between marketing and operations by publishing a simple weekly capacity scorecard so everyone sees tradeoffs before campaigns roll out.

When sales, finance, and operations are competing for the same limited capacity, I've found that priorities stay clearest when every request is evaluated against the same three factors: customer impact, financial impact, and operational feasibility. In event rentals, we once had overlapping high-value opportunities competing for the same inventory and delivery resources, and the instinct was to prioritize the largest revenue number. Instead, we looked at margin, logistical complexity, client commitments, and the risk each option created for other events already on the calendar. That exercise showed us that the biggest booking was not necessarily the best business decision once the operational strain was factored in. The lesson was to agree on decision criteria before the pressure hits, rather than letting the department with the loudest or most urgent request set the priority. Since then, putting the tradeoffs on one shared scorecard has made difficult capacity decisions faster, more transparent, and much easier for every team to support.

When resources are tight, keep your priorities clear. Only a small, cross-trained team should be able to handle a promise from start to finish. Limiting same-day and next-day pickup or ship promises was better than overloading the stores or leaving the sales floor short. Cross-training the team to cover the work and granting the people closest to the work the authority to accept or reject a promise enabled us to make the harder tradeoff of turning down some fast-fulfillment commitments to protect the team's ability to fulfill the ones we've committed to. That established the joint sales and operations priority of making promises the store is able to fulfill.

I put one ranking question in front of all three teams before any capacity gets spoken for. Which job moves revenue soonest at a margin we can live with? Sales, finance and operations score every request against that, and the resulting order sits on one shared list anybody can open.

The tradeoff I keep running into in agency work is a rush launch for a big new account landing the same week as overdue fixes on an account that's already paying. Sales wants the launch. Finance wants the invoice that follows it. Operations has the same few people for both. Putting the cost of delay beside each item usually settles it, because a slipped fix on a live account reads as churn risk and a slipped launch reads as a start date moving a week.

Sales gets one protected exception. MIT research found leads are 21x more likely to qualify when contacted within five minutes, so follow-up capacity gets reserved before anything else is scheduled.

Once the rule is agreed ahead of time, the argument happens over the list on Monday and the rest of the week is execution. People will accept a ranking they helped write even when their own item lands third.

The hardest version of this in my business is a fully booked Saturday. Sales wants to say yes to every request. Finance wants the highest-value jobs filled first. Operations knows how many cleaners can physically be in how many homes before quality slips. All three are right, and that's the problem.

What I'd put in place is one written rule for who wins a conflict, agreed before the busy week starts. Mine is that the number of qualified people on the schedule is the ceiling, and nobody argues past it. Within that ceiling, the jobs with the tightest turnaround window go first, because a missed same-day turnover costs a host a guest review and a bad one follows the host for months.

The lesson I keep coming back to is that the tradeoff gets easier once everyone can see the same capacity number. Most of the friction I watch teams create comes from each function holding a private version of what's possible. When the number is shared and posted where all three can see it, the conversation shifts from whose priority wins to what fits under the ceiling.

I'd also say the first no is the one worth practicing. Turning down a job you can't staff well tends to cost less than doing it badly, and it gives the team a precedent they can point to later.

One safeguard against priority theater is separating allocation from commitment. A team may allocate discovery capacity to a sales opportunity without committing delivery capacity before requirements, margin, and operational impact are known. That protects planning integrity and prevents provisional promises from becoming fixed priorities. A shared log should show the threshold, accountable executive, and review date.

I learned this when a modest customer accommodation expanded into exceptions across implementation, support, and engineering. Each request seemed reasonable, yet the combined load eroded delivery predictability. The correction was to measure exception volume as a capacity consumer. Alignment improved once finance could see margin leakage, operations could see queue growth, and commercial leaders could see the cost of turning exceptions into promises.

One hard lesson we learned is that a delayed no can cause more harm than an early no. In growth environments, we often keep too many projects active to avoid conflict. Everyone leaves meetings believing their work remains possible. Operations then faces confusion, deadlines clash, finance handles the fallout, and sales struggles with broken promises.

We now keep a stop list alongside our priority list. Every major commitment must include something we will pause, reduce, or decline. We review both lists together to make trade-offs clear. This improved teamwork because leaders began asking which customer promise or internal project mattered most instead of expecting operations to manage everything.

When sales, finance, and operations are competing for the same limited capacity, I keep priorities clear by forcing every request through the same three filters: customer impact, financial impact, and operational urgency. In pool repair and construction, I've learned that the loudest request isn't always the one that should move first. On one project, we had to choose between starting a profitable renovation, handling several equipment repairs, and addressing an active pool leak that was consuming water every day; we prioritized the leak because delaying it would increase the homeowner's damage and ultimately create more work for our team. The difficult part was explaining why immediate revenue wasn't the only factor, so I started making the reasoning behind scheduling decisions visible to everyone involved. My biggest lesson was that cross-functional alignment improves when teams agree on the decision criteria before competing priorities arrive, rather than negotiating the rules during a crisis.

When sales, finance and operations all want the same engineering time, I make the decision process about the customer's job rather than about which team argues loudest. At Paperless Pipeline we ship upgrades roughly every 6 weeks, and every cycle starts with a short written list of what is competing for that capacity, who asked for it and which brokerages it would help. Putting each request on one page with its cost and its beneficiary takes the politics out of it quickly.

The rule underneath is that we add what helps and leave out the rest. A sales request that would win one big deal but complicate the product for every agent usually loses, because a simple system is what keeps agents using it and what keeps support load low. Finance gets a say on cost and timing, operations gets a say on what will break, and the final call sits with one person so nobody is left guessing who decided.

After a hard tradeoff, I write down why the losing request lost and when it will be looked at again. Teams accept a no much more easily when the reasoning is visible and the door is not closed forever. Boring, written priorities beat clever negotiation every time.

Finance is often asked to settle disagreements over capacity, but we believe its real role is to set clear rules before conflicts begin. We use different scenarios rather than relying on a single forecast, showing the downside, expected outcome, and upside for each demand on capacity. Our operations team explains what could go wrong in each scenario, while sales identifies commitments that cannot be changed.

This approach helps everyone understand the risks before making a decision. In one case, we chose a margin commitment because it made scheduling more stable across weeks. We learned that margin per unit can be misleading when changes in demand create extra costs. We improved teamwork by giving these changes a clear cost instead of treating them as a minor inconvenience.

When demand exceeds capacity, I keep priorities clear by grounding the discussion in reliable KPIs, making the constraint visible, and bringing forward a practical plan rather than letting the issue linger. As a Senior Process Engineer, I was asked to plan a major truck-route expansion and quickly found the Ship Dock lacked the capacity and equipment to support it. I presented the data showing the rollout plan would not work and proposed stack-to-light technology; the team approved the change. The lesson was that a difficult tradeoff is easier to align around when people can see the operational facts and discuss the fix without blame. That keeps the focus on what the operation can support, rather than on competing opinions.

When sales, finance, and operations compete for limited capacity, priorities and ownership need to be explicit rather than left to the person who is most willing to help. I saw this with an inside sales representative who understood the company well and became the go-to person for customer service, IT, finance, and sales. As he took on more requests, his core work and professional growth suffered, while the company became too dependent on his knowledge. The difficult tradeoff was recognizing that saying yes to every department was not serving the organization well. The lesson for me is that alignment means giving work clear owners, not expecting one reliable person to carry it all.

When I started as COO, I looked at the company as an organization and at the resources I had. I drew diagrams of who comes to me, with whom, and with what. Then I set levels for every person, and each level could decide up to a certain financial limit. I said those numbers out loud to people, and I explained that everything you do can actually be translated into money. Say you lost 10 hours, and your rate is $20 an hour. Then the cost of your mistake is $200. That's what kept sales, finance and operations from fighting over the same hours. The tradeoff got a number on it. My direct reports collected information from their reports, in a cascade, all on one system. Up top, I only collected escalations.

"When there are several competing interests that require attention, it is important to CLEARLY COMMUNICATE THE AVAILABLE RESOURCES (or capacity) prior to agreeing to do additional work. Sales, Finance, and Operations should review the demands on the organization, the estimated cost associated with meeting those demands, and the organization's ability to fulfill the demands prior to establishing deadlines. By doing so, the organization avoids having one group create expectations for another that cannot be met.

Small operational changes can result in unanticipated wide-ranging effects. For instance, the introduction of a new product requires additional inventory, additional information, and additional fulfillment planning. By preparing for the requirements of introducing a new product at an early stage, organizations will be better able to manage the associated workload. Additionally, when organizations include in decision-making the individuals who are responsible for implementing the decisions made, organizations will experience a greater level of commitment from their employees and fewer unexpected events."

Set prices in advance, using a volume price ladder.

In one case a small law firm asked for 50 embroidered crewnecks with a logo bigger than usual on the chest (which in turn uses about 40% more thread). When they pushed on price, instead of just discounting (sales) or refusing to because the embroidery is more expensive (finance) or wondering about thread usage and embroidery machine running time (production), we quoted the same price for 50 crewnecks as usual but a smaller price per crewneck if they ordered 80. This way we protected the margin (finance), pointed out that bigger logos use more resources (production) and gave the customer an incentive and option to order more (sales). The customer ordered a sample first, showed it around and then went ahead with the order.

Formulating such rules takes time and cannot be done ad hoc for each customer. But if you have them, you will find that many discussions are made easier because instead of endlessly debating how much you could discount this time for this customer, you can just point to your volume price ladder.

Make time to write such rules, but not during a hectic phase!

When multiple teams are competing for the same limited capacity, I try to understand two things before deciding what goes first: the business impact of each request and what happens to everyone else if one team gets delayed.

I actually dealt with this situation while managing a program where several teams wanted to run different experiments on the same customer journey. Marketing wanted to introduce personalized content, product wanted to test UI changes, sales wanted to improve customer messaging, and finance wanted to simplify the checkout process.

The problem was that teams were running experiments simultaneously at the same time, which sometimes affected the same parts of the customer experience. This made it difficult to figure out which changes were actually producing the results we were seeing.

To avoid this, we decided to coordinate the experiments through a shared schedule. I worked with the teams to understand their priorities and the business reasons behind them. We agreed to prioritize the checkout experiment first because customers were dropping off during that process and this had a more immediate business impact. The UI improvements were still important but they were not impacting the business as much as compared to the checkout.

The bigger challenge came when one of the experiments, originally planned for two weeks, needed additional changes and more time. As the data couldn't confirm if that experiment was a success or a failure, if we kept extending it, the other teams would have to keep waiting.

I discussed the situation with the team to understand how much additional work was needed and what would happen if we paused the experiment. After exploring the options, we agreed to pause it, allowed other teams to move forward, and schedule the revised experiment for a later date. This gave the original team time to make the necessary improvements without holding up everyone else.

What I took away as a learning from this experience is that prioritization doesn't end once everyone agrees on a schedule. Plans change, experiments take longer than expected, and teams discover things they didn't anticipate at the start. What matters is being willing to revisit those decisions, explain the tradeoffs, and make sure one team's delay doesn't unnecessarily affect everyone else's work.