Sam Altman discusses Paul Graham's advice to be "relentlessly resourceful," arguing that persistent search for new approaches often solves hard problems and is a teachable skill. He recounts a startup-era anecdote where his team made roughly 30 different points of contact to secure a deal with a reluctant mobile operator. He also addresses the difficulty of knowing when to quit—saying there is no single rubric and that such decisions are judgment calls learned through experience.
Chapters
One of the things that Paul Graham used to say that I think never became as venerated advice to the degree it should have, is this idea that you should try to be relentlessly resourceful. Surprisingly often if you just keep looking for new attack vectors on a problem in front of you, you can figure it out. And I think this is one of the most important skills in life and it's surprisingly learnable or teachable, whatever you want to say. And it works, like in almost all scenarios.
Can you give us an example of a time it worked?
We needed to figure out how to get a deal done with this mobile operator. And they didn't really work with startups or technology companies in general. And we probably tried 30 different paths into this company. At one point, the key decision maker said, I'm finally going to meet with you because I want you to stop, stop bothering us, but you can just keep doing that until something works. And I think most people at kind of like the first ignored email or the first path where you don't find the right person into a company, or at least the second would just stop. And I mean, it was like a life and death thing for our company. So we were very motivated to do it, but it was probably like, yeah, 30 different points of contact. Right, right.
And how do you know when or if to quit? You're 19 years old, you're sending these emails to the chief technology office, some Gian company. Your emails keep getting ignored. At what point does it become kind of crazy?
I think there's definitely a balance. You can clearly take it too far and not learn or not adapt or whatever. But the question that when I was running YC that startups would always ask is how do I know when to give up on my startup? And I spent a lot of time trying to come up with a here's the rubric for it. I never did. I think all of these things are judgment calls. You can learn them by very large data sets and trying a lot of times, but it's hard to say. Here's the one recipe that always works, okay?