HKSM

Negotiation is a structured dialogue to reach agreement among parties with different interests or constraints. In projects, it is used to resolve conflicts, secure resources, and agree on scope, cost, schedule, and contract terms.

Definition

See definition above. The focus is on reaching acceptable solutions while protecting project objectives and relationships.

Key Points

• Used across the project life cycle to align expectations, resolve conflicts, and agree on commitments.
• Effective negotiation focuses on interests and outcomes, not positions or personalities.
• Preparation is critical: know objectives, limits, alternatives (BATNA), and decision authority.
• Use objective data and criteria to support proposals and build trust.
• Aim for mutual benefit while safeguarding scope, schedule, cost, quality, and risk constraints.
• Document decisions and update plans, contracts, and logs to reflect agreements.

Purpose

Enable the team and stakeholders to reach workable agreements that support project goals, maintain relationships, and manage constraints. Negotiation helps balance competing needs, clarify trade-offs, and reduce the risk of future disputes.

Facilitation Steps

• Prepare: define objectives, priorities, walk-away limits, and BATNA; analyze stakeholders, interests, and power dynamics.
• Plan the session: set agenda, roles, ground rules, time-box, and decision process; gather relevant data and options.
• Open: state the shared purpose, confirm scope of issues, and agree on process and etiquette.
• Explore: use active listening and questions to uncover interests, constraints, and success criteria; surface assumptions.
• Create options: brainstorm packages and trade-offs; apply objective criteria and risk-impact thinking.
• Bargain: exchange concessions conditionally and transparently; check feasibility with the team.
• Close: summarize agreements, confirm commitments, capture actions, owners, and dates; define follow-ups and escalation paths.
• Communicate and update: publish outcomes and update plans, baselines, contracts, and logs.

Inputs Needed

• Objectives, priorities, and constraints for scope, schedule, cost, and quality.
• Stakeholder analysis, requirements, and engagement strategy.
• Relevant data: estimates, performance metrics, risks, and benefits.
• Contracts, terms, procurement strategy, and organizational policies.
• Decision rights, authority limits, and approval thresholds.
• Alternatives and trade-off options for scope, resources, and timing.

Outputs Produced

• Agreements, commitments, and documented decisions.
• Updated project management plan and baselines, as needed.
• Change requests and contract amendments, if applicable.
• Updated risk, issue, and assumption logs.
• Action items with owners and due dates, and updated communication records.
• Stakeholder engagement plan updates.

Tips

• Separate people from the problem; stay respectful and focus on interests.
• Come prepared with data, scenarios, and packages of trade-offs.
• Make concessions conditional and reciprocal; avoid giving value without getting value.
• Use open-ended questions and active listening to uncover hidden interests.
• Be mindful of culture and power dynamics; ensure the right decision makers are present.
• Document immediately and confirm shared understanding in writing.

Example

A key stakeholder requests a new feature late in the release. The project manager prepares alternatives and impacts, proposes deferring two low-priority items, and negotiates to include the new feature with no schedule slip by rebalancing scope. The agreement is recorded as a change request and baselines are updated.

Pitfalls

• Negotiating positions instead of underlying interests.
• Poor preparation or unclear authority and limits.
• Conceding too early or without reciprocity.
• Ignoring objective data, leading to unfair or risky outcomes.
• Failing to document agreements and update plans.
• Excluding key decision makers, causing rework or reversal.

PMP Example Question

A supplier requests a mid-project price increase due to raw material costs. What should the project manager do first to prepare for the negotiation?

1. Meet the supplier and agree to split the difference.
2. Review the contract terms, gather cost and performance data, and define the BATNA.
3. Escalate to the sponsor and ask them to decide.
4. Send a warning letter threatening termination.

Correct Answer: B — Review the contract terms, gather cost and performance data, and define the BATNA.

Explanation: Effective negotiation starts with preparation using objective criteria and clear alternatives. Acting without data or authority increases risk of a poor or unenforceable agreement.