The Best Product Designer I Ever Worked With | Alex Cornell (Meta AI)

If you get into a field, let's say design, it's presumably because you have good enough taste in that thing that you appreciate it. And the problem when you start working in the field is that you are terrible. And so you look at your own work and you're like, this sucks, you know, because you have good taste and you're not good. So it's like the delta is enormous and it's just constantly frustrating. But the interesting thing about that is if you have the good taste, you have the barometer to know and evaluate yourself as you continue to work towards getting better. And the only way to get better is to just do it in a lot of work. And eventually that gap does start to close. Eventually when it closes, what happens is that you'll do some work and your good taste and the work will be aligned and it will be good. But then, like I said, for me, that only lasts for a little bit of time. And the longer it lasts, the better the work probably was. But if I look at it, I'm like, that's great. I go get coffee and I come back and I'm like, crap, it's terrible. It's like, it probably wasn't that good to begin with. So I think it's not really like a total end state. You don't get to a place where it's like the work is objectively good forever.

My guest today is Alex Cornell. Director of Design at Meta AI. Alex is one of the best product designers that I've ever worked with. He helped design Facebook, Substack, Linear, and an app for family and friends called Cocoon. We talked about lessons from designing leading tech products, how design will change with generative AI, and how anyone can start learning design right now. This interview is a must-watch if you're interested in design at all. If you enjoy our conversation, please like and subscribe to support this podcast.

All right, Alex. Well, welcome. Thanks for chatting with me. Not to make you feel too good, but like, you're like one of the best designers I ever worked with. So, and you've made some like amazing apps over the years, right? And amazing products. So I'd like to start at the high level. You know, do you have any kind of like core design principles that you think about or follow when building a new product?

Yeah, definitely. Well, first, thanks for that. And really happy to be here. I really enjoyed working with you as well many years ago. Yeah, I think when I think about my process and values, I guess the one that I have to always remind myself of is to resist being too clever. I think that's an instinct that a lot of designers sort of have to temper. And the other side of that I think is sort of embracing intuition, so like your own intuition and also how that will sort of manifest for a user and an experience that would feel intuitive to them. And I think, I don't know what it is about designers that we sort of crave the clever and the elegant. That is a really tempting and I think risky instinct sometimes, because if you get too clever, your interface will be beautiful, but hard to intuit. And that is not where you want to be. So I think that's definitely something that I think about at first. Yeah. I think of design, I think elegance is sort of like collecting anything niche like baseball cards or something like that, where it's like there's a small group of people who value this thing extremely, you know, like, and that, that would be designers. You know, if I showed my work on Twitter or something and it was really flashy, there's a whole group of people that would be really stoked on it. And they're all designers. They're not users, you know? And it's sort of like baseball cards where it's like the people who like baseball cards, they care a lot about like a Nolan Ryan rookie card, but like the average person's like, that's a piece of paper. That's worth nothing to me, you know? And I think there's a lot of design that might fall into that category.

Okay. So still thinking about like the user problems and like not making it too complicated to solve the user problem. Yeah.

And I think it's, it's just sort of like a constant reminder that, you know, what you're working on will be seen by somebody else for the first time. And it's very hard to put yourself in that mindset when you're staring at this thing forever and ever.

Got it. So like when you're like designing like a, you know, like a new product or app from scratch, like what kind of process do you follow and like how can PMs be a good partner for you during this process?

Yeah, I mean, I think at the outset, like at the true outset of something, you know, like if we're talking about like absolute zero, I think my favorite process is sort of an alternating between unbounded conversation Pretty open discussion in person for hours and hours, not just like 45-minute meeting, like a 6-hour conversation, maybe coffee break in between, followed by a similarly long period of iteration where you separate. So let's say if it's you and me, and we're starting something new, I would suggest we get together for a day and just talk for a long time. And it's very important that while you're talking, both of you or one of you is taking notes because it's very easy to have an insight and just, it's gone in 20 minutes. So it's pretty, that's not a guided conversation, but it's structured in the sense that you are taking notes and you are attempting to glean insights in that conversation. And then taking that very quickly to a period of design where you can try to manifest whatever it was that came up in that conversation in a way that then you can talk about it the next day. And I think that process of alternating between those two kind of unbounded, just kind of finding your way around in the dark and then like truly putting pen to paper, that back and forth can be really helpful. And Sachin and I, my co-founder at Cocoon, would do that at the beginning. We'd just get together at each other's houses, talk forever. And, you know, we have, I could still go back and find them. It'd probably be pretty interesting, these super long notes of these conversations that we'd be having and the The notes are really, really wild. You know, they're just like, it's like following your own kind of inner monologue and it's just as scattered, but you can bold and pull apart what's useful and then turn that into a design, I think, pretty quickly.

What do you guys talk about for the whole day? Like, like typical stuff, like who the user is, what the problem is, or it's very unstructured?

Yeah. I mean, I think like ideally you have presumably gathered together because you share some Appreciation or interest in a problem space. And so I think for us, just as an example, because it's, I think it's useful to have some concreteness with Cocoon. We had sort of felt like we had lost a place to connect with our family and our close friends. And this was in 2018. So well after, I think we'd all sort of appreciated that the larger social networks were no longer really the place where you were doing that. And a lot of those Relationships had retreated to group messaging, which was not really designed for, at least not designed specifically for those use cases. And I think even just that sentence or 2 sentences is enough to sort of kick off a conversation, you know, because I could say that and you could be like, oh yeah, that's true. You know, like I've got my, my large family chat, which is terrible because like you get notifications and whatever. And you just, from there you have like kind of endless ways you could go. And I think you're really trying to find the shape of the thing and like. the outer boundary of where it is. And I think like, once you've sort of established like, okay, this thing we're talking about is about this big, you know, it's like, now let's fill in all the details and like, see if within this problem space, maybe there's actually some kind of solution that we might be able to build.

Let's talk about Cocoon some more because you spent, I think you and Sachin spent 4 years on it, right? So maybe give our listeners like an overview of what the app does. Yeah.

Yeah, so Cocoon was designed for your close friends and family, and it was essentially a way to stay in touch, share, talk, but designed specifically for those relationships. So, you know, I think that there's a lot that you maybe would feel comfortable sharing with like your, your parents that you wouldn't ever really broadcast to social media. And so we were able to get like a lot more I guess intimate, you could say, in terms of like the types of tools we provided. An example would be like, we did a lot of work around flight tracking, you know, so that this essentially messaging experience could also surface a lot of information about where your flight was if you were on it. And it's like the kind of thing that like the average chat probably doesn't need that, you know, but a lot of my conversations on text with my mom are like, have you taken off yet? Are you, at the airport, and we would just automate all of that. And you can sort of imagine or use that as an example and think of lots of other features you might be able to build. But I think ultimately what we were solving for is something I know you'd be familiar with. Often it's referred to as the audience problem, which is basically that once an audience of your peers gets sufficiently large, it becomes more difficult to share because you need to share Or you need to find something that would sort of meet the criteria for all of those people. The same thing I would share with my sister, I might also, I'd have to now also share with like my best friend and my college buddies and also my coworkers. And it's like, obviously over time, what meets that, all of those criteria starts to shrink. And the way a lot of companies have traditionally tried to solve this is by artificially limiting the total size of the audience. So you'll like, I think Path is maybe the most famous example where you could only have a certain number of friends. Or I think even Retro today might be a good example where, you know, the size of the total audience you're sharing to is smaller, close friends products, these kinds of things like inside of Instagram. And our feeling was that the actual issue was not so much the total audience size, but it was just context collapse. So even if I only have 3 friends, let's say it's you, And my wife and my coworker. If I post a photo and the 3 of you comment, you don't know each other. And I know the 3 of you, but you don't know each other. So the conversation that's going to happen on that photo is going to be really, I think maybe, uh, it's going to have to be really fragmented because I can have a conversation with each of you, but like you don't care about each other. And so our feeling was that the type of sharing that we thought you should be able to do is still broadcast, essentially, like Sharing the same photo to lots of different people, lots of different groups. But any of the interaction, any of the conversation should be direct and private. So if I post a photo of my latte, that would go out to everybody, but then the conversation would be grouped by, I had a family group, I had a friend group, I had like a direct message with a few people. And that's where we ended up. And I think eventually that was, that felt like the right solution. Unfortunately, where we started and where we made the biggest splash was like the product was a little different. It was more of an ambient updating app where like you could monitor kind of what's going on with one single group of people over the course of the day automatically. And what we pretty quickly discovered was over time, that's not interesting as you start to understand people's routines. Also, most people have more than one group, which is obvious in retrospect. And also really what people want to do is they want to talk and they want to share mostly photos.

So like we were sharing like automated location Kind of reminds me of, I'm not sure if you use like WeChat Moments where I can upload a photo and if you comment on it, like if Sachin is not connected to you, he cannot see your comment. You know, it's not like Facebook where everyone can see everyone's comments. Like you have to be connected to the other person to see the other person's comments. Yeah. Yeah.

It's a similar type of insight where it's like, you, you know, you just because there's less total people who can comment, it matters like who's connected to who, you know, and I think like that symmetry was something that we felt was pretty important. And, you know, the hard thing with that is, and this is something that obviously we were aware of at the outset, is you are then now artificially constraining your product's ability to grow because, you know, once you complete your groups, there's really no incentive to go beyond that. There's no— There's no status game. And we valued that quite a lot, but I think it is also the kind of thing that can put a little bit of a headwind on your growth. And we definitely did feel that. And the people who loved Cocoon loved it deeply. But eventually we weren't seeing like this sort of explosive growth that you might see on some sort of like viral mechanic that's designed to grow, but is ultimately frivolous.

Yeah. So maybe it could have been a good lifestyle business or like bootstrap business, but not like a VC funded business, right?

Yeah, we considered, you know, towards the end, we, this was around the time when subscription products were becoming more mainstream and more accepted. We did move the model into a subscription style business with which you could unlock certain things. And there was definitely a path forward, I think, where if we had sort of, we had a lot of free users and we would have probably had to force people to Like everybody to pay, like we probably could have kept it alive forever in some version like that, but it would be kind of a lifestyle business for, and I think probably difficult to keep the lights on actually. But it was, you know, I think towards the end we did see there were lots of different possible paths. And I think that was one of them. We ultimately got acquired by Substack during the pandemic, which was a really interesting and exciting process to go through. I'd never been acquired before.

So that was fun.

Yeah.

Yeah, let's talk about Substack since I, you know, I write on Substack. I talk to Sachin a lot actually.

Oh, great. I mean, he's the best, you know, I think like he's one of the most, if not the most insightful person I've ever met. And I think like, you know, you don't start a company with just anybody. And so I think like, it's, it, to me, it's starting a company, starting a band and starting a relationship are all in the similar category of like how Closely you need to align with the person or people you are starting that journey with, you know?

Yeah, it's definitely like a long-term commitment. So like at Substack, I think you worked on the mobile app, right? Is that what you worked on?

Yeah.

Yeah.

I think, you know, their interest in us, we shared a lot of values, you know, when it came to just the internet that we sort of felt like we wanted to see and exist in, but also our specialty, you know, at that time our team of 4, had really developed like a very particular specialty, which was building mobile apps. And, you know, we had just done that with Cocoon and they didn't have a mobile app. And so that was definitely of high interest for them when they brought us in.

And I think the mobile app, I've been using it, you know, it kind of, it kind of looks similar to Twitter in some way. It has an inbox, but it also has like this feed called Substack Notes. I guess while you were designing it, what was kind of like the jobs to be done and like the problems you're trying to solve?

Yeah.

Yeah. Yeah.

Well, I guess I should say the app when I designed it was pre-Notes, so it was just the inbox and the Notes product came after I left, so I can't speak to that so much. But yeah, when we started, it was really interesting because I had never designed an app like that where I also hadn't designed the product. I guess, you know, you could say, you could say that about when we worked at Facebook. It's like, obviously we didn't design Facebook, but like Live was sort of an experience we were designing together. Substack existed in full as a product in the world. And so we were basically taking it and translating it into a mobile context. And that wasn't something that I had done before. And I think you have to recognize at that point that you are a little bit more of a conduit for not only the founder's vision, but also their core customer, which is the writer. So you're sort of bound to a different set of constraints than normal, which is good because actually I think in that case, Like I said, we had gotten really good at designing and building mobile apps. And I think when you actually have a lot of the thorny problems already mapped for you of like, what actually is this product and how does it work that it already has product market fit? Like, that's pretty interesting compared to like building an app from zero and trying to like find your way around in the dark to find product market fit. It's almost more a mission of like, don't screw this up. And I think like the thing that became very clear very quickly to us was Substack is a 2-sided market. You know, there are the writers and there are the readers, and the app is designed to make the reading experience really good for readers. And, you know, I think you might think at first that there's really no, nothing wrong with that, but, you know, from a writer's perspective, their work is going out into the world, into the hands of their subscribers. And they care quite a lot about the context of which it's read, like where it appears, how it appears, and all of this. And so you take maybe just something as simple as branding. If you have a very branded newsletter and now it's appearing in an app that is kind of more homogenizing the way the reading experience, it's like you can see how that might be a balance that's tricky to strike. And I think that was something that was really interesting to navigate. And again, like you are sort of Feeling like you are having to just really execute according to the wishes of the actual customer, which is the writer, you know? So that was really interesting, I think. And I enjoyed it because I care a lot about typography and I care a lot about layout and I care a lot about graphic design, which are things that like don't always come up in traditional mobile product design. But when you're doing like a reading app, You know, you can actually go pretty deep into the details of like, wait, what actually is the letter spacing, you know, and what is our serif font and that kind of thing, which was really fun. So I enjoyed that quite a lot.

Interesting. Maybe, uh, it's definitely a beautiful app, no doubt about it. But maybe, uh, the idea is that, you know, when I send a newsletter post out, most of my readers get it in their email inbox, right? But like, if they can use the app instead to read my stuff, maybe they can discover other writers or I can be discovered. Yeah. Yeah.

Yeah. I mean, certainly, you know, it became a very large growth lever for writers because of exactly what you describe. You know, you're being exposed to just a lot more writing that way as a reader, you know, and you might not otherwise have ever seen, you know, if it was coming into your email inbox, you would obviously never see another writer's writing there. And I mean, I think like that was always the thing too for me. I was like, You know, the email client is a pretty sad place to end up in the first place, you know, like just from like, in terms of what else is around, you know, you're kind of getting bundled in with all the other emails that you get and like the context there is kind of crazy as well. So, you know, I think the app is a much more serene environment and it is designed specifically to get to give you like the best reading experience possible. So, you know, I think You know, we felt really good about where the writing was ending up there.

Awesome. So then you were at Linear for a brief period and, you know, Linear is like a company that really cares about craftsmanship and design. I'm curious if you learned anything, if you learned anything from that experience.

Yeah. Well, yeah, I mean, Linear is definitely a company that values design more than anywhere I have worked at before. I think it is sort of maybe the best embodiment of the phrase design-led, which you hear all the time. And I think maybe not only because it's literally led by a designer in Kari, but also the product itself and the main thrust behind it really does feel like it's coming from a place of design. And I think what I liked about working there, again, it was a similar experience where they didn't have a mobile app and they wanted one. And I was Brought in to essentially bring, you know, that experience into the mobile context. It was very similar to Substack in that like there is a product with product market fit that now needs to be translated into mobile. Very similar, which I enjoyed a lot. And I think what it felt like there was a true test and every designer wants this is they always, every designer always complains they don't have enough time. They're like, oh, we only had a week or we only had 3 days or like, oh my God, this is like, it's always so fast. They wanted to ship whatever. Linear really was a great experiment for me in like, what happens if you are trusted to hone a thing for as long as you want until you think it's ready? Like truly, like we will release this when it is perfect and ready, you know?

Okay.

And like, that was really fascinating because I don't think I'd ever really been anywhere where there wasn't at least some pressure, you know, Artificial pressure, I should say, to release it. Because obviously there's pressure of any kind. I'm talking about the artificial pressure of like, here's an arbitrary deadline that we just put on the calendar. And the interesting thing about that is, for me as a designer, I sort of measure the objective, or I, yeah, objective good of a thing I'm designing by how long it takes me to not like it anymore, if that makes sense. Like, I will design a thing today. And in 20 minutes I'll look at it and I'll be like, yeah, that's pretty good. Tomorrow I'm probably gonna hate it cuz I'll have thought about it a bit more. I look at it, I'm like, yeah, actually this doesn't make sense.

Right.

The length of time between when I design it and how long it takes me not to like it is usually maps pretty well to how like objectively good it is. And so at Linear, I was sort of allowed to work on it until that period of time became basically Nonexistent. Like it never really got to, like the app that when I left that it was like kind of getting ready to go out the door. Sorry for my email.

No worries.

Was, you know, as far as I could tell, like, great. You know, that was really an exciting experience. And they also, they allowed me to explore and do some pretty wild things as well, which I enjoyed. I think my most well-known experiment there was pouring canola oil on my iPad and filming it. For a marketing campaign, which was— Yeah. Yeah. I think it was actually like, it was really fun. They, they, one day they were like, we're releasing this product called Linear Asks and we want to have just like a simple looping video of the logo. Can you think of anything? And I was like, today, like in a couple hours. And they're like, whatever you can do, you know, make it move. You can think of, imagine what that would normally look like, like a logo kind of scaling in and Maybe moving around or something. And I don't know what made me think of it, but I had my daughter's iPad with like the crazy, like case on it. And I had my camera set up and I just put it, the iPad under the camera, poured canola oil on the iPad with the logo on the iPad. And, and then that was it. And everybody thought it was like 3D because it looks kind of like one of these 3D experiments and everything, but it was literally just like. 20 minutes pouring the oil on the iPad, cleaning it up, and then that was it. And it was amazing how much it resonated with people. I think because we've all forgotten sort of the power of, you know, the analog, just like, you know, take a photo of, even like for mobile designs too. I find that people react much more strongly to my work when I film it than when I just share it static or flat even.

Did you ruin her iPad or it still works?

Trust me, her iPad has seen far worse than canola oil.

Okay.

Yeah.

That is a very, very small mark on an otherwise well-traveled iPad.

So like you worked at so many different companies and you wrote this blog post about why you left Facebook, but now you're back, but you left, you wrote a blog post. And I think the gist of it was like, you know, we were working on Facebook Live together. It was a pretty small team.

You felt pretty empowered.

And then a whole bunch of PMs and teams got involved and it became kind of annoying to deal with. So I'm curious, like, what do you think the ideal environment for a designer is? Like, just to—

Yeah, it's a good question. I think, well, certainly there is no one size fits all. I think as my career is a great example, it's like the person who wrote that blog post is not the same person you're talking to because obviously I've returned to Facebook, you know, so there are things about what I value that have changed. And I think that'll be the case for almost anybody. At that time, I was almost a religious follower of the mythical man-month concept, you know, and felt like, like almost nothing good could happen if more people were being added. You know, that, that was something I believed very strongly at that time.

Hmm.

I do still feel like, you know, the best work is accomplished by small teams and that like adding manpower really does add time. It doesn't add power. It just adds time. I do still believe that, but I think that as a designer, you can learn so much and you can add different types of value in so many different contexts that it is really worth getting to experience all of them. And I think I would suggest when I talk to other designers, I always suggest if they're evaluating, say, between a startup and a a big company. You know, it sort of depends on the stage in their career, but I think there's probably no faster way to learn than at a big company. I think a lot of people will say, you know, at a startup you have to do so much that you can learn so fast. That's sort of true, but I, at least for me personally, found that like my personal capability expanded exponentially when I worked at Facebook the first time. And I felt so much more capable than when I went into the startup world. For this last 5-year burst, because I'd kind of done a 5-year burst before Facebook before where I was just a new designer out of school. I didn't know anything. I didn't know what I was doing. I can't even believe what I was doing back then. And so, yeah, I don't know that there really is an ideal environment. It really does depend what you're looking to get out of the experience. So, and that changes, and I think you should be okay with that change. Like, I think a lot of people, like even when I came back to Meta, were surprised because When I had left, I had very strong feelings about certain things. And I still feel those things. But I also now am, you know, looking for something different in my career. And that's just kind of how it goes.

What about like, let's talk about some specifics, right? So like, at a big company, you kind of have the luxury of, like, there's a process where like, you know, you don't just design whatever you want to ship next, you leap forward 3 years, especially since you're working on generative AI right now. Like, You leap forward 3 years, you design the North Star experience, and then you walk backwards. I've always had a little bit of skepticism about that stuff because like, who the hell knows what the hell's gonna happen in 3 years? Like, no one predicted this GenAI stuff in 3 years. But now that you've kind of been around the block, like, how do you feel about this? Like, do you think designers should just focus on what's shipping or like should focus on longer-term stuff?

Yeah, really interesting. And GenAI is a great example. I mean, I think the expression is, Refer, I don't know who said it, but they're referring to product market fit about how it can feel like chasing a boulder down the hill as opposed to pushing a boulder up a hill. It's like, as soon as you hit product market fit, it's like you're actually now chasing this thing. That feels to me like GenAI compared to like, you know, let's say we were to go build like a, I don't know, a dating product or something. The sculpture of that, like that product object is stationary in the ground, has been sculpted for many years by lots of different people. And if we were to go approach it, it would be static and we can just kind of look at every side of it.

Yeah.

GenAI is the rolling boulder down the hill. It's like it's going so fast that like we, there is no like, let's all take a beat and like see it from every angle. It's like it's moving very quickly and that's obviously very exciting. But in terms of, you know, the value of a North Star and kind of how to balance that with tactical execution, I'd personally like to think of it a bit like a barbell, I guess, where it's important to do a lot of work at either end of that spectrum. And I guess maybe personally enjoy doing the North Star stuff quite a lot, but its ultimate value is, you know, you're not going to ship it, as you said. So if you actually want to kind of keep the engines running, you have to be doing the tactical execution at the same time. And the reason I like to do both is because if you have in your mind a target of where you hope one day it will end up, everything you do tactically at the moment You're aware of how that might one day fit into the broader system that you've, you know, at least dream will maybe one day come to pass. And, you know, I think maybe when we worked on Facebook Video, I had, I was always doing a lot of work on this sort of dream ultimate super player that sort of was able to play any kind of video.

Mm-hmm.

And it was a concept always, because we had lots of different video players, but anytime I did anything on the live player or any other, um, video player I was working on, I was always sort of aware of where I wanted to end up one day. And so even just simple decisions about like where certain buttons will go or the spatial model associated with showing more information, you know, knowing that I wanted to end up, let's just say in like a modal presentation, I wouldn't then go and say, hey, you know where I think description should go? Like it should go behind the video. It's like, no, I would never do that. Cause like, that's not where. I think it should ultimately end up. And I think you're only really able to do that kind of balance if you have one foot really in each camp. And then, as you said, like, time will change everything. So like what happens in between is sort of an unknown. It's almost not even worth like predicting sometimes.

But I guess your point is that like the North Star is worth it if it actually affects the decisions you're making for what you want to ship next, right? So that's how I think of it. Yeah, it does.

Yeah. And I think maybe it depends on how far— it depends how long your barbell is. You know, if it's like, I'm here and then 10 years from now, here's the North Star, that's probably not very helpful. You know, I think in my mind, my little barbell that I always sort of work around is like the length of time between the two ends is probably like 8 months. You know, it's like still tangibly within sight, you know, like you might actually be able to do it would be, you know, I don't often do the kind of work where it's like, what if everything was different and there is no interface and you can do it this way, you know, you can talk to it and it's like an AR video. Like I never do that kind of work because it's just so arbitrary and unbounded that I don't really have anything to grab onto, you know, like getting from here to there, the barbell is like. Like I said, years long. So it's kind of pointless. I've never really enjoyed doing that kind of North Star.

Got it. Yeah, dude, a North Star that's like 8 months to a year out is actually perfectly shippable, right? Like you should have a, yeah, like especially at Meta or these big companies, you should have a year-long roadmap, I think.

Yeah, I think, you know, and obviously you can change things as you go, but, and I think also a lot of times for me, the North Star, when people hear North Star, usually they think like, And maybe we've all seen these videos on YouTube that like Microsoft will put out where it's like, what if your car was your best friend? And it's like doing, I don't know, like some weird, some crazy North Star video. To me, a North Star is more just like, it's like 1 to 3 clicks beyond cycle-wise, like beyond where we're going to go next. And it's like, like it's a, it's more of a, like a practical goal. It's like, hey, at some point, wouldn't it be great if we could end up here? It's like, I know, like we got to do this and this first, and we don't know what's going to happen with this. But like, if all that stuff goes well, we could be here. And it's like, we can feel, we can all agree that we probably could get there. And it's like, yeah, maybe you could just stop everything and do it right now. And it's, I have had experiences where a North Star is actually like more of a pivot, you know, like at a startup where it's like, hey, actually let's just do this. Oh, let's just do this instead kind of thing. But at a big company, it's worth keeping it within The site and within reason, I think.

Got it. I also think it's useful to just like maybe even show the North Star to customers to see if it gets them excited. Yeah, like definitely, you know, like a lot of times at big companies we just like try to convince the execs, but like, why not just show it to the actual customers? Yeah.

Yeah, for sure. Yeah. Yeah. We did that at Cocoon. We had a 2.0 kind of launch that we, I remember roadshowed a little bit with customers and Yeah, I mean, that's always super valuable and it's so humbling too, because it's very easy to sort of get blinders on and feel like what you have is obviously what has to happen. And it's not always quite so obvious for everybody, you know.

Dude, so let's talk about AI a little bit. Why don't I start with this? What, how do you use AI in your personal life, whether as a designer or just like as a dad?

As a dad.

Yeah.

Well, I've over the last few years kind of used a blend of all of the, certainly on the like LLM front, I used sort of a blend. I remember before ChatGPT became ChatGPT and it was just GPT, I think I wasn't working, I was in between companies and I remember some friends were like, let's build an email AI where you could respond to your emails, you know? And at that, it's hard to go back to this place where like we, nobody really understood the capability of AI. Like we didn't understand what it could do. And so even that was, wait, what? It could respond for you? Like, how would that work? You know, and this was pre-ChatGPT. And I remember the first demo, somebody had gotten an email. It was maybe like an automated email about like asking them if they wanted to donate to some campaign. And the AI responded, that sounds great. I've wired you $500,000. You know, like it had like fabricated this response of sending the money. And we were all like, oh my God, this is the craziest thing we've ever seen. And then of And then of course, you know, like, I don't know, 2 months later, ChatGPT came out. And I thought that was such a fascinating thing because we had been playing around with the technology in this really weird way. Like the way you used to have to interface with it was like, you know, I forget even what it looked like, but it felt almost like you were coding.

Yeah.

And then all of a sudden, you know, it was released in chat format, which to me is, that is just a very, the technology was basically the same. It was just a small tweak of presentation and interface. And then it became the fastest growing product of all time. And it's like, it's like pretty crazy. And I think like an amazing, maybe I'm simplifying it, but like kind of an amazing example of how framing can really alter someone's perception because the technology was available. It wasn't as if you couldn't use the technology that powered the first version of it. So I think that was pretty cool, I thought. Yeah, that's my favorite. But anyway, so I was just gonna say, I've been using, you know, all, all of the various tools since as long as I've had access. I think the one that I had the most experience with and probably the most fun with, especially early on, was Midjourney. Reminded me a lot of, uh, when my daughter was born and I had a lot of time, like on the couch, I got really into drawing. I haven't, hadn't done art for a long time, but I got really into using Procreate and doing like isometric drawings and Just drawing was like a therapeutic thing, you know, and using Midjourney, and, and in the same way that sort of replaced what prior was like browsing Twitter or something. Like if I was sitting on the couch, maybe I'd be like scrolling a feed or something.

Yeah.

I started drawing instead. Midjourney also sort of replaced that sort of kind of browsing with more of like a, it was sort of like a hybrid of creating and browsing. Like I think like Oh, I wonder what it would look like if like an espresso machine was designed by Dieter Rams and, you know, was as tall as a small apartment building, you know? And it's like, so there was like a creative aspect and then the browsing was just sort of looking at that output and being like, oh, that's kind of cool. Like it was a really interesting, like I've never really had an experience like that where creation and browsing were combined in, into like one experience. It's like kind of a weird thing because when you're drawing, it's like, You don't really think of your output as being something that you're like browsing. It's like, cause you're drawing it. It's like all at one time, but like, since there's a little bit of a handoff between like the creative aspect of prompting a generative AI and seeing its output, that I think that little handoff period is enough to be like, you know, you're trying this thing out, which is kind of fun.

Yeah. I think that like, it's a lot easier to create something that's a remix of something else that you see than to just make it from scratch. So yeah, like you can see images, like for me, like, you know, I see people post memes on Twitter and I just like repost it with like another description. Maybe that's the same thing for Midjourney. Yeah.

Yeah. Commentary.

Yeah. Let's talk about this whole chatbot thing, man. Like, you know, we talk about ChatGPT, like how do you think the interface, do you think the interface will go from buttons and menus to chatbots or do you think there's something else out there with AI?

Well, I think with AI, one thing I've learned is that predicting what will happen too far into the future is usually a fool's errand, which is one of the reasons why I enjoy working in the space is how quickly it evolves. It can feel sort of, it's really hard to grasp the power and what the possibilities are. So I think like, I don't speculate too often, but I do think that it's, as with many things, like when we bring The old assumptions of the way tools work and to new capability. Usually that's like the first step. Usually, you know, it's like, here we have like, like even using Midjourney is like kind of hilarious if you think about what you're actually doing, you know, like literally talking to it through Discord using these really abstract commands. And then the buttons you get in return are like really random. It's like, here's an image. Would you like to see it twice as big or would you like to see it Half as small? Or would you like to see to the right of the image or to the left of it? It's like, what? Why are those my options? You know? And it really feels like a literal mapping of like, what does this, what are we able to do? Oh, well, we can make it twice as big. Great. Button. We could also see, we could like, you know, we could expand the sides. Great. 4-bar buttons, you know? And it's like, it's a literal mapping of like, what are we able to do to What is the interface? And I think like, as, and I think even, you know, they're, I think releasing now a web interface, which will obviously evolve some of that stuff. But I think like over time, as we move away from the sort of just like literal map of what can it do to what buttons we expose, I think that will obviously become a lot more intuitive to use my favorite word. You know, I think it'll get Maybe a lot more, I would suspect it would become a lot more freeform and less like literal, you know, like I think a lot of those interfaces now are like super, super like limited and literal.

So I mean, like maybe something where like you just have a canvas and you like draw some boxes and it fills stuff in or resize it and then, you know, it expands it, right? Yeah. I don't know.

Yeah, exactly. You know, it's like, it's really, it's, it, I guess I don't know.

Yeah, he's got to follow all the AI newsletters.

Yeah, yeah, exactly.

Okay. All right, man. Well, I guess last topic. So, you know, there's been like a lot of like layoffs in tech and like I talked to Scott, who is like the CPO of Adobe. He talks about how the talent stack is collapsing. In fact, I asked him like, how do you find a product leader who's really good at design? And he says, just hire a designer. So I guess the question, you know, as someone who has like really good design taste and has been through this, how does someone who's not a designer Start learning design or start acquiring taste, so to speak?

Yeah, definitely. I mean, I think I started my, I guess, creative career in music, and a lot of designers have, I suppose. But I think there's a lot of good parallels between how you become good at music and how you become good at design. And you can break that into 3 categories, probably. You obviously have to listen to a lot, which in the case of design is just Constant exposure to— let's, we'll use product design as an example, recognizing that design is much broader than product design, you know, obviously, but product design, just since we've been talking about it, you know, if you want to become a good designer, you need to be exposed and aware of what is out there, you know, and that's everything from reading the HIG, you know, the interface guidelines and the Android material guidelines, reading that from COVID to cover, but also just using As much as you can, because, you know, the way Apple does a traditional modal presentation is one way, but then like a couple guys in a garage are going to think of some crazy weird way to do it. Like I saw that it's not that often you see a new interface paradigm, but I was just using the Amy calendar and they have this like pretty wild thing where the interface is like split in 2. And it's like, there's an implication that you've actually got like almost 2 planes of the app that can kind of move in parallel. And it's like, I'd never really seen that before. And it's like, that's awesome. And if you're not exposing yourself constantly to that kind of ideas, it'd be very hard to conceive of that kind of thing completely on your own all the time. The same is true. And then so from there, I think if you're listening to a lot of music, so to speak, the next step usually to learn is to copy it, you know, and I think through copying and in music, it's very, It's less copying. It's like you just learn to play other people's music. It's like, that's how most people get better. In design, it's hard to tell designers to be like, go build like that interface I just described, go prototype that. And in doing that, since you're not a good designer, presumably there will be these mutations that occur that are sometimes delightful, but also that becomes what your style is, sort of the amalgamated, mutated combination Of what you've tried to do with your own mistakes. And that just eventually becomes your style. Like you mix a bunch of things together. Like if you, like for me, when I was learning guitar, it's like, I love Jimi Hendrix, but I also love John Mayer. And, you know, he loved Jimi Hendrix, but his version of Jimi Hendrix is obviously different than Jimi Hendrix. And then my version of their version of it's like, it becomes this like, you know, crazy mixture. And I think that that's an important step. And then I think lastly, you know, if you're just trying to get good at design, there's an absolute requirement to just do as much work as possible, which in the music example would be practice. But there's so much value to working constantly, not only physical, like I'm, for example, very fast. Like when I work on anything, I do it very quickly because I've gotten so used to the keyboard commands and my mouse is fast and just I'm able to very quickly do what I need to do. And that only comes through practice. It's an essential step. And then I think we either talked about it or you wrote it down before. I can't remember, but the Ira Glass interview, which I've referenced and quoted before, it's like every once in a while there's a person that says a thing that's like, could not be more true. And it's like, it's almost like distills everything that's important down so precisely that it's like, really, you could just listen to how he talks about getting good. In his case, at doing radio interviews, but like you could just treat it as getting good at a thing. It's like, it's so perfect that it's like you almost should just listen to that and do what he says. And I'll do a terrible job of reiterating what he says, but his basic point is like, if you get into a field, let's say design, it's presumably because you have good enough taste in that thing that you appreciate it. And we just have to assume for the sake of this argument that you have Relatively good taste. And the problem, as he says, when you start working in the field is that you are terrible. And so you look at your own work and you're like, this sucks, you know, because you have good taste and you're not good. So it's like, like the delta is enormous and it's just constantly frustrating. And which, but the interesting thing about that is if you have the good taste, you have the barometer to know and evaluate yourself as you continue to work towards getting better. And the only way to get better is to do, as he would say, is to just do it in a lot of work, you know? And eventually that gap does start to close. And as I mentioned, for me, like we're eventually when it closes, what happens is that you'll do some work and you'll look at it and your good taste and the work will be aligned and it will be good. But then, like I said, for me, that only lasts for a little bit of time. And the longer it lasts, the better the work probably was. But like, if I look at it, I'm like, oh, that's great. I go get coffee and I come back and I'm like, crap, It's terrible. It's like, it probably wasn't that good to begin with, you know? So I think it's not really like a total end state. You don't get to a place where it's like, yeah, you know, the work is objectively good forever. But yeah, anyway, I think like those 3 categories, you know, exposure to lots of work, replicating as much as you can, and then practice.

Yeah.

That would be how I would tell a designer to get better.

Got it. So the first 2 are kind of like acquiring good taste, right? And the 3rd one is kind of like level up your skills so you can make the good taste stuff yourself.

Yeah. And good taste is an interesting concept just generally. I think the way I've always interpreted it is basically how close does your subjective understanding of an artistic field map to the general public? You know, so somebody like Rick Rubin, you know, who who has, you know, one of the best reputations of all time of music producers. Perhaps it's just that his personal taste maps directly to the zeitgeist taste, you know, like maybe that's, I don't know, like maybe that's like he's fortunate in that way because there are people whose taste is so far outside of what might be considered like global or broad. That they just end up having a very niche career. So I don't— taste is a really funky concept, and I think it's not like a solid object that has some true objective meaning. Yeah.

Yeah.

I do think you have to be honest to yourself, right?

Like, you got to be honest what you think good taste is. And yeah, you're right. It might not be the mainstream, what the mainstream thinks good taste is. Yeah.

You have to really like have a good— that's why I think it's important to constantly sort of be ingesting lots of work because, you know, if you are, I think what ultimately becomes other people's perception of your good taste is that you have a really, you're really in tune with kind of what's out there, what's happening, what's fresh and what's interesting. If you're totally out of touch and you're not really ingesting a lot of work, maybe it's just that you're just exceptionally creative on your own, but probably you'll, you will just be a little bit behind what Is, you know, the actual kind of current thing. So, you know, I think that's why that's such an important part of the process because I don't know of another way to do that.

All right, man.

So, yeah, thanks so much for this chat. Where can people find you online?

Should I direct them to your rising music career or what? You know, I still maintain, I uploaded music to Spotify maybe 15 years ago and it still gets You know, I think it's over, might be, it's either 30 or 50 million. I can't remember, but it's like, it's just been a constantly surprising, wonderful outlet that I have only ever, I plugged into it, like I said, a decade ago. And it's just constantly sending me love back in a way that like feels so unearned at this point because it was so long ago. But no, yeah, so you can find me on Spotify if you wish. But I think probably Since the general landscape of networks is ever shifting, I usually just like to send people to my website because I think if I say find me on some network, who knows if it's there tomorrow, you know? So yeah, just alexcornell.com is a safe bet usually.