liveBook · Manning

Negotiation and compromise

As explained in Think Like a Software Engineering Manager

Negotiation and compromise is a technique for resolving conflicting interests by seeking mutually acceptable tradeoffs.

Negotiation and compromise resolve conflicting priorities by finding mutually acceptable tradeoffs. In engineering work, focus on shared objectives, involve stakeholders early, and protect the quality and integrity of the process. section 12.4

Use the technique to navigate resistance:

  • Bring product managers and other stakeholders into discussions of engineering practices and technical debt. section 12.4
  • Explore creative alternatives that balance competing interests instead of accepting the first proposed tradeoff. section 12.4
  • When agreement remains difficult, use Disagree and Commit while continuing to manage the conflict constructively. section 12.4

Flexible return limits

While addressing abuse of returns, an engineering leader raised engineering-excellence concerns during roadmap discussions. The existing limit was hardcoded, required code changes and deployments for adjustments, and applied uniformly across markets. A configurable limit per marketplace offered a way to align business needs with a stronger engineering approach. section 12.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Offers principle-level guidance and an example, without detailing a formal negotiation procedure.
Examples
Uses a returns-abuse problem involving hardcoded, uniform return limits and proposed marketplace-specific configuration.
What it assumes
Assumes participation in product planning and familiarity with engineering practices, technical debt, and stakeholder collaboration.
What you can do after
Apply shared-objective negotiation to balance competing interests while preserving engineering-process quality.
How it connects
Links stakeholder collaboration, technical debt, engineering excellence, iterative improvement, and Disagree and Commit.

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.