They tell me I'm not a Rocket Engineer - and it's true. To think like a rocket engineer is to think very differently. So who is a rocket engineer - I bet you came up with the name Elon. Here is Elon's thought process for building rockets. Make the requirements less dumb. Question the requirements - the constraints are wrong. Especially if the requirements are given by an expert. Also all requirement need to be traceable to a person - not a department. Delete the part or the process - it's redundant or not at all needed. Remember the human bias is to add. The rocket engineer should be adding back only after first deleting and proving it must be added back (an acceptable rate of re-addition is 10%). Simplify or optimize only after steps 1 & 2. Never optimize early. Do NOT optimize the thing that shouldn't exist. Example SpaceX grid fin folding parts - they just are not needed. Excelerate cycle time. But only after 1,