I will use the same advice that I used in the past when it comes to "corporate types" (as opposed to "technical types"), namely: talking about risk.
What are the risks with IE6 that they can understand?
Talk about age: IE6 was first released in August 2001. Microsoft support will end at the end of it ( if it wasn’t already ). Since then, two major versions of IE have been released, and IE9 beta was officially released last week. What are the risks of an old browser for a table? Two, as I see it: security holes and difficulties finding qualified developers to continue supporting older IE6-dependent applications.
Talk about development for yesterday's technology: IE6 does not support a number of features that other browsers do, such as Mozilla, Google Chrome and Safari. Don't talk about CSS or HTML support (as this is likely to make their eyes overlap) , but talk about the user-friendly eye sweets and features that these other browsers support, which IE6 just can't , at least not moving heaven and earth. Are the risks here? The inability to deploy more advanced third-party intranet applications (if they no longer support IE6) or the additional cost of developing workarounds for features that a more advanced browser can support (for example, an SVG or Canvas-based Gantt chart application).
Talk about standards and the risk of supplier blocking. Is your company really better by going "all Microsoft" or by moving to more modern standardized software from a more diverse set of sources - a safer approach?
Point to the general use of the Internet in IE6 compared to other browsers and talk about how most Internet savvy people already use a different browser, so the "retraining" of corporate personnel is not such a big problem as it might seem.
I suspect that if your "corporate types" come to the table with an open mind, you can sell the update to another browser, assuming that the intranet application does not support IE6.
Cal jacobson
source share