Inside Gong: How teams work with design partners, their pod structure, autonomy, trust, and more | Eilon Reshef (co-founder and CPO)
Lenny's Podcast: Product | Growth | Career
Deep Dive
What is Gong's pod model and how does it organize product teams?
Gong's pod model organizes product teams into cross-functional units, each consisting of a product manager, a user experience designer, fractional writers, fractional analysts, and 5-7 engineers led by an engineering team leader. This structure allows pods to operate autonomously, focusing on specific outcomes like building new products or features, such as the forecasting tool they developed.
How does Gong work with design partners in their product development process?
Gong works closely with design partners, often involving 6-12 or even up to 24 partners per pod. These partners provide real-time feedback on half-built features, allowing Gong to iterate quickly and ensure the product meets customer needs. This approach has led to a near 100% success rate in feature adoption.
Why does Gong prioritize autonomy and trust within their product teams?
Gong prioritizes autonomy and trust because it allows team members to bring their unique perspectives and creativity to the table, leading to better results. Eilon Reshef believes that giving teams the freedom to make decisions fosters motivation and long-term engagement, ultimately resulting in higher-quality products.
What is the 'spiral method' for learning complex topics quickly?
The 'spiral method' involves starting with a basic understanding of a topic and then spiraling deeper by talking to multiple experts. As you gather insights from different sources, the new information decreases until you reach a point of convergence, indicating a solid understanding of the topic. This method helps in quickly mastering complex subjects.
Why did Gong focus on a narrow initial customer profile (ICP) when starting out?
Gong focused on a narrow ICP to create a 'small pond' where customers could influence each other, leading to viral adoption. By targeting specific criteria like U.S.-based companies selling software over video conferencing, Gong was able to build a strong foothold in a niche market before expanding.
What lessons has Gong learned from being early in AI development?
Gong learned that while LLMs (Large Language Models) are powerful, they don't solve everything. Expertise in AI and machine learning is still essential for building specialized models, such as deal prediction systems. Gong emphasizes the importance of measuring progress and iterating quickly to improve AI capabilities.
How does Gong balance customer feedback with their product vision?
Gong encourages product managers to interpret customer feedback rather than blindly implementing requests. They assess whether a feature is a 'must-have' or unique to one customer. This approach ensures that products are broadly applicable while still addressing specific customer needs.
What is the role of a 'research coordinator' in Gong's product development process?
A research coordinator at Gong handles the logistics of setting up meetings with design partners. They work with product managers to identify target markets and customer profiles, then reach out to potential partners and schedule meetings, streamlining the process for the product team.
What is Eilon Reshef's approach to making quick decisions, even for big one-way door decisions?
Eilon Reshef believes in making decisions quickly, even when the choice isn't clear-cut. He argues that many decisions are 51-49 in favor of one option, and delaying doesn't significantly improve the outcome. This approach reduces overthinking and keeps the team moving forward efficiently.
What is the significance of Gong's 95% feature adoption rate?
Gong's 95% feature adoption rate highlights the effectiveness of their design partner approach. By working closely with customers during development, Gong ensures that the features they build are highly relevant and valuable, leading to widespread usage across their customer base.
- Gong uses a pod model, which is a cross-functional product team structure.
- Each pod works with 5-24 design partners.
- They aim for nearly 100% feature adoption rate.
- Success is attributed to close collaboration and customer feedback.