On Talent I observed something fairly early on at Apple, which I didn’t know how to explain then, but I’ve thought a lot about it since. Most things in life have a dynamic range in which [the ratio of] “average” to “best” is at most 2:1. For example, if you go to New York City and get an average taxi cab driver, versus the best taxi cab driver, you’ll probably get to your destination with the best taxi driver 30% faster. And an automobile; what’s the difference between the average car and the best? Maybe 20%? The best CD player versus the average CD player? Maybe 20%? So 2:1 is a big dynamic range for most things in life. Now, in software, and it used to be the case in hardware, the difference between the average software developer and the best is 50:1; maybe even 100:1. Very few things in life are like this, but what I was lucky enough to spend my life doing, which is software, is like this. So I’ve built a lot of my success on finding these truly gifted people, and not settling for “B” and “C” players, but really going for the “A” players. And I found something… I found that when you get enough “A” players together, when you go through the incredible work to find these “A” players, they really like working with each other. Because most have never had the chance to do that before. And they don’t work with “B” and “C” players, so it’s self-policing. They only want to hire “A” players. So you build these pockets of “A” players and it just propagates. Steve Jobs, Steve Jobs: The Lost Interview Waste as little effort as possible on low competenceA small team of committed coworkersBuild projects around motivated individualsIndividuals matter talent
Waste as little effort as possible on low competence One should waste as little effort as possible on improving areas of low competence. It takes far more energy and work to improve from incompetence to mediocrity than it takes to improve from first-rate performance to excellence. Peter F. Drucker, Managing Oneself 95%-ile isn't that goodOn Talent talent
95%-ile isn't that good An Article by Dan Luu danluu.com Reaching 95Mistakes at the top Waste as little effort as possible on low competence talent
Craft and Material in Digital Design An Article A little bit more about the stoneIt is how we come to understand our medium craftmaterialsoftware
A little bit more about the stone In the documentary Rivers and Tides, artist Andy Goldsworthy repeatedly struggles to stack stones into a sculptural cairn. Over and over the stones fall. Each time, Andy’s sculpture stands a little taller before the moment of failure. At a penultimate moment in the episode, the ever-patient Goldsworthy begins to look exasperated. He’s just staring at the rocks scattered on the ground, studying them intently. A curious passerby has watched him fail a few times, and Andy tells the man, “Every time, I learn a little bit more about the stone. I’m learning how it works.”
It is how we come to understand our medium There is such a unique quality to experiential learning, through direct experience with a material. It cannot be substituted through lectures or books. It must be felt. It must be earned through time well spent, through making and failing and re-making. It is how we come to understand our medium. If you’re a digital designer who doesn’t understand basic principles of computer science, or has never written a bit of code, or has never built a website, what are you doing? What can you say about the material you shape? The idea that designers in the information age shouldn’t waste their time with this skill baffles me. It is woefully misguided advice. A digital designer who has not learned the nature of their medium is a designer unprepared to argue for their vision. This is a designer who is unable to push back against the criticism of skeptical engineers. This is a designer who risks offering opinions instead of solutions. If you are crafting experiences in the digital space, you should know what’s required to implement your ideas. You should try implementing it yourself, (if only to build empathy with your developers!)