OzExpat, err.. yes, … thus clarifying my previous post.
My lighthearted comment on your thoughts was to identify the issue with all cognitive processes and not just that of speech; hence, my later points about discipline and managing attention.
I fully agree with your point that only the deviations should be called and not the normal, although there may be justifiable exceptions – see below. One problem for the industry is that due to training / experience weaknesses, ‘normal’ may not be well understood or even known at all.
In this regard, the last part of my post might have been clearer if I had described the current short term fixes as being deficient by not referring to the normal value, although it appears that many of the ‘new’ calls appear to be attention triggers as opposed to crosschecks.
Thus while ‘quick-fixes’ might defend against weak training / experience, but they do not replace the much need specific checks of critical operating parameters, e.g. instead of ‘power set’ during take off, the call should be ‘Power Set xx% (EPR)’ which refreshes memory of the normal (for the low experienced), and enables comparison with the normal or what is expected (for the more experienced pilot), and thus is an excellent error check. Calling airspeed before flap extension in a modern aircraft would be superfluous for a well trained and experienced crew, but cognitive (situation) awareness of speed is still essential.
Similarly, a deviation call should provide additional information as well as being an attention trigger, e.g. “engine 2, high TGT, 860, increasing” - system alert, parameter, value, trend.