Evidence receipt / belief
Published · transcript-backedJenny Wen: belief
1 Mar 2026 Lenny's Podcast The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude)
“Seeing that prototype and seeing the kinds of information that people found really helpful, seeing Claude's plan and to-dos, seeing Claude's context and the files that it was going through, those kinds of things are things that I ended up pulling out of that prototype into Claude cowork. So yeah, I think about how can designers almost be more like VCs in this way, internally when we're looking at prototypes.”
Source trail
Everything needed to verify it.
- Speaker
- Jenny Wen
- Attribution
- Verified speaker
- Claim type
- belief
- Recorded
- 1 Mar 2026
- Publisher
- Lenny's Podcast
Transcript context
…Yeah. This framework, I think I saw it on Twitter, maybe last year or something, and it was Evan Tana, who's a partner at SPC. He's a VC. So it basically is this two by two. I don't think it got so much attention, but once I started seeing it, I actually couldn't stop thinking about it. So on the two by two, he basically has founders. Founders can be either illegible or legible, and then ideas can either be illegible or legible. And basically he was saying that, "Okay, if both the founder and idea is super legible, the idea is probably not that novel, and somebody's already like, they're already going to implement it or do it and you're actually not finding something new." But then where it gets really interesting is where the idea itself is illegible. And by illegible, he means, "Oh, it's sort of really on the frontier, people might not get it yet," or the way it's being told, it's not being told in the way that makes the most sense to people. And I think this is obviously a good way for a VC to operate, because you're trying to look for the opportunities that people don't see and put them out there in the world. But I also think that part of the role of the designer, at least, at least at a frontier lab at Anthropic, is spotting the ideas that are illegible, and trying to understand what's there, and how to take that and transform it, whether it's through storytelling, or whether it's through the actual UX and the form factor, and put it out there. And I think when I mentioned going through Slack and looking at all the stuff that people are making, that's kind of what I'm doing. I'm trying to see, oh yeah, what are the ideas that there's some energy there around, but might not make sense yet, that are worth me thinking about more in my work? There's one good example, actually, that ties to cowork where there was this internal prototype that we called Claude Studio that I think somebody built partway through last year, and it essentially was just this really kind of dense, powerful interface that was built on top of some agentic harness. It might've been Claude Code at that point in time too. And it had all these displays where it was showing you all this knowledge and all these skills and things Claude was doing, and previewing its outputs. And I think, to a designer, I looked at it and I was like, "I don't know what's going on. I don't really get it." But then I sort of saw the folks in research, the folks building it and just folks internally, there's just a lot of energy around it. And I was like, "Cool, I think there's something here, but I just don't understand it yet." And I think that really was an example of an illegible idea. And ultimately what came from it was the skills framework and the markdown files that instruct Claude on how to do something. So that came out of that specific prototype. That was not something I was directly involved in, and that was more of, the folks working this prototype extracted that out of it. on how to do something. So that came out of that specific prototype. That was not something I was directly involved in, and that was more of, the folks working this prototype extracted that out of it. But when it did come to work on Claude cowork and I was thinking about, oh yeah, what is the form factor for those things? Seeing that prototype and seeing the kinds of information that people found really helpful, seeing Claude's plan and to-dos, seeing Claude's context and the files that it was going through, those kinds of things are things that I ended up pulling out of that prototype into Claude cowork. So yeah, I think about how can designers almost be more like VCs in this way, internally when we're looking at prototypes. This is super interesting. I did a research project recently with this guy Terrance Rohan, a VC, actually, we looked at what are patterns across people that have joined companies very early that ended up being massive successes, like Palantir and Stripe and Linear and Notion, all these companies. People that have joined many of these companies early, what were they looking for? And one of the factors was the idea is so crazy that everyone's laughing at this. "This is impossible. You're never going to do this. This is the craziest thing. Why would you even think ... " OpenAI actually was one of them, just some research lab doing some stuff. So it's interesting that ... And it's not like every time this will work, and it's not like every crazy idea that makes no sense will be good. But I think what you're saying is pay attention to stuff that's interesting to you and isn't totally clear. Maybe you can be the person that helps pull it together.…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.