Inbal Shani: recommendation

Transcript context

…I wanted to ask, so GitHub came up with this whole Copilot idea. We had Ryan on the podcast talking about how there's a researcher just experimenting with what can we do with a bunch of data. And then that essentially turned into, wow, this is actually working. Let's quickly scale this and launch it. I guess is there anything you learned from that huge success within GitHub and Microsoft to find other big opportunities? Is there something you do about how you structure product teams or create space for people to experiment with things like this to find the next Copilot? It's a lot about that. It's a lot about creating that bandwidth for the team to innovate and experiment and carving that time out, but also being okay that not every experiment is going to be successful. So the shift to learn or to fail forward, these are the philosophies that I believe in. If you don't try, if you don't experiment, you will never innovate. And if you don't fail, you will never learn from your mistakes, you'll never learn from your experience, so you will not progress forward. So really creating that ability to experiment, the same that we've done with Copilot or we've done in GitHub Advanced Security or even the way GitHub was created, it's all that innovative thinking that the teams have that are thinking about what is that next generation use case? What is the future developer will need to be happy, to be more productive, to do their job? In a world that software development is changing so fast, you have to create that bandwidth for the next generation, the next innovation. And if you didn't have a chance to see that the two-day keynote in Universe, I highly recommend because we basically shared our next vision for Copilot with Copilot Workspace. We also had Satya Nadella on stage and he was very excited. He's like, "Oh my god, GitHub, if you build that, this is amazing." So you see that we keep on putting this vision forward again and again at least six months to a year before we even have something in the market because we're already thinking, we're already innovating, we're already on the next thing. Is there something that you do to allow for that other than just these principles of ship to learn and it's okay to fail? Is there a way you structured teams or resource teams? Is it like you have a percentage of time to think about other ideas, or is it just generally we're okay failing, find time to work on other things?…

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