Introduction: The Efficiency Trap
We’re buried in productivity hacks, agile sprints, and complex software suites, all promising a faster way to the finish line. We’re told to add, to optimize, to accelerate. But what if we’re just optimizing the unimportant and accelerating toward the wrong destination?
Elon Musk, known for tackling some of the world’s most ambitious engineering challenges, operates on a simple 5-step framework. It’s a design and problem-solving process that can be applied to almost any project or workflow. The secret to its power isn’t just in the steps themselves, but in their strict, counter-intuitive order. Following them out of sequence is the most common mistake smart people make.
1. Question Every Requirement
The first step is to challenge every assumption, specification, and constraint of a project. Every requirement should be treated as a hypothesis, not a given. The goal is to ensure the requirements themselves aren’t flawed from the outset—or, as Musk’s team would put it, to “make the requirements less dumb.”
Critically, you must attach every requirement to the specific person who created it, not a department or an anonymous entity. This creates direct accountability and makes it easier to question and modify the requirement. Surprisingly, requirements from very smart people can be the most dangerous, as they are often accepted without the scrutiny they need.
2. Delete, Delete, Delete
Once the requirements are validated, the second step is to aggressively remove any part or process that is not essential. This is not a gentle pruning; it’s a ruthless act of subtraction.
Musk advocates for an aggressive approach: if you don’t end up adding back at least 10% of what you removed later on, you didn’t delete enough. This rule serves as a powerful cognitive override, forcing teams to fight the inertia of “we’ve always done it this way” and the natural fear of removing something that feels safe. Only by culling the unnecessary can you ensure the work you’re about to do in the next step is actually valuable.
3. Simplify and Optimise
You’ve earned the right to optimize only after questioning every requirement and deleting every non-essential component. This is where the framework’s strict order becomes crucial.
The most common mistake smart engineers make is to jump directly to this step. They spend immense effort optimizing a process or a part that should not exist in the first place. By simplifying and optimizing only what has survived the first two filters, you ensure your efforts are focused on things that truly matter. This discipline is what gives you the green light to finally hit the accelerator.
4. Accelerate Cycle Time
With a simplified and optimized process in place, the fourth step is to increase its speed. The goal is to make the cycle time for the remaining steps as fast as possible.
However, this step must come after the first three. Accelerating a flawed process only leads to producing bad outcomes more quickly. As Musk memorably puts it:
“If you’re digging your grave, don’t dig faster.”
5. Automate
Automation is the final step, and it should only be considered after the process has been questioned, simplified, and accelerated. Automating a process too early is a recipe for disaster because it solidifies any existing flaws and locks in waste.
Musk has openly admitted to making this mistake in the early days at Tesla’s Nevada and Fremont factories. The team wasted significant time and resources automating processes and steps that were later deemed unnecessary and were deleted entirely. Automation comes last, and not a moment sooner.
Conclusion: Rethink Your Process
The power of this framework lies not in the novelty of its individual steps, but in its rigid sequence. By embracing this brutally simple and counter-intuitive sequence, you solve problems at their root cause rather than patching symptoms. You avoid the single most expensive mistake in any business: brilliantly engineering a product, or a process, that should have been deleted.