<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>设计思考</title><description>围绕 AI 产品、C 端体验、复杂业务与设计实践的方法论文章。</description><link>http://localhost:4321/</link><item><title>为什么设计&quot;看起来没问题&quot;，但用户就是不会用</title><link>http://localhost:4321/insights/design-thinking/</link><guid isPermaLink="true">http://localhost:4321/insights/design-thinking/</guid><description>体验走查不是&quot;凭感觉挑毛病&quot;，而是有一套完整的法则体系。过去几年我陆续，按用户体验的五个层级分类，形成了一份可以对照排查的清单。
</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><category>交互设计</category><category>UI</category><category>UX</category></item><item><title>示例｜AI 产品体验：从功能可用到值得信赖</title><link>http://localhost:4321/insights/ai-product-experience/</link><guid isPermaLink="true">http://localhost:4321/insights/ai-product-experience/</guid><description>AI 产品需要同时处理理解、反馈、解释和纠错。本篇为页面内容占位，后续替换为真实项目方法论。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><category>AI 产品体验</category><category>示例内容</category><category>AI 交互</category></item><item><title>示例｜设计复盘：从问题定义到方案落地</title><link>http://localhost:4321/insights/design-retrospective/</link><guid isPermaLink="true">http://localhost:4321/insights/design-retrospective/</guid><description>一次完整设计复盘应该记录哪些判断、取舍和证据？本篇为页面内容占位，后续替换为真实项目复盘。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><category>设计实践与协作</category><category>示例内容</category><category>设计复盘</category></item><item><title>示例｜复杂业务的交互架构：如何让系统变清晰</title><link>http://localhost:4321/insights/interaction-architecture/</link><guid isPermaLink="true">http://localhost:4321/insights/interaction-architecture/</guid><description>从角色、任务和信息关系出发，拆解复杂业务产品的交互架构方法。本篇为页面内容占位，后续替换为真实项目复盘。</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><category>复杂业务与跨端设计</category><category>示例内容</category><category>交互架构</category></item></channel></rss>