跳到正文
cccskills
免费在 GitHub 公开

design-negotiation

Prepare design discussions about deadlines, scope, staffing, and stakeholder requests. Use research and metrics to explain user risks, propose alternatives, and document decisions so partners and leadership can make informed choices around shared goals.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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).

实测评分 未实测

查看安装方法

适用场景

  • Negotiating scope after a deadline is shortened
  • Discussing changes requested by leadership
  • Explaining the need for more design resources
  • Documenting agreements and accepted risks

包含的文件(1)

  • SKILL.md5.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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 system
  • Document the decision either way: what was decided, who made it, what the trade-off was

Headcount and Resource Requests

"We need a third designer on this project." Approach:

  • Quantify current scope vs capacity: "We have X design dependencies for Y delivery date; current capacity covers Z."
  • Translate to business risk: "Without the additional resource, we ship [specific feature] without design, or we push [milestone] by X weeks."
  • Propose alternatives if headcount isn't available: scope reduction, phased delivery, design system acceleration

Evidence-Based Advocacy

Design negotiation is strongest when grounded in evidence:

  • User research: "We tested this flow with 8 users; 6 couldn't complete the task."
  • Metrics: "The current pattern has a 34% drop-off at step 3."
  • Competitive context: "Every comparable product in this space supports X."
  • Accessibility and legal: "This pattern fails WCAG 1.4.3; that's a compliance risk."
  • Design system precedent: "The system already solves this — deviating creates maintenance debt." Avoid arguments based on taste ("this looks better") or authority ("I'm the designer") — they don't land with non-designers and they shouldn't have to.

Negotiation Principles

Start with the user problem, not the design solution

"Users are confused at this step" is more compelling than "this layout is unclear." Lead with the problem; the solution follows.

Acknowledge constraints

Engineers have technical constraints; PMs have delivery pressure; leadership has business goals. Dismissing these weakens your position. Name them first: "I understand we need this by Q3…"

Make trade-offs explicit

Decision-makers often don't know they're making a trade-off. Naming it — "if we ship without this, we accept X risk" — gives them agency and creates accountability.

Pick your battles

Not every design decision is worth negotiating. Reserve your credibility for the things that genuinely affect users. Let go of things that won't.

Document outcomes

When a decision goes against design's recommendation, write it down: what was decided, why, and what the expected impact is. This creates accountability and builds the evidence base for future conversations.

Building Long-Term Influence

Negotiation outcomes depend heavily on the relationships and credibility you've built before the negotiation:

  • Deliver consistently: teams trust designers who ship; trust opens room for pushback
  • Speak the business language: designers who understand revenue, cost, and risk are taken more seriously in strategic conversations
  • Bring data habitually: teams that routinely hear research in design reviews start expecting it everywhere
  • Celebrate shared wins: when design investment leads to measurable outcomes, make sure the team knows — publicly and with specifics

Best Practices

  • Prepare for high-stakes conversations in advance: know the data, anticipate objections, have alternatives ready
  • Never go into a negotiation without a fallback position — what's the minimum acceptable outcome?
  • Ask questions before proposing solutions; understand the other party's constraints before defending yours
  • Follow up in writing after verbal agreements — misremembers are common under deadline pressure

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

中文简介正在准备中。当前显示英语简介。

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills30582026年9月6日 更新

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

中文简介正在准备中。当前显示英语简介。

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills30582026年9月6日 更新

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

中文简介正在准备中。当前显示英语简介。

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills30582026年9月6日 更新

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

中文简介正在准备中。当前显示英语简介。

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills30582026年9月6日 更新

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

中文简介正在准备中。当前显示英语简介。

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills30582026年9月6日 更新

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

中文简介正在准备中。当前显示英语简介。

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills30582026年9月6日 更新

查看 Owl-Listener 的全部技能

报告此技能的问题