Then, the exercise is repeated [...] until everyone’s responses are approximately the same
In the real world, if the client wants X, it does not matter that ALL the engineers agree that the statement really says Y. Doubly so since engineers and clients often seem to speak two different languages.
It’s far more useful to learn what the CLIENT wants, not what all the engineers THINK she wants. In fact, learning how to come to this sort of false conclusion seems exactly opposite of what Eliezer wants to teach—you now have a group of engineers convinced that they know what this overly-general statement means, despite never having checked back in with the client!
… of course, for a twist, do this, and then tell them that they’re WRONG and the client actually wanted X. Punish them for not thinking to go and actually consult the client. It produces frustration and ill-will (the presenter has just tricked them), but with a receptive audience you do potentially teach a very potent lesson.
In the real world, if the client wants X, it does not matter that ALL the engineers agree that the statement really says Y. Doubly so since engineers and clients often seem to speak two different languages.
It’s far more useful to learn what the CLIENT wants, not what all the engineers THINK she wants. In fact, learning how to come to this sort of false conclusion seems exactly opposite of what Eliezer wants to teach—you now have a group of engineers convinced that they know what this overly-general statement means, despite never having checked back in with the client!
… of course, for a twist, do this, and then tell them that they’re WRONG and the client actually wanted X. Punish them for not thinking to go and actually consult the client. It produces frustration and ill-will (the presenter has just tricked them), but with a receptive audience you do potentially teach a very potent lesson.