Operations · 5 min read

How to Resolve Conflict Between Sales and Operations

Treat recurring sales-versus-operations conflict as a problem in promises, capacity, incentives, or handoffs before treating it as a personality issue. Trace a few disputed jobs, define what can be sold under normal conditions, and create one visible process for exceptions that affect delivery or economics.

Start with specific broken promises

Choose a few recent jobs where sales and delivery disagreed. Record what the customer was promised, what operations believed was agreed, what information was available, and when the gap became visible. Avoid opening with broad claims that sales overpromises or operations resists growth. A concrete timeline makes it possible to distinguish missing information from a deliberate exception. Include successful handoffs too, so the team can identify conditions that make the relationship work rather than only collecting evidence against each other.

Identify whether the disagreement is about demand or capacity

Sales may be asked to fill a pipeline while operations is asked to protect service quality. Those goals can conflict when there is no shared capacity view. Show the constrained resource, current commitments, available delivery windows, and assumptions about new work. If demand is weak, delivery slack matters. If the queue is already full, another rush sale has a different consequence. A shared operating fact is a better starting point than deciding which department should be more cooperative.

Define the normal offer and handoff standard

Write the scope, lead time, required customer inputs, acceptance criteria, and conditions included in the standard offer. Agree what information sales must confirm before a job enters the delivery queue. Keep the requirement small enough to use consistently. An exhaustive handoff form that people avoid is not a reliable control. Operations should explain why each input matters, and sales should help identify where obtaining it would unnecessarily delay a normal purchase.

Make exceptions a commercial decision

A nonstandard promise should show the extra work, displaced commitment, cost, and proposed price or scope change. Name who can approve it and how quickly a decision is needed. Sales should not privately promise capacity it does not control; operations should not quietly veto a commercially attractive exception without explaining the tradeoff. A visible exception process lets the business choose a deliberate departure from the standard offer without turning every unusual request into a departmental dispute.

Align measures around useful delivered value

Booked revenue alone can reward promises the business cannot keep. Utilization alone can reward a schedule that leaves no room for necessary variation. Review a small shared view of accepted work, delivery reliability, quality, contribution, and cash timing where relevant. Do not add dozens of targets and expect balance to emerge automatically. Choose guardrails for the specific behavior causing conflict, and give owners a forum to discuss a tradeoff before a customer becomes its unwilling referee.

Close the loop after a difficult delivery

Review whether the miss came from an inaccurate promise, incomplete inputs, estimating error, capacity change, or rework. Decide which rule changes. Do not turn every review into a demand for both teams to communicate better. Name the information, owner, and point in the workflow where the next miss can be prevented. When the team intentionally accepted a risky exception, preserve that decision in the record rather than later treating the predictable cost as a surprise caused by another department.

Use the operating review to resolve recurring tradeoffs

Bring patterns and decision requests to the weekly review: repeated rush promises, incomplete handoffs, or a backlog concentrated at one step. Reserve separate working sessions for detailed process repair. The review should settle capacity allocation and exception authority, not require a fresh argument about every job. Include the people who can change the relevant commitments. A forum with no decision-maker can make both departments feel heard while leaving the customer promise unchanged.

Escalate conduct separately from process design

A clearer workflow will not excuse deliberate misrepresentation, disrespect, or repeated refusal to follow agreed rules. Address those behaviors with specific evidence through the appropriate management process. At the same time, do not use a conduct discussion to avoid repairing contradictory goals. Both can be necessary. Review the new process after several work cycles: fewer private exceptions, earlier escalation, and more reliable delivery are stronger evidence of progress than a temporary reduction in arguments.

Try the decision

The following fictional case is a practice scenario. Use the facts provided to identify the action that addresses the decision problem rather than its symptoms.

Questions operators ask