Interests vs Position in Negotiations — Scenario 3 — SLA between Strategic Client and Operations
Practical example on how to separate position and interest in a contractual SLA conflict between a strategic client and operations, to negotiate viable clauses.
When contractual and operational aspects clash, negotiations get stuck in legal terms and costs. Separating position and interest helps generate alternatives (exceptions, phases, pricing) that protect both parties.
Below: context, objectives, blocker, extraction of positions/interests, and practical options to move forward.
Scenario 3 — SLA between Strategic Client and Operations
Conflict: client demands a stricter SLA after a failure; Operations warns that meeting that SLA without adjustment implies higher operational costs.
Context
Key client demands a stricter SLA after a failure; Operations indicates that the new SLA entails higher operational costs and need for additional resources.
Objectives
Client: guarantee availability and obtain compensation for risks. Operations: ensure price and sufficient resources before accepting the new SLA.
Blocker
Vague master contract: the legal team did not define penalties or exceptions. Both parties fear exposure — the client to continuity, operations to unexpected costs.
Scenario detail and practical reminder
Practical note: After a critical incident, it is common for the affected party to request strong guarantees; however, immediately imposing penalties without analyzing resources and exceptions usually leads to breaches and litigation.
- Summary context: Strategic client requests a stricter SLA after service loss.
- Risk for Client: greater exposure to business interruptions if there are no clear contractual guarantees.
- Risk for Operations: cost overruns, team overload, and degradation of other services if conditions are accepted without resources.
Interests and positions
Strategic Client
Position: Impose a stricter SLA and possible compensations/penalties.
Interests: Guarantee service continuity, minimize business risk, and regain trust after the failure.
Operations
Position: Reject the SLA without price or resource adjustment; demand compensation/additional resources to assume the risk.
Interests: Avoid unexpected operational costs, ensure the team can meet the SLA without degrading other operations.
Difference between position and interest in this case
The position is the contractual demand (stricter SLA vs rejection without price). The interest is service security versus operational sustainability and cost control.
With clear interests, practical clauses can be negotiated: exceptions, compliance phases, escalation clauses, and adjusted pricing to cover risk.
- Examples of interest-based solutions (not just position-based):
- Pilot phase / trial period: apply stricter SLA for 3–6 months with monitoring and review.
- Exception clauses: define acceptable force majeure causes, maintenance windows, and penalty limits.
- Escalation and runbooks: establish procedures and response times, responsibilities, and escalation owners.
- Costing and pricing: adjust price or introduce premium fees for higher SLA levels (cost-sharing or additional availability charge).
- Metrics and reporting: agree on clear metrics (uptime %, MTTR, number of incidents) and a shared dashboard for transparency.
- Immediate practical action: Propose within 48–72h an addendum/RFC with:
- Specific metrics (e.g., monthly availability, MTTR) and calculation formula.
- List of exceptions and explicit maintenance windows.
- Resource impact and estimated cost to meet the SLA (hours, infrastructure, on-call).
- Pilot period, acceptance criteria, and review (e.g., 3 months, with evaluation meeting at the end).
- Compensation mechanism and maximum penalty cap, aligned with real risk.
- Monitoring and reporting plan (dashboards, alerts, and report cadence).
- Legal and operational approval before signing the addendum.
Quick recommendations
- Always separate position and interest: ask each party to summarize their interest in a clear sentence.
- Avoid automatic penalties without defining exceptions: document causes, limits, and caps.
- Propose a pilot with metrics and review: reduces risk and generates real data to adjust SLA and price.
- Quantify operational cost: operations should present incremental cost to meet SLA and propose associated pricing.
- Define an escalation mechanism and runbook to reduce MTTR and increase client confidence.
If you want, I can turn this into an SLA addendum (draft) or minutes with points to be signed by Client and Operations before moving forward.