2 ms·
Let's say that having high intelligence makes you 5% more effective per standard deviation at everything you do, but deliberate practice makes you 10% more effe
by nostrademons 12y ago
Let's say that having high intelligence makes you 5% more effective per standard deviation at everything you do, but deliberate practice makes you 10% more effective per week at whatever you practice.
Now take two founders, one of whom is twice as effective at fundraising as the other. There are a couple possibilities: maybe he spent 7 weeks more time practicing fundraising than the other, or maybe he spent 6 weeks more and is 2 standard deviations more intelligent. If he spent 7 weeks more time practicing, then the other founder who devoted that to, say, customer development will know the market twice as well. But even if he spent 6 weeks practicing and gets a boost from his higher intelligence (equivalent to 1 week of practice), the other person is still 60% more effective at the other stuff.
This model is very much simplified, but illustrates a big point that I took a long time to learn: small broad-based improvements take much longer to pay off than targeted, high-% improvements in narrow areas. So yes, being intelligent is nice, it helps slant every skill you learn in your favor. But it is no substitute for actually practicing hard and removing errors.
There are similar counterintuitive principles at work in many other areas. I've found that engineering tools or frameworks that promise a few percent improvement in productivity are rarely worth learning and almost never worth developing unless they have a huge userbase, because it may take you 2 months to develop them but if they save you 5% in development time it'll take 40 months to break even, by which time they're probably not applicable anymore. Similarly, you are almost always better off hiring the person with little experience who is really passionate about your company, rather than the guy who is seemingly a genius at everything he does but really doesn't care about you or what you do. It's probably also behind the YC advice to be "narrow and deep" when building for customers; you can improve the product much more quickly when directly targeting a small userbase than when trying to please a large one.