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:
https://www.youtube.com/watch?v=t705r8ICkRw

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

(From Youtube)