I thought this was an absolutely masterful explanation of engineering design thinking. If I may, I would also like to add to this list another thing he mentione

I thought this was an absolutely masterful explanation of engineering design thinking. If I may, I would also like to add to this list another thing he mentioned: "each requirement must have a name attached to it." I believe he was referring to the first step. And "Name" was really "a person" as opposed to "a department." This was his way of saying DRI all the way down to each individual requirements, to force someone to be accountable for it. His example was that SpaceX interns previously listed requirements, that were later assigned to a department (e.g. avionics), and when prompted, no one in that department really knew why it was there.