Elon Musk Attitude Quotes

When hiring, look for people with the right attitude. Skills can be taught. Attitude changes require a brain transplant.

When hiring or promoting, Musk made a point of prioritizing attitude over résumé skills. And his definition of a good attitude was a desire to work maniacally hard.

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.

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. On the assembly line

for five hours. When he finally got in to see Musk at 8 p.m., Dontchev took the opportunity to unload about how his gung-ho approach wasn’t valued at Boeing. When hiring or promoting, Musk made a point of prioritizing attitude over résumé skills. And his definition of a good attitude was a desire to work maniacally hard. Musk hired Dontchev on the spot.

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.

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

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 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. On the assembly line

Dontchev was born in Bulgaria and emigrated to America as a young kid when his father, a mathematician, took a job at the University of Michigan. He got an undergraduate and graduate degree in aerospace engineering, which led to what he thought was his dream opportunity: an internship at Boeing. But he quickly became disenchanted and decided to visit a friend who was working at SpaceX. “I will never forget walking the floor that day,” he says. “All the young engineers working their asses off and wearing T-shirts and sporting tattoos and being really badass about getting things done. I thought, ‘These are my people.’ It was nothing like the buttoned-up deadly vibe at Boeing.” That summer, he made a presentation to a VP at Boeing about how SpaceX was enabling the younger engineers to innovate. “If Boeing doesn’t change,” he said, “you’re going to lose out on the top talent.” The VP replied that Boeing was not looking for disrupters. “Maybe we want the people who aren’t the best, but who will stick around longer.” Dontchev quit. At a conference in Utah, he went to a party thrown by SpaceX and, after a couple of drinks, worked up the nerve to corner Gwynne Shotwell. He pulled a crumpled résumé out of his pocket and showed her a picture of the satellite hardware he had worked on. “I can make things happen,” he told her. Shotwell was amused. “Anyone who is brave enough to come up to me with a crumpled-up résumé might be a good candidate,” she said. She invited him to SpaceX for interviews. He was scheduled to see Musk, who was still interviewing every engineer hired, at 3 p.m. As usual, Musk got backed up, and Dontchev was told he would have to come back another day. Instead, Dontchev sat outside Musk’s cubicle for five hours. When he finally got in to see Musk at 8 p.m., Dontchev took the opportunity to unload about how his gung-ho approach wasn’t valued at Boeing. When hiring or promoting, Musk made a point of prioritizing attitude over résumé skills. And his definition of a good attitude was a desire to work maniacally hard. Musk hired Dontchev on the spot.

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.

Quite often, the Tesla engineers brought their Silicon Valley attitude to the automakers’ traditional stomping grounds. There’s a break and traction testing track in northern Sweden near the Arctic Circle where cars get tuned on large plains of ice. It would be standard to run the car for three days or so, get the data, and return to company headquarters for many weeks of meetings about how to adjust the car. The whole process of tuning a car can take the entire winter. Tesla, by contrast, sent its engineers along with the Roadsters being tested and had them analyze the data on the spot. When something needed to be tweaked, the engineers would rewrite some code and send the car back on the ice. “BMW would need to have a confab between three or four companies that would all blame each other for the problem,” Tarpenning said. “We just fixed it ourselves.

Musk still tended to drive the young engineers mad with his work demands and blunt criticism. “I remember being in a meeting once brainstorming about a new product—a new-car site,” said Doris Downes, the creative director at Zip2. “Someone complained about a technical change that we wanted being impossible. Elon turned and said, ‘I don’t really give a damn what you think,’ and walked out of the meeting. For Elon, the word no does not exist, and he expects that attitude from everyone around him.” Periodically, Musk let loose on the more senior executives as well. “You would see people come out of the meetings with this disgusted look on their face,” Mohr, the salesman, said. “You don’t get to where Elon is now by always being a nice guy, and he was just so driven and sure of himself.