{ "_description": "本文件由 data/ 生成：请改动来源文件，不要改这里。各字段的证据边界见接入指南。", "schemaVersion": "1.0.0", "kind": "entry", "locale": "zh-CN", "id": "lean-ux", "name": { "zh": "精益 UX", "en": "Lean UX" }, "page": "https://designvocabulary.com/zh/entries/lean-ux/", "self": "https://designvocabulary.com/zh/entries/lean-ux.json", "alternates": { "zh-CN": "https://designvocabulary.com/zh/entries/lean-ux.json", "en": "https://designvocabulary.com/en/entries/lean-ux.json" }, "site": { "catalogSchemaVersion": "0.1.0", "entries": 158, "index": "https://designvocabulary.com/zh/entries/index.json", "query": "https://designvocabulary.com/api/query?lang=zh", "guide": "https://designvocabulary.com/zh/agents/", "llms": "https://designvocabulary.com/llms.txt" }, "provenance": { "sourceBacked": [ "entry.definition" ], "editorial": [ "entry.boundary", "entry.signature", "entry.when", "entry.when_not", "entry.tradeoff", "entry.comparison", "entry.rules", "entry.relations", "entry.implementationNote", "entry.philosophy" ], "scope": "定义参考以上来源；数字界面示例、选择建议、条件关系及配方由本样例编辑，尚未经用户研究验证。", "editorialStatus": "drafted", "specimenData": "fictional", "specimenNote": "示例为原创虚构界面；定义附来源，用法与配方为编辑建议。", "sources": [ { "id": "leanux-gothelf-2011", "url": "https://www.smashingmagazine.com/2011/03/lean-ux-getting-out-of-the-deliverables-business/", "title": "Smashing Magazine · Lean UX: Getting Out Of The Deliverables Business (Jeff Gothelf)", "checkedAt": "2026-10-20", "archive": { "status": "unconfirmed", "confirmed": false, "url": null, "capturedAt": null, "lookupUrl": "https://web.archive.org/web/20261020*/https://www.smashingmagazine.com/2011/03/lean-ux-getting-out-of-the-deliverables-business/" } }, { "id": "leanux-canvas", "url": "https://jeffgothelf.com/blog/how-to-use-the-lean-ux-canvas/", "title": "Jeff Gothelf · How to use the Lean UX Canvas", "checkedAt": "2026-10-20", "archive": { "status": "unconfirmed", "confirmed": false, "url": null, "capturedAt": null, "lookupUrl": "https://web.archive.org/web/20261020*/https://jeffgothelf.com/blog/how-to-use-the-lean-ux-canvas/" } }, { "id": "leanux-leanstartup-principles", "url": "https://theleanstartup.com/principles", "title": "The Lean Startup · Principles", "checkedAt": "2026-10-20", "archive": { "status": "unconfirmed", "confirmed": false, "url": null, "capturedAt": null, "lookupUrl": "https://web.archive.org/web/20261020*/https://theleanstartup.com/principles" } } ], "lists": [], "ordered": false, "listDisclaimer": "席位号是编辑位置，不是评分、排名或人气统计；清单未收满时保持原样，不补足。" }, "entry": { "id": "lean-ux", "type": "philosophy", "name": { "zh": "精益 UX", "en": "Lean UX" }, "aliases": [ "Lean User Experience", "Lean UX Canvas", "精益用户体验", "精益设计" ], "granularity": "experience", "intents": [ "understand-users", "assess-impact", "reduce-complexity" ], "tags": [ "假设", "实验", "最小可行产品", "成果导向", "快速学习" ], "definition": "把设计工作当作一连串需要验证的假设：团队先写下想达成的成果与背后的假设，用最少的工作做一个实验去检验风险最大的那一条，再根据结果决定继续、调整还是放弃；它借用精益创业\"构建—衡量—学习\"的循环，衡量进展的是学到了什么，而不是交付了多少文档。", "boundary": "精益 UX 不等于\"少做设计\"或跳过研究：它减少的是不帮助学习的交付物，而不是对用户的理解。它也不等于敏捷开发本身——它是一种在敏捷节奏中组织设计与产品发现的方式，Gothelf 最早的文章就说明它也可以用在瀑布流程里。它不同于参与式设计：精益 UX 让用户以实验对象与反馈来源的身份参与，方向与取舍仍由产品团队根据证据决定；参与式设计要求受影响的人本身掌握部分决策权。用户在实验中给出了反馈，并不等于他们参与了决定。", "signature": [ "工作以\"我们相信……如果……\"式的假设陈述来组织，而不是以功能清单来组织", "团队先确定这一轮最需要学到的一件事，再找验证它所需的最少工作", "目标写成可观察的用户行为变化，而不是要交付的界面数量" ], "when": [ "方向存在较大不确定性，做错的代价高于多做一次实验", "团队能频繁接触真实用户并在短周期内看到结果", "设计、产品与工程愿意共同承担对成果的判断，而不是逐级交接文档" ], "when_not": [ "错误代价不可逆或涉及安全、合规，不能拿真实用户做粗糙的实验", "把\"最小可行\"当作长期交付低质量产品的理由", "实验指标只看短期点击，忽视了难以量化的长期影响" ], "tradeoff": "把方案写成假设、用小实验尽早验证，能在投入大量开发之前发现方向错误，也让团队讨论证据而不是意见；代价是它依赖能被快速衡量的信号，对难以量化或需要长期观察的影响不敏感，而频繁的小实验本身也会消耗用户的耐心与信任。", "comparison": { "focus": "尽快验证方案背后的假设，以学习而非交付衡量进展", "mechanism": "写下成果与假设，用最少的工作做实验检验风险最大的一条，再据结果迭代", "cost": "偏向可快速衡量的信号，长期与难以量化的影响容易被忽视" }, "sources": [ { "id": "leanux-gothelf-2011", "title": "Smashing Magazine · Lean UX: Getting Out Of The Deliverables Business (Jeff Gothelf)", "url": "https://www.smashingmagazine.com/2011/03/lean-ux-getting-out-of-the-deliverables-business/", "claim": "Jeff Gothelf 在 2011 年 3 月 7 日的这篇文章中介绍精益 UX：它受精益与敏捷开发理论启发，关注体验本身而不是文档；只做核心流程的原型并尽早拿去给用户测试，经过验证的原型即可充当规格说明，繁重的交付物被视为浪费；与整个团队的协作对产品成败至关重要；文章还说明它聚焦设计阶段，因此在瀑布或敏捷流程下都可使用。本词条关于\"减少不帮助学习的交付物\"与\"不等于敏捷本身\"的说法据此转述。", "checkedAt": "2026-10-20", "archive": { "lookupUrl": "https://web.archive.org/web/20261020*/https://www.smashingmagazine.com/2011/03/lean-ux-getting-out-of-the-deliverables-business/", "status": "unconfirmed", "checkedAt": "2026-10-20T08:00:13.662Z", "error": "save-request-failed" } }, { "id": "leanux-canvas", "title": "Jeff Gothelf · How to use the Lean UX Canvas", "url": "https://jeffgothelf.com/blog/how-to-use-the-lean-ux-canvas/", "claim": "Gothelf 在 2021 年 6 月 28 日的这篇文章中介绍他与 Josh Seiden 在《Lean UX》一书中使用的精益 UX 画布：依次写下业务问题、以客户行为变化表示的业务成果、用户、用户收益与可能的方案，再把它们组合成\"我们相信……\"式的假设陈述，找出其中风险最大、最需要先学到的一点，并设计验证它所需的最少工作（如访谈、原型、落地页或 A/B 测试）。本词条的定义与\"假设陈述、最需要学到的一件事、最少工作\"的特征据此转述。", "checkedAt": "2026-10-20", "archive": { "lookupUrl": "https://web.archive.org/web/20261020*/https://jeffgothelf.com/blog/how-to-use-the-lean-ux-canvas/", "status": "unconfirmed", "checkedAt": "2026-10-20T08:00:15.760Z", "error": "save-request-failed" } }, { "id": "leanux-leanstartup-principles", "title": "The Lean Startup · Principles", "url": "https://theleanstartup.com/principles", "claim": "该页列出精益创业的原则：把想法变成产品、观察客户反应、再决定转向还是坚持的\"构建—衡量—学习\"反馈循环应尽量加快；用最小可行产品（MVP）尽早开始学习；进展的单位是经过验证的学习。本词条只据此说明精益 UX 所借用的循环与\"以学习衡量进展\"的观念；把两者联系起来是本词条的编辑判断。", "checkedAt": "2026-10-20", "archive": { "lookupUrl": "https://web.archive.org/web/20261020*/https://theleanstartup.com/principles", "status": "unconfirmed", "checkedAt": "2026-10-20T08:00:16.460Z", "error": "save-request-failed" } } ], "relations": [ { "target": "participatory-design", "kind": "related", "condition": "需要分辨用户在过程中扮演什么角色", "reason": "两者都让用户频繁进入设计过程，但精益 UX 中用户是实验对象与反馈来源，决定仍由团队依据证据做出；参与式设计中受影响的人本身拥有部分决策权。", "basis": "editorial" }, { "target": "human-centered-design", "kind": "composes_with", "condition": "需要决定先验证哪一条关于用户的假设", "reason": "以人为中心的设计提供对需求与情境的理解，精益 UX 把这些理解写成可检验的假设并安排实验顺序。", "basis": "editorial" }, { "target": "double-diamond", "kind": "related", "condition": "选择组织设计工作的方式", "reason": "精益 UX 适合方向已定、需要快速验证的阶段；问题本身尚不清楚时，双钻模型对问题定义的强调更合适。", "basis": "editorial" }, { "target": "value-sensitive-design", "kind": "conflicts_when", "condition": "实验只衡量短期行为指标", "reason": "以点击或转化为成果的实验可能在不知不觉中损害隐私、自主等难以量化的价值；需要事先说明哪些价值不能被实验交换。", "basis": "editorial" } ], "rules": [ { "when": "以真实用户做实验", "instruction": "事先确定实验的停止条件与不可交换的底线（例如隐私、安全与已承诺的功能），不可逆或涉及安全的决定不要用粗糙实验来检验。", "strength": "must", "basis": "editorial" }, { "when": "一个最小可行实验得到正面结果", "instruction": "把实验版本替换为达到正常质量要求的实现，并记录这一轮学到了什么，而不是让实验版本直接成为长期交付。", "strength": "recommend", "basis": "editorial" } ], "philosophy": { "values": [ "进展以学到的东西衡量，而不是以交付的数量衡量", "方案在被证明之前都只是假设" ], "tension": "快速学习的速度与长期、难以量化的影响之间", "questions": [ "这一轮我们最需要学到的是什么？", "验证它所需的最少工作是什么？", "这个实验会让哪些人承担代价？" ] }, "demo": null, "version": "0.1.0", "editorialStatus": "drafted", "requirements": [], "demoCapabilities": [], "implementationNote": "本词条尚无可操作示例；插画为编辑示意，以一个循环表现假设、实验与学习，不复制任何书中的画布原图。应用到团队之前仍须写下具体的假设、实验方法与停止条件。", "image": { "src": "/images/lean-ux.webp", "alt": "一张示意图：三个节点排成一个顺时针的循环——一张代表假设的灰条卡片、一个粗糙的虚构 FIELDNOTES 原型界面、一块显示简单柱状变化的结果面板，箭头依次连接，循环中央放着一盏小灯泡表示学到的东西。" }, "searchTerms": [ "hypotheses", "experiments", "minimum viable product", "outcome-driven", "fast learning" ] } }