Excellent points about CAD & GUI. That's a very interesting and complex area given all the different UI modality options: light-pen, tablet, mouse, touchscreen, haptics, function keypad, and keyboard. At some level, the UI designer must conform to the demands of the engineer. And yet innovations in UI can mean that sometimes the engineer benefits from conforming to the UI technology. Customer & code must co-evolve. Too many requirements documents hardcode obsolete practices.
The biggest Sapir-Worf issue here is that there are zero parallel verbal human languages. They are all sequential which makes discussions of requirements, data flows, tasks, etc. inherently expressed in sequential terms. As big an issue as differing vocabularies might seem, differences in baseline grammar and structure are much worse.
Talking to the customer is likely to create sequential pseudocode (i.e., hard to parallelize) with the added problem that the customer has no clue about the potential permutations in the process (inputs, intermediates, or outputs) that could conceivably arise (see Therac-25 for a lethal example of this). I wonder how many race conditions occur because neither the customer nor the programmer were even aware that there was second runner on the track.