21:46 Link copied!
It's interesting the fast moving, let's say. What do you what do you kinda call this this innovation
team, what do you have a label for this, like, let's come up with the new ideas part of the org? Well, I think it's really important to acknowledge that, new ideas come from everywhere and we want that. But I think the design team in particular,
it's really important. And we call it the design team. Like, it's really important that they have a flat non hierarchical structure,
you know, where new ideas can come from anywhere. I mean, think that that is absolutely
critical. So in terms of how you operationalize this, is that the key to the innovation you've seen as this like specific
small design team
who
can work. Like, talk about just how you actually operationalize this sort of way of working. Yeah. I mean, I I think it's an important part of it, but a lot of how we built Snap was modeled actually on mine and Bobby's original relationship. Right? Where, like, Bobby, you know, has a computer science, you know, heavy duty computer science and stats background,
you know, mathematical and computational science.
But he really likes design and likes thinking about,
you know, building things for customers and empathizing with them. I have a design background, right? I was in the product design program back at school, which actually was like part of the mechanical engineering department at the time. I took some computer science classes.
So I sort of kind of under,
knew what I was talking about when it came to computer science. So we both like had mutual respect for each other and our skill sets and our backgrounds, and both enjoyed talking
together about the types of products we wanted to create. And that dialogue created, you know, a lot of innovation. And so a lot of how we've thought about growing the company over time is like strengthening that dialogue between engineers and designers and creating, you know, an environment where,
you know, folks feel comfortable throwing out really crazy ideas. But I think, you know, for the design team in particular, the thing that is probably most important
is the velocity
of design work. So I typically meet with our designers for a couple hours every week, and we just look at work. I mean, new work every week, you know, hundreds of ideas, I would guess, you know, on a on a weekly basis. That, you know, to me, you know, if if I think about
where I learned how to to design and and build things, I have sort of an interesting combination because, you know, I I went to to Stanford for the product design program, which is really focused on empathy, right, in this iterative process of understanding what people want and building prototypes and and iterating, but really centered on on empathy, right, human centered design.
And then at the same time, I had also been to art school. So I had studied at Art Center. I'd studied at Otis here in Los Angeles, both great art schools. And so I was used to this like grinding
expectation
that you're making new work all the time and then just an absolutely brutal critique process on a regular basis. And so, you know, for me, as I thought about, you know, parts of my education that I really liked, it was this combination of really developing empathy with people and what, you know, the types of products that they want in their lives. But at the same time, having this really high velocity,
you know, work ethic where you're not just like thinking,
you know, all the time about,
you know, new products, you're actually making stuff every week, all the time. And then you're talking about it as a team because that critique process is where so much of the learning sort of happens.
Know, I would say that the velocity of work,
you know, is really important because our favorite saying is, you know, if you wanna have a good idea, you have to have lots of ideas. That's really, really important. I just had Keith Raboy on the podcast. I don't know if you know this about his he has many contrarian takes. One is if you're building a consumer product, do not talk to customers.