design-ops

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Design Ops & Handoff

Design Ops 与交付

Operational processes that make design teams effective — sprints, handoff, rituals, documentation, and quality assurance.

让设计团队高效运转的运营流程——冲刺、交付、固定机制、文档和质量保证。

Design Sprints

设计冲刺

A 5-day process for solving big problems and testing ideas before committing engineering resources. Based on Jake Knapp's Sprint methodology developed at Google Ventures.
一个为期 5 天的流程,用于在投入工程资源之前解决重大问题并验证创意。基于 Jake Knapp 在 Google Ventures 开发的 Sprint 方法论。

When to Sprint

何时使用冲刺

SignalSprint Is RightSprint Is Wrong
Problem clarityBig problem, unclear solutionSolution already known — just build it
StakesHigh — wrong direction costs monthsLow — easy to course-correct later
Team alignmentDisagreement on approachTeam already aligned
Time pressureNeed answers this weekCan run a longer discovery process
ComplexityCross-functional problemSingle-discipline task
信号适合冲刺不适合冲刺
问题清晰度问题重大,解决方案不明确解决方案已经明确——直接开发即可
风险与代价高——方向错误可能浪费数月时间低——之后很容易调整方向
团队共识对实现方式存在分歧团队已经达成一致
时间压力本周内需要答案可以开展更长时间的探索流程
复杂度跨职能问题单一职能任务

The 5-Day Structure

5 天结构

DayFocusKey ActivityOutput
MondayMapDefine the challenge, set a 2-year goal, map the problem space, pick a targetSprint questions, problem map, target area
TuesdaySketchReview existing solutions, each person sketches solutions individuallySolution sketches (one per person)
WednesdayDecidePresent sketches, vote (dot voting + decider picks), create storyboardStoryboard for prototype
ThursdayPrototypeBuild a realistic facade — just enough to testTestable prototype
FridayTest5 user interviews, observe together, identify patternsGo/no-go decision with evidence
天数重点核心活动产出
周一梳理定义挑战、设定 2 年目标、梳理问题空间、选定目标Sprint 问题、问题图谱、目标领域
周二草图审视现有解决方案,每个人独立绘制解决方案草图解决方案草图(每人一张)
周三决策展示草图、投票(圆点投票 + 决策者最终选择)、创建故事板原型故事板
周四原型构建逼真的仿真界面——足以用于测试即可可测试原型
周五测试开展 5 次用户访谈、共同观察、识别规律有证据支持的推进/不推进决策

Sprint Team

冲刺团队

RoleCountResponsibility
Decider1Has authority to make final calls. Usually PM or founder
Facilitator1Runs the process, keeps time, manages energy
Designer1-2Leads sketching, builds prototype
Engineer1-2Feasibility gut-checks, helps prototype
Domain expert1-2Customer support, sales, marketing — whoever knows the user
Total5-7More than 7 is counterproductive
角色人数职责
决策者1拥有最终决策权,通常由 PM 或创始人担任
引导者1组织流程、控制时间、manage团队精力
设计师1-2主导草图绘制并构建原型
工程师1-2快速判断可行性、协助构建原型
领域专家1-2客服、销售、市场等最了解用户的人员
总计5-7超过 7 人会适得其反

Sprint Rules

冲刺规则

  1. No devices during working sessions — full attention
  2. Work alone together — individual sketching, not group brainstorming
  3. The Decider decides — democracy is slow; one person breaks ties
  4. Prototype, don't build — facade quality, not production quality
  5. 5 users is enough — you'll see 85% of usability issues with 5 participants

  1. 工作期间不使用设备——保持全神贯注
  2. 一起工作,但各自独立思考——分别绘制草图,而不是集体头脑风暴
  3. 由决策者拍板——民主决策效率较低;由一个人打破僵局
  4. 做原型,不要做产品——只需达到仿真质量,而非生产质量
  5. 5 名用户就足够——通过 5 名参与者即可发现 85% 的可用性问题

Design-to-Development Handoff

设计到开发的交付

Handoff is the #1 source of quality loss in product teams. The goal: engineers should never have to guess.
交付是产品团队中质量损失的首要来源。目标:工程师永远不需要靠猜。

Handoff Maturity Levels

交付成熟度等级

LevelDescriptionSymptom
1. ScreenshotDesigner sends a static imageEngineers guess spacing, states, behavior
2. Annotated mockupRedlines, spacing calloutsBetter, but still missing states and edge cases
3. Interactive specFigma/design tool with inspect mode, component linksEngineers can extract values, but behavior is undocumented
4. Full specAll states, transitions, error handling, responsive behavior, tokensEngineers build exactly what was designed
5. IntegratedDesign and code share a component system; handoff is a conversation, not a documentMinimal spec needed — shared language does the work
Target: Level 4 minimum. Level 5 for mature teams.
等级说明典型问题
1. 截图设计师发送静态图片工程师只能猜测间距、状态和行为
2. 带标注的设计稿包含红线标注和间距说明有所改善,但仍缺少状态和边界情况
3. 交互式规范Figma/设计工具中包含检查模式和组件链接工程师可以提取数值,但行为没有文档说明
4. 完整规范涵盖所有状态、转换、错误处理、响应式行为和令牌工程师能够准确构建设计内容
5. 集成化设计与代码共享组件系统;交付是持续对话而非静态文档只需最少的规范——共享语言即可完成协作
目标:至少达到 Level 4;成熟团队应达到 Level 5。

What a Complete Handoff Includes

完整交付应包含的内容

Every screen or component handoff must cover:
CategoryRequired Items
LayoutSpacing (in tokens, not pixels), alignment, responsive breakpoints, container behavior
ContentFinal copy (not lorem ipsum), character limits, truncation rules, localization notes
StatesDefault, hover, focus, active, disabled, loading, empty, error, success — for every interactive element
BehaviorWhat happens on click/tap, keyboard interaction, drag, swipe. Transition details
ResponsiveHow the layout adapts at each breakpoint. What reflows, stacks, hides, or changes
TokensColor tokens, typography tokens, spacing tokens — never raw hex/px values
AccessibilityFocus order, ARIA roles, screen reader announcements, touch targets, color contrast
Edge casesLong strings, empty data, error recovery, offline behavior, permissions
AssetsIcons (SVG), images (with alt text), animations (specs or files)
每个界面或组件的交付都必须涵盖:
类别必需项
布局间距(使用令牌而非像素)、对齐方式、响应式断点、容器行为
内容最终文案(而非 lorem ipsum)、字符长度限制、截断规则、本地化说明
状态默认、悬停、聚焦、激活、禁用、加载、空、错误、成功——适用于每个交互元素
行为点击或轻触时发生什么、键盘交互、拖拽、滑动,以及转换细节
响应式布局如何适应每个断点;哪些内容会重排、堆叠、隐藏或发生变化
令牌颜色令牌、排版令牌、间距令牌——绝不直接使用原始十六进制或 px 数值
无障碍聚焦顺序、ARIA 角色、屏幕阅读器播报、触控目标、颜色对比度
边界情况长字符串、空数据、错误恢复、离线行为、权限
资源图标(SVG)、图片(包含替代文本)、动画(规范或文件)

Handoff Anti-Patterns

交付反模式

Anti-PatternProblemFix
"It's in Figma"No context, engineer must reverse-engineer intentWrite behavior notes on every frame
Happy path onlyOnly the ideal flow is designedDesign all states before handoff
Pixel specs"24px left margin"Use tokens:
spacing-md
Verbal handoff"I'll explain it in standup"If it's not written down, it doesn't exist
Big-bang handoffEntire feature dropped on engineering at onceHand off in slices that match sprint stories
No error states"We'll figure out errors later"Error states are designed first, not last

反模式问题修复方式
“就在 Figma 里”缺少上下文,工程师必须反向推测设计意图在每个画板中写明行为说明
仅覆盖理想路径只设计了理想流程交付前设计所有状态
像素规范“左边距 24px”使用令牌:
spacing-md
口头交付“我会在站会上解释”没有写下来的内容就不算数
一次性交付将整个功能一次性交给工程团队按与 Sprint Story 匹配的切片分批交付
缺少错误状态“错误以后再说”错误状态最先设计,而不是最后补充

Team Rituals and Cadences

团队固定机制与节奏

Core Design Rituals

核心设计固定机制

RitualFrequencyDurationPurposeWho Attends
Design critiqueWeekly45-60 minImprove work-in-progress through structured feedbackAll designers
Design-eng syncWeekly30 minAlign on upcoming work, resolve handoff questionsDesign lead + eng lead
Design reviewPer milestone30-60 minStakeholder sign-off on directionPM, design, eng leads, stakeholders
Handoff sessionPer story/feature30-45 minWalk engineering through specs, answer questionsDesigner + implementing engineers
Design QAPer release60-90 minVerify implementation matches specDesigner + engineer
RetroBi-weekly or per sprint45 minImprove the processWhole product team
Design sprintAs needed5 daysSolve big problems, validate risky ideasCross-functional team (5-7)
固定机制频率时长目的参与者
设计评鉴每周45-60 分钟通过结构化反馈改进进行中的工作所有设计师
设计与工程同步会每周30 分钟对齐即将开展的工作,解决交付问题设计负责人 + 工程负责人
设计评审每个里程碑30-60 分钟由利益相关者确认设计方向PM、设计负责人、工程负责人、利益相关者
交付会议每个 Story/功能30-45 分钟向工程团队讲解规范并回答问题设计师 + 负责实现的工程师
设计 QA每次发布60-90 分钟验证实现结果是否符合规范设计师 + 工程师
复盘每两周或每个 Sprint45 分钟改进流程整个产品团队
设计冲刺按需5 天解决重大问题、验证高风险创意跨职能团队(5-7 人)

Running Effective Design Critiques

开展高效的设计评鉴

Format: Presenter shares context (2 min) → Group reviews silently (3 min) → Structured feedback (15-20 min per piece) → Next steps (2 min)
Critique rules:
  1. Presenter states what feedback they want — "I need help with the empty state" not "What do you think?"
  2. Feedback references principles, not preferences — "This violates Fitts's Law" not "I don't like the button placement"
  3. Describe problems, don't prescribe solutions — "Users might miss this action" not "Make the button bigger"
  4. No defending — presenter listens, asks clarifying questions only
  5. Written notes — someone captures all feedback items with action owners
格式: 展示者分享背景(2 分钟)→ 小组静默评审(3 分钟)→ 结构化反馈(每件作品 15-20 分钟)→ 下一步(2 分钟)
评鉴规则:
  1. 展示者说明希望获得哪类反馈——“我需要有关空状态的帮助”,而不是“你们觉得怎么样?”
  2. 反馈应基于原则而非个人偏好——“这违反了 Fitts's Law”,而不是“我不喜欢这个按钮的位置”
  3. 描述问题,不要直接指定解决方案——“用户可能会忽略这个操作”,而不是“把按钮做大”
  4. 不要辩护——展示者只需倾听并提出澄清性问题
  5. 记录书面笔记——由一人记录所有反馈事项及行动负责人

Handoff Session Structure

交付会议结构

  1. Context (5 min) — What problem does this solve? What user story?
  2. Walkthrough (10-15 min) — Designer walks through the flow, screen by screen
  3. States and edge cases (10 min) — Hover, error, empty, loading, responsive
  4. Tokens and components (5 min) — Which design system components to use, which tokens
  5. Questions (10 min) — Engineers ask anything unclear
  6. Action items — What needs clarification before build starts

  1. 背景(5 分钟)——要解决什么问题?对应哪个用户 Story?
  2. 演示(10-15 分钟)——设计师逐屏讲解整个流程
  3. 状态和边界情况(10 分钟)——悬停、错误、空、加载、响应式
  4. 令牌和组件(5 分钟)——应使用哪些设计系统组件和令牌
  5. 提问(10 分钟)——工程师提出所有不明确的问题
  6. 行动事项——开发开始前还需要澄清哪些内容

Documentation Standards

文档标准

File Organization

文件组织

project-name/
├── exploration/          # Early concepts, discarded directions
│   └── v1-concepts/
├── current/              # Active, approved designs
│   ├── flows/            # User flows and journey maps
│   ├── screens/          # Screen-level designs
│   └── components/       # Component-level specs
├── assets/               # Production-ready exports
│   ├── icons/
│   └── images/
├── handoff/              # Handoff documentation
│   └── [feature-name]/
└── archive/              # Past versions (never delete, move here)
project-name/
├── exploration/          # 早期概念、已放弃的方向
│   └── v1-concepts/
├── current/              # 当前有效且已批准的设计
│   ├── flows/            # 用户流程和旅程地图
│   ├── screens/          # 界面级设计
│   └── components/       # 组件级规范
├── assets/               # 可用于生产的导出文件
│   ├── icons/
│   └── images/
├── handoff/              # 交付文档
│   └── [feature-name]/
└── archive/              # 历史版本(绝不删除,移至此处)

Naming Conventions

命名约定

ElementConventionExample
Files
[project]-[feature]-[variant]
taskpilot-onboarding-v2
Pages/frames
[flow]-[step]-[state]
checkout-payment-error
ComponentsMatch code component names exactly
ButtonPrimary
, not
Main CTA
VersionsSemantic:
v1.0
,
v1.1
,
v2.0
Major = new direction, minor = iteration
LayersDescriptive, no "Group 1" or "Frame 47"
header/nav/menu-trigger
元素约定示例
文件
[project]-[feature]-[variant]
taskpilot-onboarding-v2
页面/画板
[flow]-[step]-[state]
checkout-payment-error
组件与代码中的组件名称完全一致
ButtonPrimary
,而不是
Main CTA
版本语义化版本:
v1.0
、
v1.1
、
v2.0
主版本 = 新方向,次版本 = 迭代
图层使用描述性名称,不要使用“Group 1”或“Frame 47”
header/nav/menu-trigger

Version Control Rules

版本控制规则

  1. Never overwrite — create a new version, archive the old one
  2. Name the change — "v2.1 — added error states" not just "v2.1"
  3. Link to decisions — every major version links to the decision that drove it (Slack thread, meeting note, sprint review)
  4. Single source of truth — one canonical file per feature. No "copy of" files
  5. Archive, don't delete — move outdated designs to archive with a date stamp

  1. 绝不覆盖——创建新版本,并归档旧版本
  2. 为变更命名——使用“v2.1 — 新增错误状态”,而不是只写“v2.1”
  3. 关联决策记录——每个主要版本都应关联推动该版本的决策(Slack 话题串、会议记录、Sprint 评审)
  4. 单一事实来源——每个功能只有一个规范文件,不保留“副本”文件
  5. 归档而非删除——将过期设计移至归档目录并添加日期戳

Design QA

设计 QA

Design QA is the process of verifying that what was built matches what was designed. Do it before every release.
设计 QA 是验证构建结果是否符合设计的过程。每次发布前都应执行。

Design QA Checklist

设计 QA 检查清单

CategoryCheckTool
Visual accuracyColors match tokens. Spacing matches spec. Typography is correctSide-by-side comparison, browser dev tools
StatesAll states render correctly: default, hover, focus, active, disabled, error, loading, emptyManual testing, Storybook
ResponsiveLayout works at all breakpoints. Nothing overflows, truncates wrong, or disappearsResize browser, test on real devices
ContentReal content fits. Long strings handled. Empty states designed. Truncation worksTest with edge-case content
InteractionAnimations match spec. Transitions are smooth. Timing feels rightManual testing, slow-motion recording
AccessibilityFocus order correct. Screen reader announces correctly. Contrast passes. Touch targets 44px+axe, keyboard testing, VoiceOver/NVDA
Cross-browserRenders correctly in Chrome, Firefox, Safari, EdgeBrowserStack or manual
PerformanceImages optimized. No layout shift. Animations don't drop framesLighthouse, Core Web Vitals
类别检查项工具
视觉准确性颜色与令牌一致、间距符合规范、排版正确并排对比、浏览器 DevTools
状态所有状态均正确呈现:默认、悬停、聚焦、激活、禁用、错误、加载、空手动测试、Storybook
响应式布局适用于所有断点,不出现溢出、错误截断或内容消失调整浏览器窗口、在真机上测试
内容真实内容能够适配、长字符串得到处理、空状态已经设计、截断表现正确使用边界情况内容测试
交互动画符合规范、转换流畅、时序感受合适手动测试、慢动作录制
无障碍聚焦顺序正确、屏幕阅读器播报正确、对比度达标、触控目标至少为 44pxaxe、键盘测试、VoiceOver/NVDA
跨浏览器在 Chrome、Firefox、Safari、Edge 中正确呈现BrowserStack 或手动测试
性能图片经过优化、没有布局偏移、动画不会丢帧Lighthouse、Core Web Vitals

Filing Design QA Issues

提交设计 QA 问题

Every issue needs:
**What:** [Element name] on [screen/page]
**Expected:** [What the design spec shows — link to frame]
**Actual:** [What the build shows — screenshot]
**Severity:** [Critical / Major / Minor / Cosmetic]
**Environment:** [Browser, viewport, OS]
Severity scale:
  • Critical — Functionality broken. User can't complete the task
  • Major — Wrong behavior. User can complete the task but with confusion or errors
  • Minor — Visual discrepancy. User isn't affected functionally but quality feels off
  • Cosmetic — Nitpick. Pixel-level differences that only designers notice
每个问题都需要包含:
**问题:** [元素名称],位于 [屏幕/页面]
**预期:** [设计规范所呈现的内容——附画板链接]
**实际:** [构建结果所呈现的内容——附截图]
**严重程度:** [严重 / 主要 / 次要 / 外观]
**环境:** [浏览器、视口、操作系统]
严重程度分级:
  • 严重——功能损坏,用户无法完成任务
  • 主要——行为错误,用户可以完成任务,但会产生困惑或错误
  • 次要——视觉差异,不影响功能,但会降低质量感受
  • 外观——细节问题,只有设计师才会注意到的像素级差异

Acceptance Criteria for Design

设计验收标准

Add these to every user story:
Design acceptance criteria:
- [ ] All states match design spec (link to Figma frame)
- [ ] Responsive behavior verified at 320px, 768px, 1024px, 1440px
- [ ] Keyboard navigation works (Tab, Enter, Escape, Arrow keys)
- [ ] Screen reader announces all interactive elements correctly
- [ ] Design tokens used (no hardcoded colors, spacing, or typography)
- [ ] Loading and error states implemented
- [ ] Edge-case content tested (empty, long strings, special characters)

将以下内容添加到每个用户 Story 中:
设计验收标准:
- [ ] 所有状态均与设计规范一致(附 Figma 画板链接)
- [ ] 已验证 320px、768px、1024px、1440px 下的响应式行为
- [ ] 键盘导航正常工作(Tab、Enter、Escape、方向键)
- [ ] 屏幕阅读器能够正确播报所有交互元素
- [ ] 使用设计令牌(不硬编码颜色、间距或排版)
- [ ] 已实现加载和错误状态
- [ ] 已测试边界情况内容(空内容、长字符串、特殊字符)

Process Metrics

流程指标

Track these to measure design ops health:
MetricWhat It MeasuresTargetHow to Measure
Handoff completeness% of handoffs with all states, tokens, responsive specs>90%Audit handoff docs quarterly
Design QA pass rate% of stories passing design QA on first review>80%Track QA issues per story
Rework rate% of design work that gets redone after handoff<15%Count post-handoff design changes
Sprint velocity impactHow often missing specs block engineering0 blocks/sprintTrack blocker tags in standup
Design debtKnown visual/interaction inconsistencies in productionDecreasing trendMaintain a design debt backlog
Critique participationDesigners bringing work to critique regularly100% monthlyTrack critique presenters

跟踪以下指标,以衡量 Design Ops 的健康状况:
指标衡量内容目标衡量方式
交付完整度包含所有状态、令牌和响应式规范的交付占比>90%每季度审核交付文档
设计 QA 一次通过率首次评审即通过设计 QA 的 Story 占比>80%跟踪每个 Story 的 QA 问题
返工率交付后被重新设计的工作占比<15%统计交付后的设计变更
Sprint 速度影响规范缺失阻塞工程工作的频率每个 Sprint 0 次阻塞在站会中跟踪阻塞标签
设计债务生产环境中已知的视觉或交互不一致问题呈下降趋势维护设计债务待办列表
评鉴参与度定期携作品参加评鉴的设计师比例每月 100%跟踪评鉴展示者

Scaled-Down Operations for Lean Teams

精简团队的轻量化运营

The processes above assume a dedicated design team. But many organizations have a single designer — or someone who does design as part of a broader role. The principles still apply; the execution scales down. This section provides adapted methods for resource-constrained teams, drawing on Leah Buley's UX team-of-one framework.
上述流程假设团队拥有专职设计团队。但许多组织只有一名设计师,或者由某个人在更广泛的职责中兼顾设计。原则依然适用,只是执行方式需要缩减。本节提供适合资源受限团队的调整方法,参考 Leah Buley 的 UX 单人团队框架。

The Core Mindset

核心思维方式

  1. Focus on small wins. You can't transform the organization overnight. Pick one visible improvement, deliver it, and let the result build momentum for the next
  2. Build a user-centered culture, not a UX department. Your goal isn't to own all design work — it's to make everyone on the team think about users
  3. Develop a growth mindset. Seek opportunities to expand skills incrementally. You don't need permission to start practicing research or testing
  1. 关注小胜利。 你无法一夜之间改变整个组织。选择一项可见的改进,交付成果,并让结果为下一步积累势能
  2. 建立以用户为中心的文化,而不是成立 UX 部门。 目标不是独占所有设计工作,而是让团队中的每个人都开始思考用户
  3. 培养成长型思维。 寻找逐步扩展技能的机会。无需等待许可,就可以开始实践研究或测试

Guerrilla Methods

游击式方法

When you don't have budget, time, or formal research infrastructure:
Full ProcessGuerrilla AlternativeWhen It's Enough
Formal usability study (lab, recruiting, 5+ participants)Hallway testing with 3 people for 15 minutesEarly concepts, internal tools, low-stakes features
Multi-week discovery research3 customer interviews in one week + support ticket reviewYou need directional insight, not statistical confidence
Design sprint (5 full days)Mini-sprint: 2-day version (map + sketch on day 1, prototype + test on day 2)Smaller problems, aligned team, good prior research
Full journey mapping workshopAssumption map on a whiteboard (30 min with the team, mark what you know vs. guess)When you need alignment more than research
Formal design critique (weekly, all designers)Async critique in Figma comments with one engineer and one PMSolo designer, no design peers available
Design system with governanceComponent inventory + shared Figma library with naming conventionsSmall product, 1-3 engineers
当你没有预算、时间或正式研究基础设施时:
完整流程游击式替代方案适用场景
正式可用性研究(实验室环境、招募、5+ 名参与者)与 3 人进行 15 分钟的走廊测试早期概念、内部工具、低风险功能
持续数周的探索研究一周内开展 3 次客户访谈 + 审查支持工单需要方向性洞察,而非统计置信度
设计冲刺(完整 5 天)迷你 Sprint:2 天版本(第 1 天梳理 + 草图,第 2 天原型 + 测试)规模较小的问题、已达成共识的团队、已有良好前期研究
完整的旅程地图工作坊在白板上制作假设图(与团队进行 30 分钟,标出已知信息和猜测)需要对齐而非研究时
正式设计评鉴(每周,所有设计师参加)在 Figma 评论中异步评鉴,由一名工程师和一名 PM 参与单人设计师、没有其他设计同行时
带治理机制的设计系统组件清单 + 采用命名约定的共享 Figma 库小型产品、1-3 名工程师

Building Relationships and Advocacy

建立关系与影响力

As a solo or lean-team designer, your effectiveness depends on relationships more than process.
Earn a seat at the table:
  • Start by meeting the team's immediate needs — even grunt work builds goodwill
  • Show, don't tell. A quick prototype that surfaces a problem is worth more than a presentation about UX maturity
  • Connect UX work to metrics leadership already cares about (conversion, support tickets, retention)
Influence without authority:
  • Frame recommendations as experiments, not mandates: "Can we test this with 3 users before committing?"
  • Share research findings in the format your audience consumes — Slack summary for engineers, dashboard for leadership, annotated screenshots for PMs
  • Present findings with confidence but invite collaboration: "Here's what we learned — what does this mean for your area?"
作为单人设计师或精简团队成员,你的效能更多取决于人际关系,而非流程。
赢得一席之地:
  • 先满足团队的即时需求——即使是琐碎工作,也能建立良好关系
  • 用行动展示,而非空谈。一个快速揭示问题的原型,比一场关于 UX 成熟度的演示更有价值
  • 将 UX 工作与管理层已经关注的数据指标关联起来(转化率、支持工单、留存率)
在缺乏职权的情况下施加影响:
  • 将建议表述为实验,而不是指令:“能否先与 3 名用户测试,再决定是否投入?”
  • 按受众习惯的形式分享研究发现——给工程师发 Slack 摘要,给管理层看数据看板,给 PM 看带标注的截图
  • 自信地展示发现,同时邀请协作:“这是我们的研究发现——这对你们的领域意味着什么?”

Adapted Rituals for Solo/Lean Teams

单人/精简团队的调整型固定机制

Full RitualLean AlternativeCadence
Weekly design critiqueBi-weekly "design lunch" — show WIP to anyone interested, even non-designersEvery 2 weeks
Design-eng sync15-minute standup addition: "Here's what's coming in design this sprint"Per sprint
Formal design reviewShare a 1-page decision doc with the PM before a milestone. Async approvalPer milestone
Design QA sprintQA checklist in the PR template — designer reviews before mergePer story
RetroAdd one design-specific question to the team retro: "Where did design and implementation diverge?"Per sprint
完整固定机制精简替代方案节奏
每周设计评鉴每两周举行一次“设计午餐”——向任何感兴趣的人展示进行中的工作,包括非设计人员每 2 周
设计与工程同步会在 15 分钟站会中增加一项:“这是本 Sprint 即将交付的设计”每个 Sprint
正式设计评审在里程碑前向 PM 分享一页决策文档,采用异步审批每个里程碑
设计 QA 冲刺在 PR 模板中加入 QA 检查清单——合并前由设计师审查每个 Story
复盘在团队复盘中增加一个设计相关问题:“设计与实现在哪些地方出现偏差?”每个 Sprint

Scaled-Down Handoff

轻量化交付

When full specs aren't practical:
  1. Annotate in-context. Add behavior notes directly on Figma frames — don't create a separate spec document
  2. Prioritize what's ambiguous. Don't spec obvious things. Focus on states, transitions, and edge cases that engineers would have to guess
  3. Walk through once, document questions. A 15-minute walkthrough call + a list of engineer questions answered in Figma comments is often enough
  4. Build shared vocabulary early. If you and the engineer agree on component names and token usage, you need fewer words in every handoff
当完整规范不切实际时:
  1. 在上下文中标注。 直接在 Figma 画板中添加行为说明,不要创建单独的规范文档
  2. 优先说明模糊之处。 不要规范显而易见的内容。聚焦工程师不得不猜测的状态、转换和边界情况
  3. 只演示一次,并记录问题。 一场 15 分钟的演示通话,加上在 Figma 评论中回答的工程师问题清单,通常已经足够
  4. 尽早建立共享词汇。 如果你与工程师对组件名称和令牌使用达成一致,每次交付所需的话语就会更少

The Power of Small Wins

小胜利的力量

Track and communicate your impact, even informally:
  • "We tested the new flow with 3 users — 2 couldn't find the save button. We moved it, and support tickets for that flow dropped 40%"
  • "The assumption map revealed we had no data on how users think about billing. Two interviews later, we redesigned the billing page before engineering started"
  • "Adding a design QA step to PRs caught 12 visual bugs this quarter that would have shipped"
Small wins compound. Each one makes the next conversation about investing in design easier.

即使只是非正式地跟踪和传达你的影响:
  • “我们与 3 名用户测试了新流程——其中 2 人找不到保存按钮。我们调整了位置,该流程的支持工单下降了 40%”
  • “假设图显示,我们没有关于用户如何理解计费的数据。完成两次访谈后,我们在工程开发开始前重新设计了计费页面”
  • “在 PR 中加入设计 QA 步骤后,本季度拦截了 12 个原本会发布的视觉缺陷”
小胜利会不断累积。每一个小胜利,都会让下一次关于投入设计资源的讨论更加容易。

Common Mistakes

常见错误

MistakeWhy It FailsBetter Approach
Skipping the sprint map dayTeam builds solutions to the wrong problemMonday's map and target selection is the most valuable day
Designing in isolationWork handed off doesn't match engineering realityDaily or weekly design-eng syncs
No design QA processVisual quality degrades over timeQA every story, not just every release
Over-documenting30-page spec nobody readsSpec what's ambiguous. Shared component system handles the rest
Under-documenting"You can see it in Figma"If an engineer has to ask, the spec was incomplete
Treating handoff as a one-time eventThrows work over the wallHandoff is a conversation that continues through implementation
No retrosSame mistakes repeatBi-weekly retros with specific action items and owners
Design critique as approval gateCritique becomes politicalCritique is for improving work, not for approving it
错误失败原因更好的方式
跳过冲刺的梳理日团队针对错误的问题构建解决方案周一的梳理和目标选择是最有价值的一天
闭门独立设计交付内容与工程实际不相符每天或每周举行设计与工程同步会
没有设计 QA 流程视觉质量随着时间不断下降每个 Story 都执行 QA,而不只是每次发布时执行
过度文档化没人会阅读 30 页的规范只规范模糊之处,其余由共享组件系统处理
文档不足“在 Figma 里就能看到”如果工程师还需要提问,就说明规范不完整
将交付视为一次性事件只是把工作扔给工程团队交付是贯穿实现全过程的持续对话
不做复盘同样的错误不断重复每两周复盘,并设置具体的行动事项和负责人
将设计评鉴当作审批关卡评鉴变得充满政治博弈评鉴用于改进工作,而不是审批工作