The Goal of This Post

This post shares some of my favorite passages and ideas from The Book of Elon by Eric Jorgenson.

It’s a compact guide to Elon Musk’s philosophy of company building—centered on frontline leadership, engineering rigor, talent density, simplicity, and a relentless drive to make things work better. More than a biography, it’s a collection of mental models for building strong teams, reducing friction, encouraging innovation, and creating organizations capable of doing difficult, meaningful work.

—

Frontline Leadership

• The troops fight harder if they see the general on the front lines.
• Get out there on the front line. Show them that you care.
• Never ask your troops to do something you’re not willing to do.

The separation of the workplace into “executives” and “employees” does not create a good working environment. We want to create a system of equality without artificial barriers, so someone can start as a trainee and one day lead the entire company.

• Managers should work at the forefront, in the same work environment as the entire team.
• Managers should always take care of their team before they take care of themselves.
• Always be smashing your ego. Internalize responsibility. Do whatever it takes to succeed.

A major failure mode is a high ego- to- ability ratio. If your ego- to- ability ratio gets too high, then you’ve broken the feedback loop to reality.

Eat Glass and Stare into the Abyss

• You have to feel quite compelled to start a company. You must have a high pain threshold.
• Bear in mind, the most likely outcome is failure.
• Reconcile yourself to that strong possibility, and only if you still feel compelled to, do it.

“Eating glass” means you’ve got to work on the problems the company needs you to work on, not the problems you want to work on.

Create a Culture of Builders

• You want everyone to be able to think like the chief engineer.
• They need to understand the system at a high level, well enough to know when they are making a bad optimization.
• The output of any company is the vector sum of the people within it.

If you’re able to get talented, hard- working people to join the company, work together, and have a relentless sense of perfection toward a common goal, you will end up with a great product.

Retain Only Special Forces

• I believe that’s the culture companies need to have if they’re going to become successful.
• The competitiveness of any company is a function of the most talented and driven people.
• Having a strong sense of purpose will attract the very best talent in the world.

The minimum passing grade is excellent.

Remove Organizational Boundaries

• It must be okay for people to talk directly and make the right thing happen.
• Communication should travel via the shortest path necessary to get the job done.
• Excessive use of made- up acronyms is a significant impediment to communication,

Simple, straightforward, low- ego terms are generally best.

Innovation Needs Permission to Fail

• Create an environment that fosters innovation.
• To provide support for innovation, make sure the penalty for failure is low.
• If you expect innovation, the compensation structure must reflect that. The risk- reward must favor taking bold moves.

You have to always look at the incentive structure of an organization and ask, “Is that organization properly incentivizing innovation?”

Simplicity Wins

• Simplicity both improves reliability and reduces cost.
• Simplicity comes from hundreds of little changes.
• The best part is no part. The best process is no process.

It’s a lot of little things. I look at every tiny part of each process and ask, “Is this process necessary?”

---

The Algorithm

1. Make your requirements less dumb.
2. Try very hard to delete the part or process.
3. Simplify or optimize.
4. Accelerate.
5. Automate.

How to think about this:

• The first step is to question the requirements. Otherwise you could get the perfect answer to the wrong question.
• The most common mistake of smart engineers is to optimize a thing that should not exist.
• You’re not adding deleted things back in 10 percent of the time, you’re clearly not deleting enough.
• Always wait until the end of designing a process before you introduce automation.

---

All content credit goes to the author(s). I’ve shared the bits I’ve enjoyed the most and found most useful.

Cheers, till next time! Saludos!
Alberto