Managers negotiate long before anyone says, "Let's make a deal." You negotiate when product needs more engineering time. Two teams want the same launch window, or a direct report needs clearer expectations. These conversations shape trust, focus, and what your team can deliver.
Start building practical leadership skills with Bunch
Strong negotiation skills help managers uncover the interests behind competing positions, clarify priorities, and create workable tradeoffs without sacrificing important principles. The goal is not to win every exchange. It is to reach decisions people understand, can support, and will follow through on.
That makes negotiation a daily leadership practice, not a specialized sales technique. Before choosing a script or tactic, it helps to define what the skill actually includes and how it changes the way managers handle ordinary decisions.
Negotiation is the everyday work of reaching workable agreements when people have different priorities, constraints, or levels of authority. For a technology manager, that can mean aligning product and engineering on a roadmap. Agreeing with finance about project resources, setting expectations with a direct report, or clarifying ownership with a partner team. It is not limited to sales, procurement, or money. Whenever one person needs something from another, a negotiation may be taking place.
This makes negotiation a leadership capability, not a special tactic reserved for high-stakes meetings. Strong managers create enough clarity for people to make tradeoffs without damaging trust. They explain what matters, ask what matters to others, and look for an agreement that supports the wider goal. These habits overlap with leadership communication training, especially when a decision involves uncertainty or competing perspectives.
A position is what someone says they want. An interest is the reason that request matters. If a product manager says, "We need this feature in the next sprint," the position is the deadline. The underlying interests might include a customer commitment, a dependency for an upcoming launch, or concern that a problem will become harder to fix later.
Managers negotiate more effectively when they explore those interests instead of arguing over positions. Ask what outcome the other person is protecting, what constraint they are working within, and which part of the request is essential. An academic review recommends focusing on interests rather than positions. It also recognizes negotiation as relevant to work involving multiple parties (research on negotiation as a professional skill).
Imagine engineering can support only one of two roadmap requests this cycle. Product wants a customer-facing workflow, while security wants remediation work completed first. A positional conversation asks which team gets the slot. A manager using negotiation skills brings the interests into view: customer impact, risk exposure, effort, dependencies, and the cost of delay.
The resulting agreement might adjust scope, sequence a smaller security fix before the workflow, or set a clear review point for the next cycle. The manager has not made every party equally happy. Instead, they have made the tradeoff visible and created terms the teams can execute. Before proposing that kind of agreement, pause to prepare. Clarifying facts, priorities, principles, and alternatives gives the conversation a stronger foundation.
Preparation turns a tense request into a clear management conversation. Before you ask for roadmap priority, headcount, time, or stakeholder support, separate what you know from what you assume. Then decide what a useful agreement would look like for everyone involved.
A practical preparation model includes facts, priorities, principles, common ground, a walk-away point, and a BATNA, or best alternative to a negotiated agreement. These elements are also identified in an academic review of negotiation practice published by the National Center for Biotechnology Information. Use the model as a private checklist, not a script you must recite.
Good preparation creates room for curiosity. Once you know your facts and boundaries, you can spend less energy defending your position and more time hearing the interests behind the other person's request. That shift makes the next skill essential: listening.
Difficult conversations test more than your ability to make a persuasive case. They require you to understand what the other person needs, stay grounded when emotions rise, and make the next step clear. These negotiation skills matter when a product team challenges an engineering deadline, a colleague pushes back on feedback, or two functions want the same limited resource.
A position is what someone says they want. An interest is the reason that request matters. If a product lead insists that a feature must ship this quarter. The underlying concern might be a customer commitment, a launch dependency, or fear that the work will lose priority. Listening for that concern creates more options than arguing about the date.
Use active listening in a visible way. Let the person finish, reflect the key point in your own words, and check whether you understood it correctly. Then ask an open question. Try. "What problem would this solve for your team?" or "Which part of the plan creates the most risk?" Harvard's Program on Negotiation identifies open questions as a way to reveal interests and constraints. Learn more about open questions in negotiation.
Emotional regulation does not mean pretending that tension is absent. It means noticing your reaction before it controls your words. Slow the pace, take a breath. And name the observable issue rather than assigning motives. "I hear that this deadline feels non-negotiable" is more useful than "You are being unreasonable." If the conversation becomes unproductive. Suggest a short pause and agree on when you will resume.
Listening does not require unlimited flexibility. State what you can support, what you cannot commit to, and what information would change your view. A clear boundary might be, "We can add this work if we move the reporting milestone. But we cannot promise both with the current capacity." Patience gives people room to process the tradeoff. It also helps you avoid accepting a weak agreement simply to end an uncomfortable meeting.
Relationship-building can be modest and genuine. Ask how the other team measures success, acknowledge a valid constraint, or recognize the work they have already done. Harvard's Program on Negotiation reports that modest efforts to get to know one another may support collaboration and agreement. This is not a demand for personal closeness. It is an investment in trust and context.
For a deeper approach to the communication side of these moments, explore leadership communication training and these conflict resolution strategies. Once the conversation is calmer and the interests are visible, the next challenge is deciding which tradeoffs are both effective and ethical.
An ethical tradeoff does not mean every person gets everything they want. It means the manager makes the decision process clear, tests what each person actually needs, and avoids shifting hidden costs onto the least powerful stakeholder. That approach turns negotiation skills into a practical form of responsible leadership.
Start by separating positions from interests. A position is the stated request, such as "We need another sprint." An interest explains why: perhaps the team is protecting reliability. Meeting a customer commitment, or managing an unfamiliar technical risk. The distinction matters because interests create more possible options than a yes-or-no response. Research on negotiation recommends focusing on interests rather than positions, while also preparing facts, priorities, principles, common ground, and a realistic alternative if agreement is impossible. The academic discussion of negotiation skills provides that foundation.
Use the following comparison to choose a method deliberately. No approach is automatically ethical or unethical. The right choice depends on urgency, trust, power differences, the number of stakeholders, and whether the relationship must continue.
| Approach | What it emphasizes | Useful manager application |
|---|---|---|
| Positional bargaining. | Each side defends a stated demand and tests its limits. | Use when the decision is narrow, time-sensitive, and boundaries are already clear. |
| Collaborative negotiation. | People surface interests, share constraints, and create options together. | Use for recurring partnerships, cross-functional work, and problems with several possible solutions. |
| Ethical tradeoffs. | The manager balances value, fairness, risk, and consequences for affected people. | Use when resources are scarce or one group could bear an unseen operational or human cost. |
List the resources that can move without compromising core principles. Time, scope, sequence, ownership, visibility, decision rights, meeting load, development opportunities, and access to expertise may all matter. For example, a product manager might preserve a launch date by reducing scope, while engineering receives dedicated review time and a documented follow-up for deferred work. The tradeoff is not "engineering versus product." It is a transparent exchange between competing interests.
Ask each stakeholder to name their priority, their constraint, and the outcome they can support. Then test the option against a simple fairness question: who benefits, who carries the risk, and who gets a voice in the decision? If the answer reveals a serious imbalance, slow down and revisit the design. ESADE's overview of negotiation techniques notes that different approaches have different applications depending on context. Ethical judgment is what connects that flexibility to responsible management.
Managers use negotiation skills whenever people with different responsibilities need to agree on a workable path. In a distributed technology team, that often means making tradeoffs without relying on hallway conversations or informal influence. The goal is not to win every request. It is to understand the interests behind each position, make constraints visible, and agree on what happens next.
A product leader may want a customer-facing feature moved forward, while engineering is protecting reliability work or reducing technical debt. Treating the conversation as "feature versus engineering" creates a false choice. The underlying interests may be customer trust, learning speed, operational stability, or a commitment already made to another team.
Ask: "What outcome makes this request important now, and what risk are we accepting if we delay it?" Then compare options against shared criteria, such as customer impact, dependencies, risk, and reversibility. A fair next step might be to define a smaller discovery slice. Defer the full build until a named review date, or swap another item out of the sprint. Put the decision, owner, and revisit point in writing so a distributed team is not asked to remember an ambiguous agreement.
Cross-functional work often depends on a designer, security partner, data specialist, or manager who is already supporting several teams. A request for "just a little help" can still create an unseen queue. Negotiating well means describing the outcome needed, the minimum useful contribution, and the timing constraint instead of asking for an undefined commitment.
Ask: "What can your team support without putting its current commitments at risk, and which part of this work would create the most value?" Possible next steps include narrowing the scope or sequencing the work. You could also share a specialist for a defined window or exchange capacity with another team. Negotiation is not limited to money. Time, attention, access, and priority are resources too, as research on workplace negotiation notes.
A direct report may want more autonomy, while a manager wants earlier visibility into risks. A peer may prefer written feedback, while you expect concerns to be raised live. The visible disagreement is about frequency or format. The underlying interests are usually trust, clarity, safety, or a desire to avoid surprises.
Ask: "What kind of feedback helps you act, and what do you need from me when the stakes are high?" A fair next step is to agree on one concrete behavior. Also choose a communication channel and a review point. For example, the person might share a short risk note before a milestone, while the manager commits to responding within an agreed working window. For more guidance on handling the human side of these conversations, explore Bunch's daily leadership challenges.
Practice prompt: Before your next negotiation, write down each person's stated position, the interest that may sit behind it. One open question, and a next step that protects both sides' legitimate needs.
Practice clearer leadership conversations with Bunch
Five core negotiation skills are preparation, active listening, clear communication, emotional regulation, and value creation. Strong managers also practice patience and reflection. These skills help you understand interests, state boundaries, explore options, and choose a fair next step.
Start by defining the outcome and gathering facts. Next, identify priorities, constraints, common ground, and your best alternative. Then agree on the conversation process, listen for interests, and generate options. Close by confirming the decision, owners, and follow-up date.
Prepare before the meeting, ask open questions, and separate the person from the problem. Do not treat every conversation as a contest. Make tradeoffs visible, explain what you can and cannot change, and document the agreement. If emotions rise, pause and return to the shared goal.
No. Managers negotiate time, attention, scope, staffing, decision rights, feedback expectations, meeting access, and support. A clear exchange can protect focus while helping another team meet its needs. The best agreement reflects the interests and constraints on both sides.
Negotiation improves when you practice it in the moments that make up your workday. Use a short reflection after a difficult conversation, notice the interests beneath each position, and prepare one better question for the next discussion.
Bunch helps managers turn everyday leadership challenges into repeatable development through practical daily learning, AI coaching, and peer learning. Explore a focused way to keep building the judgment and communication your role requires.
Rick McCartney, DNP, is the innovative CEO of Bunch.ai, an AI-driven leadership coach. With a commitment to leveraging technology for global impact, Rick integrates clinical insights with strategic thinking to empower leaders in enhancing their organizations and teams.
