{
  "_description": "本文件由 data/ 生成：请改动来源文件，不要改这里。各字段的证据边界见接入指南。",
  "schemaVersion": "1.0.0",
  "kind": "entry",
  "locale": "zh-CN",
  "id": "double-diamond",
  "name": {
    "zh": "双钻模型",
    "en": "Double Diamond"
  },
  "page": "https://designvocabulary.com/zh/entries/double-diamond/",
  "self": "https://designvocabulary.com/zh/entries/double-diamond.json",
  "alternates": {
    "zh-CN": "https://designvocabulary.com/zh/entries/double-diamond.json",
    "en": "https://designvocabulary.com/en/entries/double-diamond.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": "doublediamond-designcouncil",
        "url": "https://www.designcouncil.org.uk/our-resources/the-double-diamond/",
        "title": "Design Council · The Double Diamond",
        "checkedAt": "2026-10-20",
        "archive": {
          "status": "unconfirmed",
          "confirmed": false,
          "url": null,
          "capturedAt": null,
          "lookupUrl": "https://web.archive.org/web/20261020*/https://www.designcouncil.org.uk/our-resources/the-double-diamond/"
        }
      },
      {
        "id": "doublediamond-history",
        "url": "https://www.designcouncil.org.uk/our-resources/the-double-diamond/history-of-the-double-diamond/",
        "title": "Design Council · History of the Double Diamond",
        "checkedAt": "2026-10-20",
        "archive": {
          "status": "unconfirmed",
          "confirmed": false,
          "url": null,
          "capturedAt": null,
          "lookupUrl": "https://web.archive.org/web/20261020*/https://www.designcouncil.org.uk/our-resources/the-double-diamond/history-of-the-double-diamond/"
        }
      },
      {
        "id": "doublediamond-15-years",
        "url": "https://www.designcouncil.org.uk/our-work/projects-programmes/archive/article/double-diamond-15-years/",
        "title": "Design Council · The Double Diamond: 15 years on",
        "checkedAt": "2026-10-20",
        "archive": {
          "status": "unconfirmed",
          "confirmed": false,
          "url": null,
          "capturedAt": null,
          "lookupUrl": "https://web.archive.org/web/20261020*/https://www.designcouncil.org.uk/our-work/projects-programmes/archive/article/double-diamond-15-years/"
        }
      }
    ],
    "lists": [],
    "ordered": false,
    "listDisclaimer": "席位号是编辑位置，不是评分、排名或人气统计；清单未收满时保持原样，不补足。"
  },
  "entry": {
    "id": "double-diamond",
    "type": "philosophy",
    "name": {
      "zh": "双钻模型",
      "en": "Double Diamond"
    },
    "aliases": [
      "Double Diamond Model",
      "Framework for Innovation",
      "双钻石模型",
      "双菱形模型"
    ],
    "granularity": "experience",
    "intents": [
      "understand-users",
      "include-users",
      "reduce-complexity"
    ],
    "tags": [
      "设计流程",
      "发散",
      "收敛",
      "问题定义",
      "迭代"
    ],
    "definition": "英国设计委员会（Design Council）用两个菱形描述设计过程：第一个菱形先发散地探索问题、再收敛到对问题的重新定义（发现、定义），第二个菱形先发散地提出多种方案、再收敛到经过小规模测试的方案（发展、交付）。它的要点是先确认解决的是对的问题，再去把问题解决好。",
    "boundary": "双钻模型是对设计过程的一种描述，不是一份按顺序执行的操作手册：设计委员会自己说明它不依赖特定的方法与工具，后来的创新框架（Framework for Innovation）也把\"发现之后退回起点\"与\"很早就测试粗糙想法\"画了进去。它不等于以人为中心的设计：后者是把人的需求与情境置于中心的原则与心态，双钻模型是组织工作阶段的一张图，两者常一起使用，但走完四个阶段并不保证真正理解了人。它也不是\"设计思维\"的五阶段模型，两者阶段划分不同，本词条不把它们当作同一套流程。",
    "signature": [
      "项目计划里明确区分\"弄清问题\"与\"解决问题\"两个阶段",
      "每个阶段先有一段刻意放宽范围的探索，再有一次明确的收敛决定",
      "定义阶段的产出是一份重新表述的问题，而不是一个方案"
    ],
    "when": [
      "团队对\"到底要解决什么问题\"还没有共识",
      "需要向非设计背景的合作者说明设计工作分哪几步、每步产出什么",
      "项目有足够时间先做探索，而不是一开始就锁定方案"
    ],
    "when_not": [
      "把四个阶段当成只走一遍的瀑布流程，发现新问题也不回头",
      "用画好的双钻图代替真正的用户研究与测试",
      "问题已经清楚、只需小改动，硬套完整的四阶段只增加开销"
    ],
    "tradeoff": "两个菱形把\"先发散再收敛\"和\"先定义问题再求解\"变成一张人人看得懂的图，便于跨职能团队对齐阶段与产出；代价是这张图过于整齐，容易被读成线性流程——真实项目常常需要在阶段之间来回，图本身也不告诉你每个阶段具体该怎么做。",
    "comparison": {
      "focus": "先确认要解决的问题，再解决它",
      "mechanism": "用两轮发散与收敛组织发现、定义、发展、交付四个阶段",
      "cost": "图形整齐，容易被误读为只走一遍的线性流程"
    },
    "sources": [
      {
        "id": "doublediamond-designcouncil",
        "title": "Design Council · The Double Diamond",
        "url": "https://www.designcouncil.org.uk/our-resources/the-double-diamond/",
        "claim": "设计委员会的这一页把双钻模型称为被普遍接受的设计过程描述，列出四个阶段：发现（与受影响的人相处以理解真实问题，而非假设）、定义（用发现阶段的洞察重新框定挑战）、发展（借鉴他处并与不同的人共同设计以产生多种方案）、交付（小规模测试方案、放弃不可行的、改进可行的）；页面说明它不依赖所用的方法与工具，并说明创新框架是其扩展版本，纳入了发现后退回起点与很早测试想法的情况。本词条的定义、四阶段与\"不是操作手册\"的边界据此转述。",
        "checkedAt": "2026-10-20",
        "archive": {
          "lookupUrl": "https://web.archive.org/web/20261020*/https://www.designcouncil.org.uk/our-resources/the-double-diamond/",
          "status": "unconfirmed",
          "checkedAt": "2026-10-20T08:00:10.160Z",
          "error": "save-request-failed"
        }
      },
      {
        "id": "doublediamond-history",
        "title": "Design Council · History of the Double Diamond",
        "url": "https://www.designcouncil.org.uk/our-resources/the-double-diamond/history-of-the-double-diamond/",
        "claim": "该页记载：2003 年，时任设计委员会设计与创新总监的 Richard Eisermann 向团队提出\"如何描述设计过程\"的问题，由此开始这一模型的工作；风筝形的过程图早在 1960 年代就有人引用；设计委员会从 2004 年起在会议、演示与客户工作中公开使用双钻模型，2007 年的报告《11 Lessons on Managing Design》以它为结构。本词条据此说明模型的来源与时间，不采用页面未给出的其他年份。",
        "checkedAt": "2026-10-20",
        "archive": {
          "lookupUrl": "https://web.archive.org/web/20261020*/https://www.designcouncil.org.uk/our-resources/the-double-diamond/history-of-the-double-diamond/",
          "status": "unconfirmed",
          "checkedAt": "2026-10-20T08:00:10.859Z",
          "error": "save-request-failed"
        }
      },
      {
        "id": "doublediamond-15-years",
        "title": "Design Council · The Double Diamond: 15 years on",
        "url": "https://www.designcouncil.org.uk/our-work/projects-programmes/archive/article/double-diamond-15-years/",
        "claim": "设计委员会首席设计官 Cat Drew 于 2019 年 9 月 3 日发表的这篇文章回顾双钻模型诞生十五年，说明它于 2002 至 2004 年间在设计委员会形成，并随文发布新的创新框架（Framework for Innovation）供下载。本词条关于\"2019 年以创新框架扩展双钻\"的说法据此转述。",
        "checkedAt": "2026-10-20",
        "archive": {
          "lookupUrl": "https://web.archive.org/web/20261020*/https://www.designcouncil.org.uk/our-work/projects-programmes/archive/article/double-diamond-15-years/",
          "status": "unconfirmed",
          "checkedAt": "2026-10-20T08:00:12.960Z",
          "error": "save-request-failed"
        }
      }
    ],
    "relations": [
      {
        "target": "human-centered-design",
        "kind": "composes_with",
        "condition": "用阶段图组织以人为中心的项目",
        "reason": "以人为中心的设计提供原则与心态，双钻模型提供阶段与产出的划分；只有阶段图而没有与真实使用者的反复接触，四个阶段只是形式。",
        "basis": "editorial"
      },
      {
        "target": "participatory-design",
        "kind": "composes_with",
        "condition": "在发展阶段需要与受影响的人共同提出方案",
        "reason": "设计委员会把共同设计列为发展阶段的做法之一；参与式设计进一步要求这些人对取舍拥有实际决定权。",
        "basis": "editorial"
      },
      {
        "target": "systems-thinking",
        "kind": "composes_with",
        "condition": "问题定义牵涉多方与反馈回路",
        "reason": "发现阶段的发散探索若只看单个用户，容易漏掉问题背后的结构；系统思考帮助在定义阶段把问题框得更准。",
        "basis": "editorial"
      },
      {
        "target": "lean-ux",
        "kind": "related",
        "condition": "选择组织设计工作的方式",
        "reason": "双钻模型强调在动手解决之前先充分定义问题，精益 UX 强调尽早把假设做成小实验；两者都要求迭代，但前者更适合问题尚不清楚的阶段，后者更适合方向已定、需要快速验证的阶段。",
        "basis": "editorial"
      }
    ],
    "rules": [
      {
        "when": "用双钻模型规划项目",
        "instruction": "在计划中预留从后续阶段退回发现或定义阶段的时间，并写明什么样的发现会触发退回。",
        "strength": "recommend",
        "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/double-diamond.webp",
      "alt": "一张示意图：两个相连的菱形横向排列，第一个菱形内散布着便利贴与访谈卡片，汇聚到中间一张代表问题陈述的卡片；第二个菱形内展开几张不同的虚构界面草图，最后收敛到右侧一个经过测试的 FIELDNOTES 界面，一条细虚线从右侧弯回起点。"
    },
    "searchTerms": [
      "design process",
      "divergence",
      "convergence",
      "problem definition",
      "iteration"
    ]
  }
}
