Elon Musk Automation Quotes

One of the biggest mistakes we made was trying to automate things that are super easy for a person to do, but super hard for a robot to do.

Musk took responsibility for the over-automation. He even announced it publicly. “Excessive automation at Tesla was a mistake,” he tweeted. “To be precise, my mistake. Humans are underrated.

1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out.

Always wait until the end of designing a process—after you have questioned all the requirements and deleted unnecessary parts—before you introduce automation.

With automation comes abundance.

a way to get around the country’s rigid labor laws that limit the hours employees can work, by automating a metal stamping factory so that it could run twenty-four hours per day instead of sixteen hours like the factories of rivals.

Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out.

5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out.

On one weekend, they marched through the factory painting marks on machinery to be jettisoned. “We put a hole in the side of the building just to remove all that equipment,” Musk says. The experience became a lesson that would become part of Musk’s production algorithm. Always wait until the end of designing a process—after you have questioned all the requirements and deleted unnecessary parts—before you introduce automation.

THE RIVE BROTHERS used to be like a technology gang. In the late 1990s, they would jump on skateboards and zip around the streets of Santa Cruz, knocking on the doors of businesses and asking if they needed any help managing their computing systems. The young men, who had all grown up in South Africa with their cousin Elon Musk, soon decided there must be an easier way to hawk their technology smarts than going door-to-door. They wrote some software that allowed them to take control of their clients’ systems from afar and to automate many of the standard tasks that companies required, such as installing updates for applications. The software became the basis of a new company called Everdream, and the brothers promoted their technology in some compelling ways.

2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out.

1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out. The algorithm was sometimes accompanied by a few corollaries, among them: All technical managers must have hands-on experience. For example, managers of software teams must spend at least 20% of their time coding. Solar roof managers must spend time on the roofs doing installations. Otherwise, they are like a cavalry leader who can’t ride a horse or a general who can’t use a sword. Comradery is dangerous. It makes it hard for people to challenge each other’s work. There is a tendency to not want to throw a colleague under the bus. That needs to be avoided. It’s OK to be wrong. Just don’t be confident and wrong. Never ask your troops to do something you’re not willing to do. Whenever there are problems to solve, don’t just meet with your managers. Do a skip level, where you meet with the level right below your managers. When hiring, look for people with the right attitude. Skills can be taught. Attitude changes require a brain transplant. A maniacal sense of urgency is our operating principle. The only rules are the ones dictated by the laws of physics. Everything else is a recommendation

five commandments: 1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out.

Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out. The algorithm was sometimes accompanied by a few corollaries, among them: All technical managers must have hands-on experience.

five commandments: 1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out. The algorithm was sometimes accompanied by a few corollaries, among them: All technical managers must have hands-on experience. For example, managers of software teams must spend at least 20% of their time coding. Solar roof managers must spend time on the roofs doing installations. Otherwise, they are like a cavalry leader who can’t ride a horse or a general who can’t use a sword. Comradery is dangerous. It makes it hard for people to challenge each other’s work. There is a tendency to not want to throw a colleague under the bus. That needs to be avoided. It’s OK to be wrong. Just don’t be confident and wrong. Never ask your troops to do something you’re not willing to do. Whenever there are problems to solve, don’t just meet with your managers. Do a skip level, where you meet with the level right below your managers. When hiring, look for people with the right attitude. Skills can be taught. Attitude changes require a brain transplant. A maniacal sense of urgency is our operating principle.

Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out. The algorithm was sometimes accompanied by a few corollaries, among them: All technical managers must have hands-on experience. For example, managers of software teams must spend at least 20% of their time coding. Solar roof managers must spend time on the roofs doing installations. Otherwise, they are like a cavalry leader who can’t ride a horse or a general who can’t use a sword. Comradery is dangerous. It makes it hard for people to challenge each other’s work. There is a tendency to not want to throw a colleague under the bus. That needs to be avoided. It’s OK to be wrong. Just don’t be confident and wrong. Never ask your troops to do something you’re not willing to do. Whenever there are problems to solve, don’t just meet with your managers. Do a skip level, where you meet with the level right below your managers. When hiring, look for people with the right attitude. Skills can be taught. Attitude changes require a brain transplant. A maniacal sense of urgency is our operating principle. The only rules are the ones dictated by the laws of physics.

Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out. The algorithm was sometimes accompanied by a few corollaries, among them: All technical managers must have hands-on experience. For example, managers of software teams must spend at least 20% of their time coding. Solar roof managers must spend time on the roofs doing installations. Otherwise, they are like a cavalry leader who can’t ride a horse or a general who can’t use a sword. Comradery is dangerous. It makes it hard for people to challenge each other’s work. There is a tendency to not want to throw a colleague under the bus. That needs to be avoided. It’s OK to be wrong. Just don’t be confident and wrong. Never ask your troops to do something you’re not willing to do. Whenever there are problems to solve, don’t just meet with your managers. Do a skip level, where you meet with the level right below your managers. When hiring, look for people with the right attitude. Skills can be taught. Attitude changes require a brain transplant. A maniacal sense of urgency is our operating principle. The only rules are the ones dictated by the laws of physics. Everything else is a recommendation.

I became a broken record on the algorithm,” Musk says. “But I think it’s helpful to say it to an annoying degree.” It had five commandments: 1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify and optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out. The algorithm was sometimes accompanied by a few corollaries, among them: All technical managers must have hands-on experience. For example, managers of software teams must spend at least 20% of their time coding. Solar roof managers must spend time on the roofs doing installations. Otherwise, they are like a cavalry leader who can’t ride a horse or a general who can’t use a sword. Comradery is dangerous. It makes it hard for people to challenge each other’s work. There is a tendency to not want to throw a colleague under the bus. That needs to be avoided. It’s OK to be wrong. Just don’t be confident and wrong. Never ask your troops to do something you’re not willing to do. Whenever there are problems to solve, don’t just meet with your managers. Do a skip level, where you meet with the level right below your managers. When hiring, look for people with the right attitude. Skills can be taught. Attitude changes require a brain transplant. A maniacal sense of urgency is our operating principle. The only rules are the ones dictated by the laws of physics. Everything else is a recommendation.

the autonomous-driving side of things, Alphabet (formerly Google), which has logged several million self-driving-car test miles, continues to lead the pack. At the end of 2016, it created a new business division, called Waymo, for its autonomous driving technology. In May 2017, Waymo and Lyft announced that they would work together on developing the technology, and later in the year, Alphabet invested $1 billion in the start-up. Others, like Cruise Automation (which GM acquired for $1 billion) and Comma.ai, which offers open-source autonomous driving technology in the same vein as Google’s Android mobile operating system, are chasing hard. Baidu, China’s leading Internet search company, has an autonomous-driving research center in Sunnyvale. Byton—backed by China’s Tencent, Foxconn, and the China Harmony New Energy auto retailer group—has an office in Mountain View, as does Didi Chuxing, the Chinese ride-sharing company in which Apple invested $1 billion. Many of these companies have taken not just inspiration but also talent from Tesla. Part of the value of an innovation cluster like Silicon Valley lies in the dispersal of intellectual labor from one node to the next. For instance, PayPal is well known in the Valley for producing a number of high performers who left the company to start, join, or invest in others. The so-called PayPal Mafia includes Reid Hoffman, who founded LinkedIn; Max Levchin, whose most recent of several start-ups is the financial services company Affirm; Peter Thiel, a Facebook board member and President Trump–supporting venture capitalist who cofounded “big data” company Palantir; Jeremy Stoppelman, who started reviews site Yelp; Keith Rabois, who was chief operating officer at Square and then joined Khosla Ventures; David Sacks, who sold Yammer to Microsoft for $1.2 billion and later became CEO at Zenefits; Jawed Karim, who cofounded YouTube; and one Elon Musk.

There’s no better case study showing how connectivity and computing power will turn old products into digitized machines than Tesla, Elon Musk’s auto company. Tesla’s cult following and soaring stock price have attracted plenty of attention, but what’s less noticed is that Tesla is also a leading chip designer. The company hired star semiconductor designers like Jim Keller to build a chip specialized for its automated driving needs, which is fabricated using leading-edge technology. As early as 2014, some analysts were noting that Tesla cars “resemble a smartphone.” The company has been often compared to Apple, which also designs its own semiconductors. Like Apple’s products, Tesla’s finely tuned user experience and its seemingly effortless integration of advanced computing into a twentieth-century product—a car—are only possible because of custom-designed chips. Cars have incorporated simple chips since the 1970s. However, the spread of electric vehicles, which require specialized semiconductors to manage the power supply, coupled with increased demand for autonomous driving features foretells that the number and cost of chips in a typical car will increase substantially.