Elon Musk's 5 step process for making things in a better way
Vložit
- čas přidán 10. 09. 2024
- This video is an extract for educational purposes from a great interview with Elon Musk by Everyday Astronaut. Watching the entire multi-hour tour of SpaceX's Starbase is recommended. You can find the first episode on Everyday Astronaut's channel here:
• Starbase Tour with Elo...
This video is an extract for product managers, service designers and others people who make hardware, software or both. It might be good general life advice too!
The 5 step process for handling requirements when making things, according to a man who gets a lot of things done and learns from his mistakes (including the Cybertruck window smash, which he's wearing an image of on his t-shirt during the interview).
1. Make your requirements less dumb
- Your requirements are definitely dumb
- Its particularly dangerous if a smart person gave them to you as you might not question them enough
2. Delete the part or process
- If you're not adding back then you're not deleting enough
- Don't add requirements just in case, don't hedge your bets
3. Simplify/Optimise
- Don't optimise if it shouldn't exist
4. Accelerate cycle times
- But don't go faster if you haven't worked on the other 3 things first...
- If you're digging your grave don't dig your grave faster
5. Automate
- Don't reverse these 5 steps
Love the chaos honestly, feels like a real convo with a friend in the middle of work instead of a cold stale interview on tv
What chaos?
@@IAn0nI background noise
@@caviersim3806 that's not noise, that's the sound of awesomeness
1. Make your requirements less dumb
2. Delete as much of the process as possible (test the borders/trim the fat to get rid of unnecessary parts)
3. Simplify/optimize
4. Accelerate cycletime (go faster)
5. Automate
1:30 “the most common error of a smart engineer is to optimize the thing that should not exist.”
@@Hejirah For example, Trying to make a car with three or five wheels is dumb and shouldn't exist since 4 wheels are safer, tested, and work all the time.
@@mr_dareah gotcha
@@mr_darethats a very trivial example
@@mr_dareits not really like that example at all
Thank you for including the paraphrased quote at the end!! ❤
Whomever interviewed him on this day, when he was wearing this exact shirt. Asked the best questions bar none.
I listen to this every morning, it's a bit silly since it becomes gospel to me. Anyway, the first step, to question the requirements, is, as he says, harder if a smart person made the requirements. I want to add, that if you, yourself, aren't smart enough, when asking this smart person, it's not possible to question the requirements enough. It's impossible unless you educate yourself to understand on a deeper level. Imagine getting the requirement from a smart person, that you have to use a cylindrical chair when making a time machine. How could you question this enough? You'd have do question in a manner so deep, that the smart person has to educate you on how it works. Otherwise, you will have requirements that you don't know if they should be there, you just trust the smart person and build on top of it.
The requirement to use "cylindrical chair when making a time machine" is given to the person who is likely going to implement it, so a peer also expert in the domain or related. They don't hand it to say, a woodworker or a marine biologist !
Thanks for this video - it's worth gold
1 make your requirements less dumb
2 delete as much of the process as possible
3 simplify/optimize
4 accelerate cycletime (go faster)
5 automate
good video + summary at end, thanks
All starts ups need to watch this video. Primary focus on cycle times is simply foolish if core DESIGN and PROCESS issues are ignored!!!
sorry for asking (I am somewhat dumb), but what cycles? cycles of what?
@@Hejirah One cycle is one run through of the process. So if you’re making something a cycle time is how long it takes you to make that thing.
Awesome, great advice, was looking for someone to make a compilation and found it. Thanks. Would be cool too also delete the background noise with some of that AI, but I'm asking too much I guess ha.
Same
Delete that requirement!
Thank you! Appreciate you transcribing
WATCHING 👀 AGAIN 🤗😎💚💚💚
Golden nuggets here, thx for this :-)
man thx this is perfect to share
He really is a beautiful person this is great.
Luar biasa salam sukses Tesla❤❤❤
Enough is enough Sir
Are they testing the killbots in the background? Those huge gunshot sounds
la fakin catedra de diseño
great video
Elon tho is gospel to me. 🥰💗
Then how does someone get a job in engineering if schools are not teaching proper engineering curriculum?
Video interessante !
One of greatest advice
Methodology
You missed about adding at least 10% back in you will bleed up…
Ulipataa ansr Orr Badi nilikuonesha kituu muhimusana itamsaidiya kufanya transport ikuwe chip
What does "Make your requirements less dumb" mean?
It means to have a plan with worthwhile, beneficial, effective, and or meaningful progress. Simply put, better inputs will equal better outputs.
Классный Илон маск
Send this to your boss
Hi mechazilla
Eu quero dólar
I wrote a scientific paper about that :)
Can you shared?
👍👍👍👍👍🙏🙏🙏🙏🙏
Meu amor me dê dólares a sua empresa
The first two steps should be swapped. Delete anything extraneous, then with what remains, evaluate whether it's sensible. Then only once you know that it's necessary and has sensible requirements, continue forward with optimization. And never automate what hasn't been optimized. Automation is just faster, not better. If you're doing something poorly, automating only stacks up more bad results in less time.
Every part added is due to requirements, and you can only delete to fit the requirements
Is this a joke?
Not at all. You just don’t understand