Evidence receipt / belief
Published · transcript-backedEilon Reshef: belief
2 Jan 2025 Lenny's Podcast Inside Gong: How teams work with design partners, their pod structure, autonomy, trust, and more | Eilon Reshef (co-founder and CPO)
“Of course we had to give them resources at some stage, but it wasn't like a top down, let's do this, it was more like, hey, we're trying it out, hey, we need a couple of more resources, we're trying out more. And at some stage we realized it's super important and then we "funded it" completely.”
Source trail
Everything needed to verify it.
- Speaker
- Eilon Reshef
- Attribution
- Verified speaker
- Claim type
- belief
- Recorded
- 2 Jan 2025
- Publisher
- Lenny's Podcast
Transcript context
…This episode is brought to you by Vanta. When it comes to ensuring your company has top-notch security practices, things get complicated fast. Now, you can assess risk, secure the trust of your customers, and automate compliance for SOC 2, ISO 20000-1, HIPAA, and more with a single platform, Vanta. Vanta's market leading trust management platform helps you continuously monitor compliance alongside reporting and tracking risks, plus you can save hours by completing security questionnaires with Vanta AI. Join thousands of global companies that use Vanta to automate evidence collection, unify risk management, and streamline security reviews. Get $1,000 off Vanta when you go to vanta.com/Lenny. That's V-A-N-T-A.com/Lenny. Is there an example of a product or a really important feature that came out of this way of working where a team just like, hey, you don't think this is a good idea, I'm just going to do it anyway? I don't think it goes up to a whole product, it's kind of very hard to... Because you have resources to build a whole product. But I do think there is substantial features that came out of it. Even the AI fine-tuning example I gave you before, it's like something came up in a hackathon, and people were like, let's start to build it, let's incubate it, and then they move forward. Of course we had to give them resources at some stage, but it wasn't like a top down, let's do this, it was more like, hey, we're trying it out, hey, we need a couple of more resources, we're trying out more. And at some stage we realized it's super important and then we "funded it" completely. So, when people listen to this, some product leaders might be thinking, oh, I want to work this way, I want to give my teams more freedom, more trust, what needs to be true in your org for this to work well, versus it become chaos?…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.