[header_button]
Most operational frameworks tell you how to do things better. Elon Musk’s algorithm starts one step earlier — by asking whether you should be doing them at all.
In an interview at Starbase and detailed in Walter Isaacson’s biography, Musk lays out the five-step process he uses to run everything from electric car production lines to rocket manufacturing. For founders inside the startup ecosystem in Canada trying to build faster with leaner teams, the order of these steps matters as much as the steps themselves.
Step 1: Make Your Requirements Less Dumb
The algorithm opens with a warning most teams aren’t expecting:
“First, make your requirements less dumb. Your requirements are definitely dumb… It’s particularly dangerous if a smart person gave you the requirements because you might not question them enough.”
From the Isaacson biography, Musk expands on what this actually means in practice:
“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.”
This is a direct challenge to how most organizations operate. Processes and requirements accumulate over time, often losing their original rationale — and the smarter the person who created them, the less likely anyone will push back. Musk’s fix is to make accountability personal: every requirement has a name attached to it, and that name is subject to questioning.
Step 2: Delete Any Part or Process You Can
Once you’ve questioned every requirement, the next step is to cut:
“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.”
This built-in benchmark — expecting to restore at least 10% of deleted items — is a useful forcing function. It signals that the goal isn’t to be reckless, but to create enough pressure on existing processes that you actually challenge whether each one needs to exist. If nothing gets added back, you probably weren’t aggressive enough in the first place.
Step 3: Simplify and Optimize
Only after requirements have been questioned and unnecessary parts removed does optimization make sense:
“A common mistake is to simplify and optimize a part or a process that should not exist.”
This is one of the most expensive mistakes a team can make: pouring energy into making something faster, cheaper, or more elegant when the correct answer was simply to remove it. Optimizing something that shouldn’t exist doesn’t improve the outcome — it just makes the waste more efficient.
Step 4: Accelerate Cycle Time
Once the foundation is right, speed becomes the lever:
“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.”
Musk is candid here about having made this exact mistake himself. Accelerating a flawed process doesn’t fix the flaw — it amplifies it.
Step 5: Automate Last
Automation closes the loop, but only once everything else is in order:
“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 instinct to automate early is understandable, especially in tech. But automating a broken process at scale is one of the fastest ways to embed a mistake permanently into a system.
The Mental Straight Jacket That Holds Most Teams Back
Musk connects the tendency to over-optimize back to how most people are trained to think:
“It’s possibly the most common error of a smart engineer to optimize a thing that should not exist. Everyone’s been trained in high school and college that you answer the question — convergent logic. You can’t tell the professor your question is dumb or you’ll get a bad grade. You have to answer the question. So everyone, without knowing, basically has this mental straight jacket on and they’ll work on optimizing the thing that should simply not exist.”
This is a cultural problem as much as a process one. Most teams reward execution over questioning — which is exactly what allows bad requirements to compound unnoticed for years.
What This Means for Startup Founders in Canada
For early-stage teams trying to move fast inside the startup ecosystem in Canada, this framework is a practical counter to the natural tendency to build momentum before building clarity:
- Start by questioning, not doing. Before optimizing any process, ask whether the requirement behind it actually makes sense.
- Name the source of every rule. Anonymous requirements don’t get challenged. Personal accountability forces honest evaluation.
- Delete before you optimize. Cutting unnecessary steps frees up more capacity than refining the ones that shouldn’t exist.
- Save automation for last. Automate processes that have already been questioned, stripped back, simplified, and proven — not the ones you hope will work themselves out at scale.
- Build this habit into your team’s culture early. Startup founders in Canada who instill a question-first mindset from the beginning avoid inheriting the same bloat that slows larger organizations down.
Why This Matters for the Startup Ecosystem in Canada 🇨🇦
As more companies look to scale startups in Canada, the temptation to move fast and automate early is stronger than ever. Musk’s algorithm is a useful reminder that speed applied to the wrong processes doesn’t create efficiency — it creates faster failure.
Founders connected to a strong startup community in Toronto and across the country can also use frameworks like this as a shared operating language for their teams, making it easier to align around what to build, what to cut, and what to leave well enough alone.
Platforms like Startup Ecosystem Canada exist to connect founders building lean, deliberate companies with the community, mentorship, and resources to do it well.
Take the Next Step
Plug into the Startup Ecosystem Canada network — tools, community, and opportunities for founders and students building in Canada.
- Join the Community — Connect with founders, operators, and investors across Canada.
- For Students — Explore student startup clubs and communities at universities nationwide.
- Discover the Network — See how we support Canadian founders at every stage, from idea to scale.
