Evidence receipt / evaluation
Published · transcript-backedMihika Kapoor: evaluation
21 Apr 2024 Lenny's Podcast Vision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product at Figma)
“" Right? And to the extent that you can get as many people in the company feeling like they shaped X, Y, Z parts of the product, I think that's really powerful, because, then, you kind of are ensuring that there's this constant feedback loop, and there's this constant investment in thinking about how can we collectively drive towards success, because at the end of the day, product development is a team sport, right?”
Source trail
Everything needed to verify it.
- Speaker
- Mihika Kapoor
- Attribution
- Verified speaker
- Claim type
- evaluation
- Recorded
- 21 Apr 2024
- Publisher
- Lenny's Podcast
Transcript context
…And this kind of leads into the next bullet point you shared of spreading the idea across the company. It feels like this is part of it just getting it spread in a big powerful way initially. But what else have you learned about just getting this to spread across the company? It gets kind of like this flame spreading throughout the organization. I think something that's very unique about Figma as compared to other companies is we have a multi-month plus long staging or dogfooding process. And so something that was really interesting to me was... One of the first projects that I worked on at the company was we were building sections inside of FigJam. And we had a problem. We built it. We put something on staging, and I was kind of like, "Okay, cool, it's been on staging a week, now we can launch, right?" And I was greeted with like, "No, we can't launch." And I think that leaning into that willingness to being vulnerable about your product and this acknowledgement that feedback is a gift, and that bits and pieces of feedback from across the company will help your product mature and get to a place where it's ready to go out the door is really important. And what's really interesting is this helps the team who's working on the product, because you're getting feedback, and that's the most direct benefit of putting something on staging early. But the other benefit about putting something on staging early is that it makes people invested in your product. So if you think about why are betas so valuable and why are alphas so valuable, it's because when someone gives you feedback, and then the team in charge implements that change, you see that and you're like, "I shaped that part of the product. " Right? And to the extent that you can get as many people in the company feeling like they shaped X, Y, Z parts of the product, I think that's really powerful, because, then, you kind of are ensuring that there's this constant feedback loop, and there's this constant investment in thinking about how can we collectively drive towards success, because at the end of the day, product development is a team sport, right? It takes everyone to make something successful. And so I just think about putting things early on staging and getting people involved in the cycle as opening up the doors to the product development process, and hopefully, that just elevates the quality of the product. Is there anything else you want to touch on or share or leave listeners with before we get to a very exciting lightning round?…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.