Another good article, thanks Tony.
In my experience you can not sell the need for more "intellectual effort" on a job unless there are clear practical consequences to not makiing the investment.
The signs are all there in most solutions derived from poor models: excessive and convulted code, data anomalies, inaccurate reports/output, application crashes due to incorrect data, etc. , but few stakeholders in these projects recognize them for what they are.
How about a list of the signs and symptoms correlated with the typical modeling flaws that are the root cause? This is the kind of thing that gets management attention as they are very aware of the pain they have been suffering, they just often have no clue as to why...