Tomer Cohen: belief

Transcript context

…I love this kind of comparison to the shift to mobile. We all went through that and there's all these stories of companies requiring you to show mobile mocks. That's the only way we're going to operate. Now everything you have to ship has to be on mobile, and it's interesting how similar this is to them, to that experience. And so a few things you just shared here just to kind of summarize some of the things that have worked for you. Showing wins, celebrating wins, showing people what other folks are doing with AI tools, creating a program that people enroll into and make it a little bit exclusive. This performance review piece is really interesting because that really will change people's behaviors. Here's how we get promoted. Have you actually already made that change to the PM? I guess it's every track, I imagine, not just product management. Have you already made that change or is it kind of like a work in progress? So there was two aspects to it. Once I moved my team, my directs, we did 360 for them. So their 360 was, if you came from PM, you had the designers on your team rate you. And so that had its own, and then we shared those with them, and that had its own kind of motivation. But then we broadly took it across. So when we hire right now, we look for those. And then this upcoming cycle, we do a bi-annual. That's going to be part of the performance evaluation piece and we announce it to everybody. And for what, it's where people are excited to show. And they're excited to know how they're going to be... It's always about, like, "I want to know how I'm being rated or evaluated." So just being able to show those examples has been a big part of it. The other thing I would say, it takes time for this program and its formality to roll out across the entire organization, and I was intentionally not trying to be quick at rolling this out to everybody because I think that just dilutes the value of it really quickly because it's not about... I could care less about your title. I care about how you work. So calling you a full stack builder is not what I'm looking for. Changing your mindset to a full stack mindset is what I'm looking for. You're thinking you can do the whole thing. You're looking at those tools and looking at how to do it. So one of the things I've said is if you're looking for a formal reorg or declaration to start building differently, you're waiting too long. Look, my biggest thing is here's a permission for me to just not wait and just go. So whether or not you have the right tools or not, go build the tool, use a tool from the outside, bring it in, show those examples. In many ways, prove that you are a full stack builder in mindset before anything else come to mind. And that just naturally will happen, and that's also where we've seen some of our best talent just goes and leans a lot into. I love that. I was going to actually mention that quote. Someone you shared, you work with told me exactly that quote you just shared, so I'm glad you brought it up of just if you're waiting for a reorg, you're not thinking about it the right way. How do you encourage people to actually play with these tools on their own? Are you just like, "Go take a few days to play with AI?" Is it just try it? Or is there anything formal you've seen of just getting people to more try this on their own without joining this program?…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.