In short
```markdown
Lenny's Podcast
Product | Growth | Career
Episode Title
Inside Gong: How Teams Work with Design Partners, Their Pod Structure, Autonomy, Trust, and More | Eilon Reshef (Co-founder and CPO)
Episode Description Eilon Reshef, Co-founder and Chief Product Officer at Gong, shares insights into:
- Gong’s approach to working with design partners
- Their unique pod model
- The speed of decision-making processes
- Lessons from early AI adoption
- The power of extreme focus
- The "spiral method" for learning complex topics
- Balancing quality with optimization for speed
Key Highlights
Pod Model
- Structure: Gong employs a pod model which involves small, cross-functional teams.
- Team Composition: Each pod typically includes a product manager, UX designer, fractional writing and analyst resources, and a team of engineers.
- Autonomy: Pods operate with high autonomy, driving projects and innovation.
Design Partners
- Collaboration: Each pod works closely with 6-12 design partners, often from existing customers, to co-create and refine products.
- Process: Design partners provide feedback, ensuring the product meets real-world needs and reduces the risk of unused features.
Autonomy and Trust
- Philosophy: Reshef emphasizes giving teams autonomy and trusting them to make decisions, fostering a culture of innovation and motivation.
- Impacts: This approach increases velocity and engagement, contributing to Gong’s success.
Speed and Decision-Making
- Approach: Reshef advocates for rapid decision-making, even for significant one-way door decisions.
- Rationale: Quick decisions are often as effective as those made after lengthy deliberation, especially when choices are closely matched.
Early AI Adoption
- Lessons Learned: Gong was an early adopter of AI, providing insights into balancing foundational AI models with custom solutions.
- Expertise: Maintaining in-house AI expertise is crucial for tailoring AI to specific business needs.
Spiral Method for Learning
- Methodology: Reshef’s "spiral method" involves iterative learning and validation through conversations and expert interactions.
- Outcome: Helps in rapidly understanding complex topics and knowing when foundational knowledge is achieved.
Initial Customer Profile (ICP)
- Strategy: Gong initially targeted a narrow ICP, focusing on specific sales criteria to establish product-market fit and scale efficiently.
Challenges and Failures
- Past Mistakes: Reshef shares mistakes from his previous ventures, emphasizing the importance of focus and product-market fit.
- Learning from Failure: These experiences informed Gong’s strategies and approaches, highlighting the value of learning from past errors.
Noteworthy Mentions
- Books: "The Ideal Executive", "Crucial Conversations"
- TV Show: "Slow Horses"
- Product Discovery: Silverware caddy organization method
- Philosophical Concept: Hanlon’s Razor – "Never attribute to malice that which is adequately explained by stupidity."
Where to Find More
- Eilon Reshef on LinkedIn: [LinkedIn Profile](https://www.linkedin.com/in/eilonreshef)
- Lenny's Newsletter: [Lenny's Newsletter](https://www.lennysnewsletter.com)
Sponsors
- WorkOS: Modern identity platform for B2B SaaS
- Think Fast Talk Smart: Podcast for effective communication tools
- Vanta: Trust management platform for compliance automation
Conclusion Eilon Reshef’s insights into Gong’s operational strategies highlight the importance of autonomy, rapid iteration, and customer-centric design in achieving product success. These approaches are instrumental for those building and scaling B2B SaaS products.
---
_Lenny may be an investor in the companies discussed._ ```
Written by AI. May contain mistakes. Listen to the episode to check what was said.
Transcript
Automatic transcript. May contain errors.0:00I want to start with talking about your pod model, which is a really unique way of building and organizing your product teams. It was probably 2016. We're trying to figure out how does the operating model look like for a product and engineering. The first bunch of people we had was essentially a pod. It was one product manager. A user experience designer, back -end engineers, couple of front -end engineers, but at some stage we're starting to scale. We're contemplating, do we go like the traditional, the old school of front -end engineers, back -end engineers? And then we said, let's try to replicate what we have.
0:28Let's talk about how these pods work with design partners. From what I've heard, it's very unlike how any other company works. We just took the pod concept to an extreme where every pod is working with, sometimes it doesn't design partners, sometimes. Two doesn't design partners. This feels like a cheap code of how to build new product lines. What are the percentage of success rate you have with new product? I would say very close to 100 % of the features we build and are being used by a significant number of people. Does it feel crazy for companies not to operate this way? I wouldn't go back.
0:57I hate terms such as risks, because that's a very ambiguous term, but just a risk of building something you're not going to know if it's going to get used. So when I asked people at GONG what to ask you, the most often term that came up is autonomy and trust. It's a favorite selfish thing to a very personal thing. I just think...
1:16Today my guest is Ailan Resha. Ailan is co -founder and chief product officer at GONG. He was also the long -time chief technology officer at GONG. As I share at the top of our conversation, it feels like basically every company that has a sales team uses GONG. And it's really rare to build a product that is so ubiquitous and so loved across the tech ecosystem. In our conversation, Ailan shares some of the secrets of what makes GONG so consistently successful. Including how their product teams work with six to 12 design partners on every new product and feature that they invest in, how he creates a culture of autonomy and trust, why and also how he optimizes for making decisions quickly, even large one -way door decisions, what he and his team have learned about building AI -based products since they've been building AI -based products longer than most other companies.
2:05And so much more, if you're building a B2B SaaS company or product, you will learn a lot from this conversation. If you enjoyed this podcast, don't forget to subscribe and follow it in your favorite podcast thing app or YouTube. It's the best way to avoid missing video episodes and it helps the podcast tremendously. With that, I bring you Ailan Rachev. This episode is brought to you by WorkOS. If you're building a SaaS app, at some point your customers will start asking for enterprise features, like Samo authentication and skin provisioning. That's where WorkOS comes in, making a fast and painless to add enterprise features to your app.
2:42Their APIs are easy to understand so that you can ship quickly and get back to building other features. Today, hundreds of companies are already powered by WorkOS, including ones you probably know, like Versel, Webflow, and Loom. WorkOS also recently acquired Warned, the Fine -Grain Authorization Service. Warned's product is based on a groundbreaking authorization system called Zanzibar, which was originally designed for Google to power Google Docs and YouTube. This enables fast authorization checks at enormous scale, while maintaining a flexible model that can be adapted to even the most complex use cases.
3:19If you're currently looking to build roll -based access control, or other enterprise features, like single sign -on, scam, or user management, you should consider WorkOS. It's a drop -in replacement for Auth0 and supports up to 1 million monthly active users for free. Check it out at workos .com to learn more. That's workos .com. Hey, it's Lenny. If you want to boost your clarity and confidence, I want to recommend a podcast called Think Fast Talk Smart. One of the most essential ingredients to success in business and in life is effective communication. Every Tuesday, host and Stanford Graduate School of Business lecture, Matt Abrahams, sits down with experts to discuss the best tips and techniques that enhance your professional development, hone your small talk, influence, presentation skills, and so much more on Think Fast Talk Smart.
4:12So what are you waiting for? Listen in every Tuesday, wherever you get your podcast, and find additional content to level up your communication at fastersmarter .io.
4:23Hey, Lon, thank you so much for being here. Welcome to the podcast. Thank you for having me. So it feels like on this podcast, every guest that I've had mentions GONG as a product they use. It feels like it's just like an ether of tech companies these days. Also, I've heard so many times how unique it is that you all operate, how you all build your product teams and operate, which is especially love hearing on this podcast. They're just different ways of operating. So I'm really excited to dig into this, to hear about the journey and things you learn along the way of building GONG. Essentially building something that is so ubiquitous and so loved, which is very rare.
4:59I want to start with talking about your pod model, which is a really unique way of building and organizing your product teams. In particular, how you work with design partners. Let's start with the pod model. You just talk about what this pod model is and how you organize your product teams. Sure. When we started the pod model that was probably 2016 before it became popular, I think that might have been before the Martin Kagan set of books. I don't remember exactly, but at some stage we're starting to scale. I mean, scaling is maybe from 50 people to 60 people, or whatever, in the whole company or whatever.
5:31We're trying to figure out how does the operating model look like for products and engineering. The first bunch of people we had was essentially a pod. It was one product manager years truly. I used our experience designer, maybe back and engineers, a couple of front and engineers and whatnot. We're contemplating, do we go like the traditional, the old school of front and engineers, back and engineers? However it is. Then we said, let's try to replicate what we have. What we essentially did is really replicated that. Up until now, we have this pod structure, product manager, UX, fractional writing, fractional analyst, and then a team leader from an engineering extent, 0 .5 to, I'd say, seven engineers.
6:13They get an agenda to think like we launched a forecast product. That was a pod working on that. Then they get to be pretty autonomous in identifying how to solve the problems and also working with enough customers. I can go to sleep knowing that they're not hallucinating as the term that everybody uses in a different context, but going in a reasonable direction. I want to talk about the autonomy piece. That's a really important point, but before we get there, let's talk about how these pods work with design partners.
6:45From what I've learned from, let's talk about the scale of how these pods work with design partners. I think we just took the pod concept to an extreme where every pod is working with sometimes it doesn't design partners, sometimes two doesn't design partners, maybe sometimes five if it's a very niche or fringe capability. They work with them head in hand. So an interesting story. The same forecast product I just mentioned, the product manager comes to me one day and he's like, hey, I just going to play with a design partner on the product. I'm going to know what's going on, and I know it's not built yet.
7:17So as the product manager, but we don't have that working. So he said, no, no, we don't, but I showed him the sort of the half -build stuff I asked him to hit save. He had saved and got an error message. And I told him, let's be it again in a week and that saved button. We're going to work. So it's very extreme in terms of working hand in hand with the customer. Customers appreciate it. I later got feedback that they appreciate how kind of the thing was going, making progress according to their feedback, not what they said, but kind of interpreting what they said, digesting it and building something that makes sense.
7:49So every bot has this set of design partners. So these pods essentially across functional product teams, each one has the organize it around like an outcome. How do you describe what each pod is responsible for? Is it like move this metric or build this product or something else? We tend to be less metric driven, maybe than in our average, especially B2C, but even like other maybe B2B companies. Usually it's more around some sort of a job to be done. In our case, it could be sense engagement. How do you kind of prospect or conversation intelligence? How do you create this summary? How do you make it easier for people to remove dratuary and consume information fast?
8:24And once you get this agenda, you kind of pretty much have a lot of, you know, you mentioned autonomy and a lot of control over how you kind of progress. Ideally, design partners guide you, not me. Awesome. Okay. So it's like, here's the outcome we want this pod to achieve. They have autonomy to work with design partners to design this new product. So maybe let's stay on this example of this forecasting tool. He just briefly describe with this tool, what it gives you, what it does. Yeah, it's product we launched a couple of years ago. And it helps organization forecast where they learn in terms of the sales organization.
8:55So every sales organization, B2B sales organization has a bottoms up forecast process. People submit numbers, people up kind of override that AI helps you kind of in our case, AI helps you protect the right number. Usually there's an analytics component top of it that kind of helps you assess it at scale. So that's the product itself. Awesome. So you created this pod here, build this forecast product, make it successful. How do they find these design partners? Is it like reach into existing customer base and figure out who would be most interested in this? Usually, usually it's existing customers.
9:26Very, very rarely would be non -existing customers, but customers with some state expressed interest in this capability, not to over like, you know, kind of give a plug to go. But of course, we can listen all of our conversations are recorded. So I can always like look up our kind of conversation database in like which customers express and need for X, Y and then you can very easily kind of reach out to them. One of the maybe unique things we've done at some stage just became, as you can, I think we have like 25 pods right now, maybe 30, I click depends what you call it, pod, but the, it's a lot of effort like this whole management.
10:01At some stage, I bored an idea that comes from a talented position.
10:09And in if you do that scale, which we had done over the years, and that person, all they do is just set up the meetings for the recruiter who then sets up the meeting for the higher manager. So in our, in our product team, there's one person who's basically a research coordinator, and she's responsible for reaching out. She basically talks with the PMs like, what's your target market, ICP, whatever you want to call that? Give me some, what do you want to learn from them? She reaches us, we have a micro CRM for that, and then sets up the meeting, and the PM comes in, they have already like a meeting in their kind of, and these are the design people at these companies that are going to be their design partners.
10:45Exactly. So I might say, hey, what I want to speak is with a head of RevOps, I don't know, midsize companies, or I know IC seller, an enterprise company, and then she can kind of, of course, sift through our customer base, slice and dice it, run in micro email campaign, and get those kind of to come in. I love that detail, because as you said, coordinating 12 companies and people at these companies and timing is really stressful and complicated, and it's like the PMs life up, so that's really helpful. It's interesting, there are some companies where product teams aren't even allowed to talk to customers.
11:16Sales people are like, no, don't mess with these people, customer success, like, now we got this, you're like the complete opposite, is each pod is working directly with, say, a dozen customers helping build a new product for them. Exactly, and in the early days, we didn't even like tightly coordinate with customer success. Nowadays, we do it much better, because there's always going to be this customer's like frustrating about something or in the negotiation about something, that's probably not the right time to ask them about to be a design partner. So we kind of double check, but it's not like a process where we have to get sign of by three customer success managers to talk with a customer.
11:54That makes sense, obviously. Yeah, you don't want to surprise people and mess up relationships. So is there any structure to the design partner process, or is it just teams have these people available and they talk with them when they want, or is there more structure to like, had effectively build a product with design partners? It depends on the context. So when you build a new product, there's some more linear path, right? This ideally wanted to be launched sometime, ideally, I want to measure some progress. So usually what we've done in this case is like some sort of a weekly meeting where we kind of kind of showed them progress and sometimes by weekly, depending on our own cadence.
12:28In some other capabilities that we build might be more, I want to say freeform, maybe it's an enhancement, maybe it's tweak, maybe it's an extension of the, let me give an example, right? One of the things we do right now is we let customers ask a question about an account. So coming to gone, like, what's new with Cisco, if it's because of customer? And at some stage, you do it, we're doing it in all languages, right? So you want to recruit a specific design partner, a set of design partners who are non -ingly speakers. So it doesn't have like a strict timeline. You want to get enough of them.
12:57So you see the thing works, gets your reasonable quality results. You're not going to get to all languages in the one hand, but the same time you don't have like just Spanish. So that might be a less structure. Maybe it's a couple of meetings with each one and then we move on. You launch the feature and you move to the next corner, what project or feature. So one thing that people might be thinking as they hear this is, how do you, all these customers are telling you, here's what I need to be to use this forecasting tool, for example. And as a PM, it's always at this balance of doing what customers ask you to do versus away with this vision.
13:27And here's how we keep it simple. You haven't what God instanted give your teams for what to do with this feedback, essentially. Yeah, I think this is kind of core skill at expect PM's to have around kind of this. This is exactly your kind of job, right? Try to figure out what requests is like must have versus not must have. We typically, they ask the customer, you know, what do you have right now? How happy are you between zero and 10 or whatever? So if you're at the six, we want to get you to an eight or a nine. So that's maybe a high level principle. But at the same time, I expected to say, hey, this is a unique, I didn't hear it from anybody else.
13:59Maybe I'm going to practically reach out to more customers, but that might be a one customer thing. And we still do one customer things if in a different context, right? So if we have a, I don't know, several eight figure deal that they have like one customization that they really, really need. And we know that they can't work without it. I mean, like every enterprise facing company, we're going to do that. But from a design part of perspective, it's the opposite. It's more like let's try to build something that works across our customer base versus for specific customer, which is why it does it is, it's probably smarter than one or two or three.
14:29Yeah, I think at some stage, I guess you get like seven or eight or nine at some stage, based on my experience, the request starts to converge. There might be one outlier, but generally, you're going to hear the same things. I imagine this approach is rooted in how you all started. We worked on a post back in the day on how you all got your first 10 customers. And I remember the story was you got, I think at 12 design partners, when you first design, gone. And then like you told them, we're going to start charging now in 11 out of 12, or like, we will buy this now, please charge us and we love it.
14:58Exactly. Exactly. So it's in a way, it's replicating this, but it was successful at the time. It wasn't, it was like maybe 80 % intentional at the time. And at some point, you take the stuff that works and you make it 100 % attention. What are the like the percentage of success rate you have with new products, because you would think this approach is the best way to consistently build products. People will end up buying and using. Is it like 100 % of the time you end up building things that people will buy and use? Is it something below that? Nobody fine? I think it does increase significantly the utility of the of the products.
15:33I would say very close to 100 % of the features we build and up being used by a significant number of people. We don't charge for all of them, most of them we don't charge, which doesn't mean other things couldn't happen. Maybe people use it, but you know, the value is not huge. So it's like, yeah, design partner likes it, like it, but it's like a plikker, it ends up being a plikker, been to a smaller fragment or segment of our customer base than what we had hoped. It may be they don't not as willing to pay for it. Oh, that's a little bit of a different process, like real product launch. It could be the quality is not good enough, because we're kind of focusing on, you know, is it providing value?
16:07Is it understandable versus like, you know, did you find a bag when you use that on a safari on this kind of computer? Because we're not building the design partner program to kind of solve for this. Maybe we should, but we are not doing it right now. But generally speaking, I would say, but more than 95 % of our capabilities we build are being, you know, kind of used in a very kind of significant way, which I think is probably higher than most companies. And this feels like a cheat code of how to build new product lines, expand product expansion, tam expansion, like ways to add new ways to charge your existing customers.
16:42And it feels like a cheat code, basically, just like tell us what you need. We'll work with you and build it and it will solve to you. It'll be great. Yeah, respectfully of, you know, you're truly, I do believe customers know much better than what they need. And then myself or my colleagues in the executive team, whoever else, it's, you talk to a customer and they kind of describe their pain. They might not know how to build it or what's the right way to implement it, but the pain should be there. Coming back to something else, you mentioned this word autonomy. So when I asked people, a gong, what to ask you and what stands out about you to them as a product leader, the most often term that came up as autonomy and trust.
17:19How much autonomy you give teams, how much you put, how much you trust teams to do the right thing. Can you talk about that way of working where that came from and why you think that is the way to operate? It's about self -esteem. It's a very personal thing. So I think even beyond trust, it's just for me, selfish. I'll tell you why I just think you get more from everybody. If you kind of let them beat themselves and do things in the way that they believe is the right way of course within limits, right? They're not going to like develop, I don't know what it is, software and different business.
17:49But the story I always like to take to tell is when my son was in primary school, which was a while back, one of the parents told me, and we had this picnic where all the parents and the kids were going to meet. Usually there's a list of ingredients that people need to bring in, bring on a bottle of water, whatever the thing is. And what's usually happened, there's even people are joking about it, is people run through the list because it's usually a physical list and then or make night. Probably now it's already in as possible, like a bottle of water and then I'm done. And then you always get the lowest common denominator because everybody brings the sort of, I don't even see cheapest, like the easiest thing that you can bring to such a picnic.
18:31And then this lady told me, here's a different method, just tell everybody, bring your own thing. I'm like, are you crazy? People are just going to not bring anything or whatever you want, right? Or people are going to read the same thing. Like multiple people are going to, I don't know, bake some pie or do something, right? And she's like, no, that's not going to happen. So I trusted her. That's maybe a trustworthy word. But we tried it out and what happened was really kind of fascinating. People were going out to the specialty stores and bringing like specialties where race, I'm based in the internet.
19:01So they were going to this homeless place, which is like, you know, Israeli thing and she's like driving 30 miles to your favorite thing. People were like baking and making stuff. So we had like literally a feast. And if anything, two things happened. Everybody was much, much happier, right? They were happier, because of course they got better food and then you're like, and also most people kind of just their personality, they brought it to the table. It's like, I really like homeless. I don't like the whatever the other thing I would have to bring. And we did it every year afterwards because we did this thing at least annually and it worked every single time.
19:30So if you take it this software, that you can't tell everybody, you know, just develop your own thing. But if you can guide them towards, hey, do the thing that in a, if you more autonomy, essentially bring yourself to the yourself, don't try to sort of put yourself in a box. I truly believe you're going to get much better results short and even more importantly, long term, because it keeps people thinking, it keeps them being motivated and they're like, how do I contribute in the way I think is the right way? Reminds me, I'm looking for daycares for our son. He's like 17 months, almost 17 months now.
20:03And there's this monastery approach to teaching kids. And it's a very similar approach, which is just let them, if they're ever busy with anything, don't even make eye contact. Don't interrupt them, let them keep doing the thing and let them choose what they want to work on. Yeah, there's many, many of these education systems or principles that are along the lines of me, the person who taught me that I don't, I don't assume she's invented it. But we all are on the side of like wanting more control. But I do the same thing with my kids. So I would never, I never installed any piece of software on my kids' devices.
20:39So not like firewall protection, I don't know, antivirus, error tag. And I think, because I'm like, this is your problem. And you know, if you want to, if you want to like protect yourself, it's your responsibility. So this is autonomy. And there was one time we're at negotiated with my daughter, she's like, I told her, I think you're kind of using your computer too much. We negotiated. She said, maybe an hour is enough. I told her maybe more. I think we agreed on a two -hour thing. And then she came to me three days in a row. So could you please install the software on my machine so I can help me like control my limits.
21:11And I love it when it's the other way around because now she's responsible. I'm helping her versus the other around. So absolutely, I take it to my personal life as well. So how does this look day to day at GONG on the product team? Like when someone hears, oh, you give them a lot of autonomy. What does that actually look like? Help people understand what that actually means? It means that if you're working with design partners and you get like an idea from the customer, it's your responsibility to decide, are you going to do it? Are you going to talk to your manager to me? You know, now I have four -square -managers.
Read the full transcript
21:44But it's your responsibility. So we're not going to quote unquote punish you. If you decided that, you know, you kind of took it an opinion from a customer and went ahead and did it. It's your responsibility to decide, you know, do I know enough? Do I need more input? How up do I go? So it's, let's requires them to think, you know, how confident am I in my decisions? So is the way is the culture basically you give them feedback and advice and the teams can operate the way they want. They can build the features. They think they're important work with design partners that they think are important.
22:18Yes. And of course, you know, you are expected to solicit feedback, right? So if you're going to build your own thing for six months and it's going to be, we're going to have, we're going to review it along the way, of course. But we expect you to initiate a review. You have like a, we have about a weekly session. We can bring up your reviews. But it's not as forcing you to do it. You have to bring it. You have to solicit it. And you have to sort of drive a process. This episode is brought to you by Vanta. When it comes to ensuring your company has top -notch security practices, things get complicated fast.
22:48Now you can assess risks, secure the trust of your customers and automate compliance for SOC 2, ISO 27001, 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 slash Lenny. That's V -A -M -T -A dot com slash Lenny.
23:31Is there an example of a product or a really important feature that came out of this way of working where a team just like, I, you don't think it's a good idea. I'm just going to do it anyway. I don't think it goes up to, to a whole product. It's, it's kind of very hard to, because you got to have resources to build a whole product. But I do think there are substantial features that, that came out of it, even sort of the kind of the AI fine tuning example I gave you before, is like something came up in a hackathon and people were like, let's start to build it, let's incubate it, and then they come move forward.
24:01Of course, we have 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 more resources. We're trying more and in some stage, we realize it's super important. And then we kind of, quote unquote, 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 or trust. What do you, what needs to be true in your org for this to work well versus it become chaos? Firstly, use a leader and need to sign up to like, sort of let go a little bit, not control everything.
24:35We link to sort of make some more mistakes than maybe you'd make otherwise. So that's the one thing. I think the harder thing is sort of, at least for me, is you also have to sort of get your peers on the same boat, right? Because the head of sales is going to ask you, hey, what's happening? How do I know what's happening? If you don't have a control over every feature and the CFO is going to ask you, hey, what's the, I don't know what if they are or are of this or how do you justify those type of decisions? So there has to be some fundamental trust within you know, you're in your team, you're in your colleagues to, to at least experiment that way.
25:14And of course, if you do an ongoing basis, you lose some visibility. And I think that's maybe one thing you got to acknowledge, right? Because if you give people more control by definition, you're going to have less visibility what you're doing. So give a little bit of visibility, hopefully get the benefit of higher velocity and higher what more are low or, you know, engagement from people. And that should result in better products as well. I love that. That's a really good example. With the sales example, which is great. Do you encourage the sales folks to talk directly to the pod to ask about these sorts of things?
25:47Or do you discourage that sort of communication? Yeah, I think sales from my perspective are part of the virtual pod, right? So the court pod is, as I mentioned, a product engineering, but part of the virtual pod is there's product marketing, customer success sales. In all fairness, you know, sales people are usually busy doing their work versus actually sitting with us and helping us kind of, is this going to sell? Did you hear it from customers? The type of questions that product managers usually do want to get. But if they're happy to spend time, they would be very evil. Coming back to the design partner way of working, does it feel crazy for companies not to operate this way to not work this closely with design partners on new products and features they're building?
26:31I wouldn't go back, right? So I think it's just like, even like, I hate terms such as risk. That's a very like, I don't know, like up a big use term, but just a risk of building something you're not going to know if it's going to get used. And I was asked by a sort of a very senior product manager of a very successful big SaaS company. It's like, why do you even do this? I'm like, what do you mean? We launch products and then we see if people like them. I don't think that's a great idea because in that company, successful, bigger than God, but at the same time, I just think it's leaving too much in the hands of, I would even call it luck, right?
27:06Because how do you know? Yeah, like I was thinking, it just feels like a cheat code and just feels like something a lot of companies can learn from how you all operate there. Something that has come up a bunch, so far in our conversation is your focus on speed and optimizing for velocity. Something that I've heard about you is that you're really big on just making really quick decisions, even like one way door decisions that are really big. Your philosophy is just make it quickly before you have all the information necessarily. Talk about that approach. That's maybe a little for a person I think, but I would encourage people to look up in Google, there's maybe I do a spoiler for it.
27:43Isaac Asimovie, the science fiction writer, I think beginning of last century, and he has this like a short story that the machine that won the war, so you can look it up. It's a fun story, pretty short, but it's basically the computer, the big computer at the time supposedly won the war, but the only reason won the war is because they wanted people to trust this superhuman machine, but what they realized the machine was just giving crap, just like our anemonesination. So the head, the person, president, whatever it is, basically ended up saying, I end up tossing a coin, but people wanted really believe that this is a smart machine thing that's going to help us win the war.
28:19So it's kind of obviously a funny story, but I think there is truth to it. It's many, many decisions when it's not a close call. It's like, should go, should go open an office in China right now. Well, probably not. There's so many reasons why not. We don't really be baited, but should we develop feature A and feature B and you look at them, they're kind of the same, I don't know, call it same value or same cost or whatever. However, whatever kind of mental framework you have for deciding, you end up being like 51, 48, 49. No decisions going to be like super wrong. So yes, you can try to bring in more data and you can try to sort of like bring more people, but like both decisions are okay.
28:57So just go ahead with one. Hopefully it's not like a huge, a huge mistake. I'll tell you I had this discussion with my co -founder, I meet with the CEO. And a few years ago, we're considering buying a company. And you know, it's like pretty strategic decisions, right? And we're like, I know there's pros and cons. We're like on the fence there. And we end up not buying the company. We kind of look up gone and we haven't bought like big companies. And I asked him maybe it was a couple of months ago. It's like, what if we had bought that company? Do you think we would have been in a radically different position?
29:30He was like, no. So it's like, I mean, it could have been better, it could have been worse, but it would not have made a huge difference. And the reason is it was a 51 -49 decision. It wasn't a 70 -30 decision. So it's hard for humans to make decision. You probably know, there's experiments that show it's almost like running or jogging or doing something that is a physical requires your physical capacity to make decisions. So just make it, I know it's hard that you want to postpone it, but just do it. It's such a freeing way of thinking about it. It's interesting because there's been recent conversations on this podcast where Spotify has this kind of value.
30:06They call Talkest Cheap. And it's meant to be a virtue. Talkest Cheap, so let's just talk a lot before we make a decision. But it's specific to Spotify because there's like a lot of regulatory challenges. And if they make it a big decision, it's a long term. It's like they put a lot of effort into it. So it's interesting, there's such different ways of operating. There's like, let's just talk for months and make a decision versus we're just going to make it and it'll be fine. Yeah, of course, like big, big one door. Yeah, I mean, this is of course, you're going to spend more time on, but people tend to overthink I think decisions.
30:42I also found out personally, the quality of my decisions, if you sort of wake me up in the middle of the night and ask me, what do you think about X? And I'm going to be like, I have no idea. I'm slipping. And then you're like, you know, you've got to force me into decision. I'm going to make a decision. Now you're going to give me two weeks to ponder over it. I don't think the quality of the decision is going to be much, much higher, which is maybe person, could be personal. But that's at least what I found out over my too many years of existence. So I think something that's probably necessary for that to work out well is having a deep experience in that space.
31:14Like you've been at this for a long time. So I imagine your instinct often is trained based on your past experience of the market and customers. You feel like that's a necessary component of trusting your gut and instinct on these sorts of decisions. Yeah, of course. You got it. Some stage note you're doing. Yeah. If I were now to make a decision around, I don't know, entering a different space, there's no way I would be like, yeah, let's flip the coin like the Asimov story and go for it. I take it, I go to a conference, learn it, whatever the thing is, and then make it a decision. But most of the decisions all of it make on a day -to -day basis is now our domain of expertise versus like totally new statistics.
31:46Awesome. Okay. Let's talk about AI for a bit. You guys were very early on AI. You were working on, basically, AI was like your product was built on machine learning back then, what it was called. Before it was cool and everyone probably thought it was like a waste of time and like, no, it's never going to work. Now everyone's building AI, building AI into their product. Would have you learned about working with AI over the years that you think people maybe are not yet aware of or that will likely cause them pain that you can help solve and avoid for them. Yeah. Funny. When we launched GONE, we didn't use the term AI because people thought it was bad thing.
32:23It makes wrong decisions or they just thought it was an action item at Acroony. When we found it going, I was in sabbatical and actually went to this deep learning course because I was bored in on fairness. After that course, I ended up buying a video stock, which I wish I had kept up until now. But I did send an email saying, hey, this is the next thing. So we understood it's the next thing. Of course, we didn't know it's going to be an LM and GPT and other acronyms that evolved over the years. And probably in now that we're talking about the end of 2020, four -ish, I think people should not go from one extreme, which is, hey, we need a bunch of data scientists for every small project, which was the case five years ago or three years ago, to an other extreme, which is, hey, LM is going to solve everything because LM has done so with you.
33:14We use LM's over the place. Most companies have developed AI kind of stuff for use LM's. It's a great thing. But at the same time, don't assume it does everything. You're seeing some need some of the core competencies of AI. So you do want to have expertise, people who actually know what they're doing and help guide us PMs around, is this something that can be built or no? Because if you're going to spend many, many hours on asking an LM to do, I don't know what, like in a case of gone, for example, tell me what the good sales cycle look like. It looks like LM's don't do that. It's just like maybe something else does, but we have a team prediction model.
33:55LM's cannot predict these because it's like very, very specialised. So I think you need to still have expertise. You still want to have some measurements. So yes, version one, you can just go to an LM and say create something, I don't know, whatever. But if you don't have measurements, like in the old machine learning, whatever metrics you use, you're not going to advance. You're going to have V1 and they're going to have V2 and there's no way to know if you've made a progress. So we kind of pay a lot of attention to, we have people who are going to specialise, you know, how you measure this LM system, which is kind of the one, using chess as well.
34:28And we do have experts who kind of help us make the right decisions. You can make a very, very good progress without these. But I think there's a glass ceiling if you don't like figure out how to kind of create a more operational rigor on this whole AI thing. So what I'm hearing is don't assume you can just outsource all your AI magic model building to the foundational model companies. You need to have your own AI expertise and how expertise. Yeah, or even if you end up outsourcing the core work, at least you have to have the expertise to understand what is doable, what is not doable, what's the right way to approach it, what's the input you give to the LLM, how is this going to be good quality or bad quality?
35:08There's even like, if you just take the product management aspect, if the LLM gives you something that is 90 % accurate, or I don't know, people are going to think it's good. The products are a little different than if it's 50 % good. So just the way you even think about it, the way I think Figma calls their AI feature like first draft, which is a term I like, because they kind of realise it's not best, it's not great, but it's a good first draft. So if you know what it is, it's easier not just to name, but how to conceptualise how to build a workflow around it, and what to train users to assume for it.
35:42And I think there's an expertise there that comes on top of an LLM, even if you just use LLM, so you can't afford or you don't want to go deeper. For folks that want to do this at their company, what are the functions that you have that help you do this? Slash skills of people you hired that you think are far important. So I think you still have to have this kind of quote unquote that data scientist role and data scientists could be in the company, it could be advisors as well, right? It's not everything has to be a full time in the company, and the role of a data scientist is help this help guide the company, right?
36:22Deal prediction model, is this an LLM thing? Do you need to build a model? If you need input, do you need how long it's going to take? Also, in our world, at least data scientists are the people who know how to measure these things. Is this model better? Is this model better? Is this problem better? Is this problem not better? And the judge then a little bit judgment, right? So when Gaul creates an account grief, at the data scientist is not going to know if that brief or this brief is the right one, but they can kind of guide us through what's the right tool set you need to sort of put it in front of customers and how do you measure this and what not?
36:53And then I think in the end of the day, you also need like this myth, you know, kind of now it's becoming a common, you know, the sort of the prompt engineer, the person who's actually working with the NLM and guiding them, that that is like a it's a bit of a technical skill, but you got to have it in it and it doesn't have to be a full -time person, but needs to be there needs to be that expertise of somebody who's actually optimizing things. Many, many customers tell us that you know, going to AI as well, it's more accurate than others. Yes, there is some combination of models we build from scratch fine tuned because we have AI expertise, but some of it is also how we kind of the prompt we give to the NLM is how much rigor we put into optimizing them and kind of finding the edge cases and and ranking them and improving them over time.
37:34If you want to get really good AI, you have to invest in it as well. As you're talking, I'm thinking about how the your pod model matches really well with this world of things moving so quickly, AI changing constantly, just giving teams autonomy feels like a huge advantage in this world where things are just changing weekly. Yeah, so we have a couple of maybe you know, it's three different pods, we have like an embedded AI specialist team, either as as specialist or a team or I don't know, a couple of people and then they kind of can iterate very, very quickly on using NLM's or using non -nLM's, you know, SLM's people now say a small language model, but whatever the thing is, they can iterate very, very quickly.
38:15Awesome. Okay, a couple more things I want to touch on. One is the spiral model. So you mentioned that you just went to learn deep learning on your own. You like went off to the side, I'm going to understand this new thing that everyone's talking about deep learning and you got really smart and machine learning basically really quickly and you have this thing you call the spiral model or the spiral method for how to learn something complex quickly. You wrote a medium post about this or block posts. What is the spiral method? How does it work? How do people learn things really quickly? But it really complicated.
38:47Yeah, I think it's even beyond just the speed, but also like how do you even know that you learn that you actually learned it? So it's kind of there is a mathematical kind of, or not physical concept called annealing, which is how certain kind of material kind of becomes the way it is and it's sort of the temperature goes slightly down, visually becoming crystal or what not. There is an element to this, I think in learning as well, which is you want to know what deep learning is, that you know nothing, you go find the person next to you and you're like, what is deep learning? They tell you something.
39:18Of course, you don't know anything because you just heard from one person and then I questioned, that's like, who else should I be speaking with? They give you three other names. I think in tech, we all tend to be to have like this very, very kind of cool ecosystem of people who are willing to help as long as you don't ask too much of them. So they speak with three other people and then they give you like other names and you sort of go around. And ideally at some stage you feel like, you know, first person you have no idea what they're talking about, you probably didn't even understand what they're saying.
39:44The fifth person you might understand 50 % or 50 % is like new. At some stage you're going to feel like, well, new stuff is 10 % or 5 % or 0%. I call it a spider, because it's going to go in circles around the target and eventually you feel like, well, I'm hearing the same thing again and again and you're like, well, if I heard it from three people, I didn't learn anything new. I'm sort of at the bull's eye. Of course, at the level I am. So I'm never going to be like a deep learning specialist in the same way that, you know, through data scientists are. But as a product manager, I know it probably as well as I can, given that, you know, everybody I spoke with at the time was not giving anything new at the level of the diet desire to this side.
40:22I love that. Is there anything you've been setting recently that you've either used this method for something else you're excited about learning that's new or on the cutting edge? Usually I kind of do this for, for kind of use cases within, within our customer base. For example, if I wanted to sort of, if you wanted to go after a certain persona or a certain use case for the product. So we had this notion of can we do a better job for a specific persona within sales, people who are account managers. So I would use a similar method. I talked to one account manager, I took to an analyst or whatever the thing is.
40:58And eventually when you start hearing the same thing, it's like, what do they care about? It's different than it sets salespeople like selling new business or different that contact center sellers. When you start hearing the same thing, you're like, okay, I kind of got to where I need to be. Now I can make decisions. I can always do another spiral and get one level deeper, which is, I don't know, to some user research go all in. But at least at the sort of the conversation level, I've got that where I need to be. I love how simple this is is you just start talking. Just find somebody to talk to you ask about this.
41:29No pressure. And then just, okay, who else did I talk to you? Just keep having conversations, spiraling deeper and deeper into knowledge and wisdom. Okay, one day I wanted to touch on, which is always stuck with me about your approach initially, when you were starting GONG, is your how you found your initial ICP, who to go after. And it's it's really funny how narrow you got when you all decided here's who we're focusing on for our first dozen customers. So I have the list here. So when you decided here's who we're targeting, here's the list of constraints. We're going to target people selling their product in the US in English over video conference using WebEx, which is the big one at the time.
42:13Selling software that is worth $1 ,000 to $100 ,000. And there was only 5 ,000 companies in this bucket. Can you just talk about why you found it was so important to get so narrow and just the power of getting really narrow, which is very counterintuitive to a lot of people where they're like, oh, we're just going to be for everyone's huge market. I think it's sort of the traditional I call it the bowling alley or whatever you want to kind of form a mechanism. Yeah, the crossing the chasm kind of methodology, which you want to start narrow, you want to create this kind of small point where people talk about each other and you can kind of light the fire in there.
42:54In my previous company, I by the way, I edit it, crossing the chasm and I told myself, nah, I can do way better than that. So we had one customer in, I think it was L 'Oreal or one of the cosmetics companies in American Express in Cisco, like different industries and there was no way we could scale it because everybody had their own lingo, the way they thought about the technology and whatnot. So by having a smaller set of kind of customers or I see kind of definition of customers, you can develop like much more focused and it's easier to light the fire because people move, right? At some stage, I think it was you're one into the business.
43:29We heard from a company that they interviewed a salesperson and the salesperson asked, are you using GONG? They said we are thinking about using GONG but we're not. Like, well, I'm only going to work for companies that use GONG and that's this sort of the power of a small pond with like companies that are like each other because you get this viral effect that is not commonly B2B but it's as close as you can because of those conversations. That other customer became a GONG customer literally because they interviewed a person who told them he's not going to come unless they bought GONG. You can do this if you have a wide market where people don't even talk to each other and there is an assumption that you're not like varying yourself at this market.
44:05I love because today, like I said at the very top of this conversation, you're just so ubiquitous. Like, everybody seems to be using GONG and I love that you started with something with those like seven, I don't know, different constraints to narrow down who you are going after and it's such a good example of the power of starting very focused and then expanding from that, which is what you've done. Okay, last question before we get to our very exciting lightning round. We have a segment on spot gas called Fail Corner where so many of these podcast conversations, everyone's always sharing all the successes, everything's always going great.
44:38Nothing ever goes wrong. In reality, things often go wrong. Can you share a story from your career or just the journey of GONG when things didn't go well, when there was maybe a failure and if you learned something from that time, what you learned? Yeah, I always kind of joke that in my previous company, we've done so many mistakes that if life limited you to a certain number of mistakes, I wouldn't have any left thing. I still do mistakes, but just so many. So every one of them probably done twice or and then it's like, oh, it's some stage is like, you know, third time's a charm. So the one I just gave you is like probably the worst is crossing the cas and you start a company, you have this like technology.
45:19I was thinking, let's go horizontal and that technology was whatever web integration something. Eventually ended up being an e -commerce content syndication or content management SaaS software, which is the right way to go because you want to specialize in a certain market, but initially just going all in was like just ridiculously not smart. And the other thing we did together was like that was the previous company started year 2000. So there was like the bubble, one of those very, very nice bubbles. So like, you know what, we actually got three customers admittedly in totally three different segments.
45:53Now let's go and scale. Now we only we get like we need like one salesperson, one is E and C kind of do what's now called product market fit. I don't know the term even existed there. And we're like, nah, you know what, investors told us he got higher more people. So we hired another 20 salespeople, all of them failing miserably because we didn't have a true product market fit, but even what's worse, we didn't have true focused ICP with like a very, very pitiful and a broad market fit. So if you sort of hear me talk about sort of how we started going, I mean, kind of there's the CEO and he kind of drove it out of that business strategy, but sort of me being sort of a cop out of there and definitely bringing the same.
46:30I'm not going to make that mistake again. I might do new and fun ones, but not that same mistake again. Awesome. Thank you for sharing that. With that, we reached our very exciting round. Are you ready? Sure. Let's do it. First question, what are two or three books that you find yourself recommending most to other people? There is a set of books. I think one that is sort of the starter one is I think it's called right now the ideal executive. People don't really know itself and manage the book out around a team and whatnot. I think the original version is funnily enough. I think it was called mismanagement, but nobody want a Bible called mismanagement.
47:09Much rather by a book that's called ideal executive because you of course are not mismanaging. You're the ideal executive altogether. So you're just reinforcing yourself. The joke society is basically kind of gives you the, it's trying to sort of define people by four characteristics. I think misnamed, but like are you an administrator? Can you like, are you, he calls it a producer, basically get the job done, integrated, which kind of brings people together. And the fourth one, it's basically kind of changed an agent, you know, kind of do a lot of mess and change stuff. Usually entrepreneurs can include that part of course.
47:46And basically his claim is like nobody does the whole for. He can maybe you're good at one, maybe okay at the other. And personally, I'm horrible in administration. So I obviously acknowledged that and I tried to sort of compliment myself. But so I think there's two things in it. Firstly, just those, I thought there was like the four good ways of looking at people as a manager as a leader of course. That's one. But I think even if you disagree with those four, just rekindle just like understanding that you want to look at the people in the organization yourself included. And it's sort of prism of, you know, key characteristics, and you can select a different framework helps you a lot with creating high velocity discussions with others.
48:27Because I can talk with somebody say, Hey, you're a P. So like, well, I'm not the PM and I, whatever the thing is. And that makes a discussion that is like much, much faster and more comprehensive as than just like trying to explain this from scratch. Like, Hey, you tend to do this and you might want to do this and you might want to strengthen that. So I'd recommend starting from this. But there's probably other methodologies you can pick and maybe kind of some of the listeners here have already had one. But that's one I like because kind of found it useful. And that's it's called the ideal executive.
48:59I think some pretty sure. Great. Any other books before we move on? That one's going to probably be very important. I like crucial conversation. That's going to mean the beating path. It's like how to conduct conversations with people in your organization. I think it's never bad to sort of read and immerse yourself into how to speak properly with other people. We have an episode coming up where we're going to share scripts and phrases to use to have better hard conversations. Yeah, it's good. Yeah, I'm excited for that. Slash scared. Okay, next question. Do you have a recent movie or TV show you really enjoyed?
49:35I didn't have TV like brought this TV for many, many years. So nowadays there's Netflix so you can find stuff. But in my case, in sort of a TV and movie tend to be pretty esoteric for an orange. So I've recently watched this British TV series called Slow Horses with Gary Aldmann. And it's a really kind of fun, you know, sort of funny spy thing, which I fall I'm using an intelligence at the same time. So some kind of comedies tend to be pretty kind of lowest common denominator. That one seems still fun and witty at the same time. So that's my latest that I kind of really kind of enjoyed watching even the third season.
50:14I love Slow Horses. It's like, I don't think it's that obscure. I think it's like one of the ones Apple promotes often. I will say the last season was not not my favorite, but the other two are. Yeah, I hundredth center green, which I said, even the third season was okay, but the first two are really, really good. Yeah, it's super fun. It's a force. It's like me like three tries to actually get into the show initially, because people kept telling me it's so good. And I started watching and it's just like, who's this old messed up guy just complaining endlessly, but you got to keep watching. Okay.
50:43Do you have a favorite product you recently discovered that you really like? I see him. You have a silverware caddy in your dishwasher, right? Oh, yeah, it's a poet like Forks and Ives. Yeah. The category. So that's my favorite product as a flageley. And I'll tell you why. It's a funny story. I lost mine. You can ask yourself, how can you, you know, freaking lose the like one of those baskets? And it was in the in the dishwasher, of course. And for some reason, I couldn't find it. That's like you have to be really kind of out of you might not find. Anyway, so I go to some Amazon or eBay or wherever I just buy a new one.
51:18And then of course, a day later, I find it's like a fence somewhere within the dishwasher. Now I have two. So this is my latest invention. If you have two of those baskets, you could put one of them in the sink and you can just like continuously load your cutlery or silverware while the thing is working or you haven't vacated it. So it kind of changed how we organize our kitchen with something that probably cost 10 bucks. No product managers ever thought about offering two of those with your dishwasher. I don't even try to upset anything of any of that. And I told you with some people, I actually ended up buying a second one and it was successful, which is the most ridiculous thing.
51:53It's like you spend 10, 15 bucks get something organized in a completely obscure and unintentional way. I'll give you an even crazier idea that a previous guest suggests Rory Sutherland has this pitch that you should have two dishwashers. Everyone should have two dishwashers because one could is your clean and one is dirty. And you just take your plates and things out of the clean one, use it and put it straight into the dirty dishwasher. And why are we just putting things away constantly just like go from one to the other one to the other? So there you go. Similar idea. Similar idea. I'm actually a thin box, though, a little bit maybe cheaper.
52:31Exactly. How is this an design for two dishwashers? Okay. Two more questions. Do you have a favorite life motto that you often come back to find useful and worker in life? Why did I use this going to sound funny, but it's actually really, and I use it and actually believe in it. It's not sure if you know for philosophers like Razer's like all comes Razer, which is basically. There's other Razers. Yeah, there's so many Razers and there's one that I think came in in some Murphy book or what not. And it's called Handelman's Razer. You can look it up Wikipedia or wherever. And it basically says it goes like never attribute to Melis.
53:08That which is adequately explained by stupidity. So it obviously sounds funny and it's trying to be funny. But it's so helpful because so often do we attribute like people's behavior, you know, thinking a company, a customer, I don't know if personal life sometimes to Melis like, oh, this person's not returning my calls because X or this person hasn't given me feedback or has given me feedback because of X. And it's sort of like we all, I think there's the saying like always assume well or with intent or whatever. And this is sort of the more funny way to sort of say that. Yes, the person is, and against stupidities, only a funny way to do it, maybe in a appropriate, but it's basically yes, they just didn't know, they didn't care, they didn't think about it, they weren't trained, whatever the thing is.
53:52And if you take this model new day to day life, at least I find that it's it's so true and so often true. That is, you know, funny but inspiring. I really love that quote. I think of it often when somebody's doing something that it's annoying me. Final question, you mentioned that you are from Israel, you live in Israel, you mentioned delicious food, hummus is one example, is there another Israeli food that you think people are sleeping on that you think you push to try when they have a chance? Israeli food has become a little bit, you know, kind of gotten a little bit to be in fashion lately.
54:25So people coming from the US to visit in the office are like, oh, Israeli food is so good. And I'm like, what do you mean it's the same food we've had for like 20 or 30 years? I think the taste changed because you kind of eat more healthy and less oily these days. Most of these Israeli food is sort of Arabic in nature or Turkey. So there's great falafel, great hummus, pita bread, Turkish delights of sorts. So a lot of those. And some very, very obscure and if you come to Israel and show Iran, some very less known food that only kind of special guests get to taste. What's that? What's one here?
54:59Okay, and say it here. You're not allowed to know. There is there's a thing called Sabih for example, nobody knows of it. It's people claim it came from the people who came from Iraq, but my wife's father came from Iraq. He's like, we've never seen this before. It's sort of pita bread filled with hummus and eggplant and eggs. Now maybe something else I have no idea. The heenie maybe I don't know. It tastes good, but it's such a weird combination and it's become a little bit of a thing. Nobody knows what the origin is. I think it's some, somebody made a mistake and gave it a name and now it's like ubiquitous.
55:31Hmm, but you are making me hungry. Elon, this was amazing. Two final questions. Where can folks find you if they want to reach out and learn more? Maybe ask some follow -up questions. And how can listeners be useful to you? I'm really available. LinkedIn is probably the best way. I tend to kind of read my inbox and LinkedIn and respond when I can. And then useful to me. I mean, if you want to come work for Kong, check out our careers page, of course. The product team is mostly based until I've even doubled in Iron -N. So maybe a little bit removed from most people, but there's sometimes folks in the US and sometimes non -products.
56:06Of course, Roj, we're hiring quite a few people these days. So we'd love to at least give us a chance. Awesome. Elon, thank you so much for being here. Thanks for inviting me. Bye everyone. Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or a leaving review, as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at Lenny'spodcast .com. See you in the next episode.
From the publisher
Eilon Reshef is the co-founder and chief product officer at Gong, one of the most ubiquitous B2B products in the world. In our conversation, we discuss:
• Gong’s unique approach to working with design partners
• Their unique pod model
• Why Eilon makes big decisions quickly
• Lessons learned from being early in AI
• The power of extreme focus
• His “spiral method” for learning complex topics quickly
• How to maintain quality while optimizing for speed
—
Brought to you by:
• WorkOS—Modern identity platform for B2B SaaS, free up to 1 million MAUs
• Think Fast Talk Smart—Tools and techniques to help you communicate more effectively
• Vanta—Automate compliance. Simplify security
—
Find the transcript at: https://www.lennysnewsletter.com/p/inside-gong-eilon-reshef
—
Where to find Eilon Reshef:• LinkedIn: https://www.linkedin.com/in/eilonreshef
—
Where to find Lenny:
• Newsletter: https://www.lennysnewsletter.com
• X: https://twitter.com/lennysan
• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/
—
In this episode, we cover:
(00:00) Eilon’s background
(04:20) The pod model
(06:33) Working with design partners
(09:13) Finding and coordinating design partners
(13:12) Balancing customer feedback and vision
(15:10) Gong's 95% feature adoption
(17:05) The importance of autonomy and trust
(23:30) How to implement this unique way of working
(27:15) Speed and decision-making
(31:47) Early AI adoption and lessons learned
(35:50) Building effective AI teams
(38:16) The spiral method for learning
(41:36) Narrowing down the initial customer profile
(44:24) Failure corner
(46:35) Lightning round
—
Referenced:
• Gong: https://www.gong.io
• Cisco: https://www.cisco.com/
• How Gong builds product: https://www.lennysnewsletter.com/p/how-gong-builds-product
• What is Montessori education?: https://amshq.org/About-Montessori/What-Is-Montessori
• Isaac Asimov: https://en.wikipedia.org/wiki/Isaac_Asimov
• Amit Bendov on LinkedIn: https://www.linkedin.com/in/amitbendov/
• Lessons from scaling Spotify: The science of product, taking risky bets, and how AI is already impacting the future of music | Gustav Söderström (Co-President, CPO, and CTO at Spotify): https://www.lennysnewsletter.com/p/lessons-from-scaling-spotify-the
• Nvidia: https://www.nvidia.com
• Figma: https://www.figma.com
• The Spiral Method: https://www.gong.io/blog/using-the-spiral-method/
• Webex: https://www.webex.com/
• L’Oréal: https://www.lorealparisusa.com/
• American Express: https://www.americanexpress.com/
• Slow Horses on AppleTV+: https://tv.apple.com/us/show/slow-horses/umc.cmc.2szz3fdt71tl1ulnbp8utgq5o
• Dishwasher basket: https://www.amazon.com/Munchkin-High-Capacity-Dishwasher-Basket/dp/B07ZPMYKKS/
• What most people miss about marketing | Rory Sutherland (Vice Chairman of Ogilvy UK, author): https://www.lennysnewsletter.com/p/what-most-people-miss-about-marketing
• Occam’s razor: https://en.wikipedia.org/wiki/Occam%27s_razor
• Hanlon’s razor: https://en.wikipedia.org/wiki/Hanlon%27s_razor
• Sabich: https://en.wikipedia.org/wiki/Sabich#Ingredients_and_description
• Careers at Gong: https://www.gong.io/careers
—
Recommended books:
• Marty Cagan’s books: https://www.amazon.com/stores/Marty-Cagan/author/B00J21JTNM
• “The Machine That Won the War”: https://www.goodreads.com/book/show/18402398-the-machine-that-won-the-war
• Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers: https://www.amazon.com/Crossing-Chasm-3rd-Disruptive-Mainstream/dp/0062292986
• The Ideal Executive: https://www.amazon.com/Ideal-Executive-Ichak-Kalderon-Adizes/dp/0937120030/
• Crucial Conversations: Tools for Talking when Stakes Are High: https://www.amazon.com/Crucial-Conversations-Tools-Talking-Stakes/dp/1260474186/
—
Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.
—
Lenny may be an investor in the companies discussed.
Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe




