First impression

This book left me energized. It does not read like a biography. It reads like a set of working notes on how one person approaches enormous problems. The part that stuck with me most was first-principles thinking, the idea of breaking a problem down to its basic components instead of copying what has been done before. It is a simple idea, but seeing it applied at the scale of building rockets and cars makes it land differently.

Who should read it

This book is useful for people who want to think more clearly about hard problems, not just feel inspired by a success story. It works well if you are in engineering, product, or any field where you keep hitting the wall of "this is just how it's done." It is also useful if you are trying to build more urgency and focus into your own work.

Read this if you want practical frameworks for decision-making and problem-solving, not a step-by-step life story of Elon Musk.

How it impacted me

The main shift for me is in how I plan to approach problems at work. Instead of starting from what already exists or what a competitor does, I want to start by asking what the problem actually requires, stripped of assumptions.

I have not applied this yet, but the plan is to use it on a recurring problem in my work where the current process feels slow or overcomplicated. The idea is to question each step, remove what is not necessary, and only then look at making it faster or automating it.

Quotes and highlights

I did not save any highlights while reading this one, so this section is thin for now. Two ideas from the book stood out enough to note here:

First-principles thinking Break a problem down to its basic parts and reason up from there, instead of assuming the usual way of doing things is correct. This matters because it opens up solutions that copying an existing approach would never reveal.

The Algorithm A sequence for improving any process: question the requirement, remove unnecessary steps, simplify what remains, then speed it up, and only automate at the end. This matters because it stops people from automating a broken process and making the mess faster.

Summary and actionable notes

The book focuses less on Musk's biography and more on how he approaches problems and work. Two ideas carry most of the weight.

First-principles thinking Most people reason by analogy, copying what others have done. The book argues for breaking a problem into its fundamental parts, questioning each assumption, and building the solution back up from there.

Try this: pick one recurring problem or cost in your work. List every assumption behind the current approach. Ask which of those assumptions are actually true, and which are just habit.

The Algorithm A five-step process for improving how something gets done:

• Question every requirement. Ask why it exists and who asked for it.

• Delete any part that is not necessary, even if it feels safer to keep.

• Simplify what is left before trying to speed it up.

• Only then increase speed.

• Automate as the last step, once the process is lean.

Try this: apply the five steps to one small workflow this week. Resist the urge to jump straight to automation.

Purpose and intensity The book frames sustained focus on a meaningful goal as a driver of output, more than talent or luck. This is harder to turn into a single action, but it is worth sitting with when picking what to focus on next.