Negotiation case study exercise for product managers

What is the challenge scenario?

A major streaming service is about to launch a feature that lets users build custom playlists and share them with friends. The internal announcement generated excitement, but three teams are now stuck in a standoff that could sink the launch.

Engineering wants to ship a minimal version in three weeks: create a playlist, generate a share link, done. Anything more risks the code quality they spent months rebuilding. Design says anything less than a full social experience will hurt the brand, and wants eight weeks for custom covers, collaborative editing and a friend activity feed. Business has a label partnership locked in for five weeks from now, needs the feature live before then, and wants sharing to be premium only so it drives subscription upgrades.

Three teams, three timelines, three definitions of success. You are the product manager. Your job is to find a path everyone can live with, without letting the product stall, the partnership fall through, or the feature ship half finished.

What are you asked to do?

Work through the standoff as a structured negotiation, not a vote. Start by capturing what each team is asking for and why it matters to them, then separate each team's stated position from the actual interest underneath it, for example Engineering's three week deadline probably protects against shipping bugs, not the number three specifically. Write a single sentence all three teams could sign off on as their shared goal. Sort eight proposed features into must launch, next release, or can wait, and be ready to defend each call. Generate at least three creative options that satisfy the core interest of two or more teams at once, thinking in terms of phased timelines, feature flags, premium gates or soft launches. Then respond directly to each team's pushback in one or two sentences, and close with a written proposal, in five short sections, that a real team could act on this week.

What does a strong answer cover?

This bootcamp does not publish a rubric for its practical challenge, so judge your own draft against the curriculum's own questions instead of a worked solution:

• Does the answer separate each side's stated position from the interest underneath it, rather than treating the position as the whole story?
• Does it name a shared goal all three teams could sign off on, not just a compromise nobody is happy with?
• Does it handle pushback from each team with a specific response, not a general reassurance that things will work out?
• Does it propose a trade or concession that protects product quality rather than simply splitting the difference between two timelines?
• Does the written proposal read like something a real team could act on this week, with a stated launch timeline and next steps?

Skills this exercise practises

Separating positions from interests, scoping an MVP under three competing constraints, generating options under real pressure, and writing a short, specific proposal that survives pushback from stakeholders who disagree with each other.

Which bootcamp does this challenge come from?

This is the practical challenge from Negotiation for Product Managers, Builders Camp's one week bootcamp on reducing conflict and improving outcomes across stakeholders, led by Andre Albuquerque across two 90 minute live sessions. Completing it counts toward that bootcamp's certificate. If stakeholder trade offs like this one come up often in your own work, the RICE prioritization framework guide gives you a repeatable way to justify a must launch call, and how to get promoted to senior PM covers the influence skills this exercise is built around in more depth. The product sense case study exercise in this same series practises a related skill: making a defensible call when the data itself is thin.

Builders Camp runs live and self paced bootcamps in product management and AI product building. See the Negotiation for Product Managers bootcamp for current cohort dates and the full self paced curriculum.