running-design-reviews

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Running Design Reviews

开展设计评审

Help the user run effective design reviews and critiques using frameworks from 8 product leaders.

帮助用户借助8位产品领导者提出的框架，开展高效的设计评审与批评。

How to Help

如何提供帮助

When the user asks for help with design reviews:

Understand the review context - Ask what stage the design is at and what kind of feedback is needed
Establish the hierarchy - Help them prioritize feedback by value, then usability, then delight
Structure the critique - Guide them on how to frame feedback constructively
Set the quality bar - Help them define what "good enough to ship" means

当用户请求设计评审相关帮助时：

了解评审背景 - 询问设计所处的阶段以及所需的反馈类型
建立优先级层级 - 帮助他们按照价值、易用性、愉悦度的顺序对反馈进行优先级排序
构建批评框架 - 指导他们如何建设性地组织反馈语言
设定质量标准 - 帮助他们定义“足够好可发布”的标准

Core Principles

核心原则

Follow the feedback hierarchy: Value, then Ease of Use, then Delight

遵循反馈层级：价值优先，其次是易用性，最后是愉悦度

Julie Zhuo: "The first thing that's most important to address is, well, is this thing actually valuable, is this solving the problem? Then once we do that, then let's focus on the next layer which I think about as ease of use... And then finally... delight." Disregard feedback about aesthetics until the core value proposition is validated.

Julie Zhuo表示：“首先要解决的最重要的问题是，这个东西是否真的有价值，是否能解决问题？在确定这一点之后，我们再关注下一层，也就是易用性……最后才是……愉悦度。”在核心价值主张得到验证之前，忽略有关美学的反馈。

Assign sponsors for major projects

为重大项目指定负责人

Karri Saarinen: "We are basically the sponsors for the projects. So then we are responsible reviewing the work. And so we might just have a meeting where we go through, okay..." Assign a founder or senior leader as a sponsor for every major project to oversee quality through live demos rather than static slide decks.

Karri Saarinen表示：“我们基本上是项目的负责人。因此我们负责评审工作。我们可能会召开会议，逐一梳理，比如……” 为每个重大项目指定创始人或资深领导者作为负责人，通过交互式演示而非静态幻灯片来监督质量。

Review 100% of shipped screens

评审100%的待发布界面

Dmitry Zlokazov: "Founders of the company, they still review a hundred percent of screens that are being shipped and everything that you will see in the app pass this review." Maintain a high quality bar by having senior leaders review every user-facing screen before shipping.

Dmitry Zlokazov表示：“公司的创始人仍然会评审所有待发布的界面，应用中你能看到的所有内容都要经过这个评审。” 通过让资深领导者在发布前评审所有面向用户的界面，维持高标准的质量。

Structure reviews around specific feedback requests

围绕特定反馈请求组织评审

Geoff Charles: "Any large rock that we have on the roadmap needs to be brought into the product review process... but it needs to be structured in a way where you are asking specifically for what type of feedback you want." Only bring high-risk decisions to formal reviews and require presenters to specify exactly what feedback they need.

Geoff Charles表示：“我们路线图上的任何重大事项都需要纳入产品评审流程……但需要以明确请求特定类型反馈的方式来组织。” 仅将高风险决策纳入正式评审，并要求展示者明确说明他们需要何种反馈。

Start big picture before minutiae

先关注大局，再处理细节

Jessica Hische: "Always think big picture before you think minutiae, because sometimes people think that... They'll throw a bunch of minutiae stuff at me, but it's because they don't know what's really bugging them." Ask "What is the overall thing that's bothering me?" before commenting on specific elements.

Jessica Hische表示：“始终先考虑大局，再处理细节，因为有时候人们会……他们会给我一堆细节问题，但其实是因为他们不知道真正困扰自己的是什么。” 在评论具体元素之前，先问自己“真正困扰我的整体问题是什么？”

Use blurred vision to see cohesiveness

用模糊视角审视一致性

Jessica Hische: "Use 'blurred eyes' to look at a brand's overall cohesiveness rather than focusing on individual pixels." Step back from details to assess whether the overall design holds together.

Jessica Hische表示：“用‘模糊视线’来审视品牌的整体一致性，而非聚焦于单个像素。” 跳出细节，评估整体设计是否协调统一。

Questions to Help Users

用于帮助用户的问题

"What specific type of feedback are you looking for in this review?"
"Is the core value proposition clear? Does this solve the right problem?"
"Before we discuss details - what's the overall feeling when you first look at this?"
"What are the highest-risk elements of this design that need the most scrutiny?"
"What would make this not shippable? Are we close to that line?"
"If a user sees this for three seconds, what will they understand?"

“你在本次评审中具体需要哪种类型的反馈？”
“核心价值主张是否清晰？它是否能解决正确的问题？”
“在讨论细节之前——你第一眼看到这个设计时的整体感受是什么？”
“这个设计中哪些是最高风险的元素，需要最严格的审查？”
“什么会导致这个设计无法发布？我们是否接近这个临界值？”
“如果用户看到这个设计三秒钟，他们会理解什么？”

Common Mistakes to Flag

需要指出的常见错误

Feedback without hierarchy - Mixing aesthetic opinions with core value concerns
Static reviews - Reviewing slide decks instead of interactive demos
Unstructured feedback requests - Not specifying what kind of feedback is needed
Skipping to details - Critiquing pixels before validating the concept
No quality bar - Shipping without senior review or clear standards

无层级的反馈 - 将美学观点与核心价值问题混为一谈
静态评审 - 评审幻灯片而非交互式演示
无结构的反馈请求 - 未明确说明所需的反馈类型
直接跳到细节 - 在验证概念之前就批评像素级细节
无质量标准 - 未经过资深评审或无明确标准就发布

Deep Dive

深入探讨

For all 10 insights from 8 guests, see

references/guest-insights.md

如需了解来自8位嘉宾的全部10条见解，请查看

references/guest-insights.md