Evidence receipt / evaluation
Published · transcript-backedJenny Wen: evaluation
1 Mar 2026 Lenny's Podcast The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude)
“I think Claude Cowork is actually a good example of this, where we labeled it a research preview and we put it out there knowing that, "Hey, this is similar to our models. This is the worst it's ever going to be, but we're going to put it out there because we believe, internally we've tried it a bunch, and there's something really powerful here that some people will benefit from.”
Source trail
Everything needed to verify it.
- Speaker
- Jenny Wen
- Attribution
- Verified speaker
- Claim type
- evaluation
- Recorded
- 1 Mar 2026
- Publisher
- Lenny's Podcast
Transcript context
…Okay. So then as a designer where in this profession, craft and great experience and quality and trust are such a core part of the job, to help instill that in the products, because that in theory leads to really successful products in companies, how do you just think about maintaining craft quality, trust, as your products are just shipping 1,000 times a day, and you're not able to stay on top of them and there's no designer involved? It's not that there's no designer involved. It's more just like it's almost that there's too much for one designer to handle. But I think with this, I think about where the features or products are, where they are in the cycle of adoption versus early preview. So for example, we sometimes will launch things and we will say, "Hey, this is a research preview. It's early. It's going to have a bunch of these flaws," and we caveat that a bunch. I think Claude Cowork is actually a good example of this, where we labeled it a research preview and we put it out there knowing that, "Hey, this is similar to our models. This is the worst it's ever going to be, but we're going to put it out there because we believe, internally we've tried it a bunch, and there's something really powerful here that some people will benefit from. It might not yet be the easiest to work with. It might not be the highest quality. It might have some issues with it, but we're going to put it out there because we believe the benefits outweigh the cons." I think that is okay to do, especially when there is something really valuable with the product already, and it's worth putting it out there. But I think the promise you sort of have to make your users is like, "Hey, we're going to put it out there, but we're going to iterate. We're going to take your feedback and we're going to iterate and we're going to make it better." And you have to commit that. You have to show that to the world, you have to respond to people's feedback, and you have to show that you are continuously shipping and improving it. Because I think the way that you really lose trust around quality and releasing something early, is if you release it early and then nothing ever happens. That is something that degrades a brand. But whenever you put something out early, it's possible to do that and maintain the brand of your company. And I think that's something that we've been doing pretty well. And I think anyone who's listening can take away from it, it's like, yeah, well, we're continuing to do that. And I think that is actually really fun for me as a designer, because you put something out there and you actually learn and you get feedback about it immediately, and you know what to do next. The way I've heard you describe this is building trust through speed.…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.