得一 / De Yi
De Yi founder operating note - review draftWhen support, product, and quality need one operating loopSource review as of 2026-06-17

当用户在压力下使用医疗器械时，不要先给他一本说明书，而要先给他下一步。

供内部 founder review 使用的简体中文工作稿。英文版为当前 canonical 评审稿。

Product Identification (Product ID，产品身份) 指的是一个产品有证据支撑的身份：它是什么，谁使用它，什么证据支持它，哪些对外表述留在边界内，以及哪些决策需要被记录下来。

EN中文日本語

这个版本是围绕 Product ID 支持闭环场景的简体中文评审稿。

核心场景不是泛泛谈 AI，而是用户在高压情况下遇到问题，如何在几秒钟内拿到对当前产品版本真正有用的帮助。

如果这个支持场景设计得对，每一次求助都可以沉淀成产品记忆，而不是在电话、邮件和会议里消失。

英文 canonical 评审稿仍然是当前主要审核版本。

这一篇在说什么

这篇文章聚焦一个具体场景：用户扫二维码进入对应 Product ID 的支持页面，快速看到图示、短视频、步骤或语音入口，而不是先读一大段说明书。

文章想说明的不是“为什么要 AI”，而是医疗器械企业怎样把支持、产品、质量、法规和后续学习放到同一个闭环里。

核心判断

  • Product ID 是底座；
  • 固定重复的部分尽量用代码、规则、结构化内容解决；
  • 只有在匹配、归纳、检索、总结时才让 AI 参与；
  • 每一次支持都要留下可追溯记录；
  • 系统夜里要能复盘过去一周的重复问题，并在第二天把 review 报告交给相关团队。

当前状态

这是供 founder review 的中文工作稿，目的是帮助你先看结构、力度和方向。

如果英文 canonical 定稿并决定上线，再把中文版本继续收紧成可发布稿。

评审时先看什么

先看这个场景是否够具体，是否真正围绕用户求助、Product ID 和记忆闭环展开。

  1. 1场景是否足够具体。
  2. 2Product ID 作为底座是否讲清楚。
  3. 3AI 作为工具而不是目标是否讲清楚。
  4. 4夜间 review 和记忆闭环是否讲清楚。

Source ledger

These sources are used to organize questions and public context. They do not make the final product-specific decision.

FDA, Device Labeling

Can help establish

The Food and Drug Administration (FDA) explains that medical-device labeling supports safe use, including instructions, warnings, and product-specific communication boundaries.

Cannot decide

Whether one company's support workflow, packaging support pattern, or product-specific communication design is sufficient for every use situation.

FDA, Unique Device Identification System (UDI System)

Can help establish

FDA explains how a device identifier supports product traceability and version-specific product reference.

Cannot decide

How a company should structure its internal Product ID memory, service workflow, or customer-support operating model.

FDA Guidance, Applying Human Factors and Usability Engineering to Medical Devices

Can help establish

FDA describes why device use conditions, user stress, task flow, and use-related risk matter in product design and validation.

Cannot decide

Which support content, support interface, or support escalation workflow is best for a specific company or device.

FDA, Medical Device Reporting (MDR): How to Report Medical Device Problems

Can help establish

FDA explains that device problems, malfunctions, and adverse-event signals must be recognized and handled with care.

Cannot decide

How one company should route every service signal into product, quality, engineering, or customer-success review.

FDA, Corrective and Preventive Action (CAPA)

Can help establish

FDA inspection materials show that companies need traceable problem handling, investigation, and action logic.

Cannot decide

Which internal memory system, automation rule, or AI-assisted operating loop is the right fit for a specific team.

FAQ

为什么中文版本现在比较短？

因为这一轮先锁定英文 canonical 逻辑，中文版本暂时作为评审支架，等方向确认后再扩成正式发布稿。