让我们来聊聊 agentic 产品设计。 每家公司都有自己的设计流程。对我而言，最有效的方法一直是：与产品团队一起在工作室里花长时间，把问题拆解成碎片，再重新组合。在这些会议里，我们会审视价值、可用性、简洁性、美学、行为、叙事性、通用性，以及情感映射。我从记事起就一直以这种方式打造产品。 在 Lemonade 做产品可不是胆小者能承受的。这种对细节的痴迷非常辛苦，但我相信它能带来更好的结果，并培养更强的产品人才。我最爱我们的设计与产品团队的一点，就是这种流程已经成为他们的第二天性。反馈快速、专业、没有紧张感。 但在我们最近的一次会议中，有些地方不同了。 我们的一位设计师使用 Figma 和 Cursor 做出的原型已经高度先进，几乎可以直接上线部署。这让我们惊鸿一瞥地看到一个未来：一个设计师在现代低代码基础设施之上，就能够为拥有百万级用户的产品，独立推出生产级体验。而随着 LoCo 的推进，我预计这在 Lemonade 只需要几个季度就会成为现实。 但有一个潜在问题值得注意。 这些年来我观察到一个有趣现象：审查的作品保真度越高，团队成员的防御心就越强。当有人拿出非常精致的作品时，他们往往会抗拒反馈——因为他们已经爱上了自己构建的东西，很难接受否定。 真正坦诚的激进式反馈（radical candor）最有效的时间点，永远是在项目早期——在人们还没有情感依恋、也不需要捍卫自己的作品之前。 这次会议也不例外。由于作品太成熟，评论变成了“要么接受、要么否定”的二元状态，而创作者也变得防御起来。好在我们都及时意识到了这种新动态，并开始研究如何回到从前那种对每个圆角、每个白色阴影、每个措辞都痴迷的状态。 在审查由代理式（agentic）代码生成的设计时，我们会尝试让设计师带来多个选项，同时打开 Cursor 项目，这样如果需要，我们可以实时修改。 我们看看会怎样推进。如果大家有兴趣，我会更新我们从中学到的东西。 Let's talk about agentic product design. Every company has its own design process. What has always worked for me is spending long studio hours with our product team, dissecting things into pieces and putting them back together. In those sessions we look at value, usability, simplicity, aesthetics, behavior, storytelling, generics, and emotional mapping. I've been crafting products this way for as long as I can remember. Product work at Lemonade isn't for the faint of heart. This obsession over every detail is hard work, but I believe it yields better results and builds stronger talent. One of the things I love about our design and product team is how this process became a second nature to them. Feedback is fast, professional, and tension free. But in our latest session, something was different. One of our designers used Figma and Cursor to build a mockup that was so advanced, it was almost ready to be shipped. It was an incredible glimpse into a world where a single designer working on top of modern low code infrastructure will be able to launch production grade experiences for products with millions of customers, and with LoCo, I expect this to become a reality at Lemonade in just a few quarters. But there's a problem to watch out for. An interesting phenomenon I've noticed over the years is that the higher the fidelity of the work being reviewed, the more defensive people become. When someone shows up with something polished, they tend to resist feedback. They've already fallen in love with what they built, and it's hard for them to accept rejection. Radical candor feedback works best at an early stage of the project, before people get attached and feel the need to defend their work. This session was no exception. Because the work was so advanced, the review became binary, and its maker became defensive. Happily, we all caught ourselves in time to acknowledge this new dynamic and started figuring out how to go back to obsessing about every corner radius, shade of white, and word. When reviewing agentically coded designs, we'll try having our designers bring in more than one option, as well as the open Cursor project so we can make changes in real time if needed. We'll see how it goes, and if this is of interest, I'll update what we learn.