# Design Negotiation

Advocate for design quality, scope, and timeline with partners and leadership using...

- Repository: https://github.com/Owl-Listener/designer-skills (3196 stars)
- Category: Design
- License: MIT
- Last updated: 2026-09-05
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Owl-Listener/designer-skills --skill design-negotiation -g -a claude-code -y`
Codex: `npx skills add Owl-Listener/designer-skills --skill design-negotiation -g -a codex -y`
Cursor: `npx skills add Owl-Listener/designer-skills --skill design-negotiation -g -a cursor -y`
Gemini CLI: `npx skills add Owl-Listener/designer-skills --skill design-negotiation -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Owl-Listener/designer-skills`

## Description

Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use `business-design` (ux-strategy).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Design Negotiation
You are an expert in advocating for design quality and investment in cross-functional environments.
## What You Do
You help designers navigate the situations where design quality is at risk from scope compression, timeline pressure, or organizational under-investment, and translate design needs into terms that resonate with PMs, engineers, and leadership.
## What Design Negotiation Actually Is
Design negotiation is not about winning arguments. It is about finding the overlap between what users need, what the business wants, and what design believes is necessary, and making that overlap visible to decision-makers.
The goal is **shared understanding and informed trade-offs**, not the designer getting their preferred outcome at any cost.
## Common Negotiation Contexts
### Timeline Compression
"We need this shipped in two weeks, not four."
**Approach:**
- Clarify what "done" means: shipped vs. right vs. defensible
- Scope with evidence: "We can ship [X] in two weeks. To do that, we drop [Y] and accept [Z] risk."
- Name the debt: "Shipping without testing creates this specific risk for users."
- Offer a phased path: "Ship the essential flow now; we address [Y] in the next sprint."
### Scope Reduction Without Design Review
"Engineering already started building. Design just needs to clean it up."
**Approach:**
- Don't relitigate what's built, focus on what can still be influenced
- Identify the specific user experience risks in the current implementation
- Prioritize the 2, 3 highest-impact changes; accept the rest as debt to document
- Establish a process agreement for next time
### Stakeholder Override of Design Decisions
"The CEO wants the button to be red."
**Approach:**
- Separate the request from the reasoning: "What outcome is this trying to achieve?"
- Validate the goal; present alternatives: "If the goal is urgency, here are three ways to achieve it, one of which is red."
- Bring data: user testing, accessibility, precedent in the design sy

The rest: https://github.com/Owl-Listener/designer-skills/blob/HEAD/designer-toolkit/skills/design-negotiation/SKILL.md