Unfortunately, that's not always good for the user. There are things I do like once a year; update my drivers license online, for example. If the web site is

Unfortunately, that's not always good for the user. There are things I do like once a year; update my drivers license online, for example. If the web site is "good enough" and never updated, then great, I know how long it will take and what steps to take--I may even have automated most of it. If they change the website every 6 months with wiz-bang features I have to relearn it, I have no idea how long it'll take, and it may not even work. A web service is kind of a bad example since it require managing a backend. To my parents, opening a spreadsheet or listening to music is the same. They lack the lexicon to discover newer interface trends like the hamburger icon, or ribbon interface. Many people used IE6 because there was a huge investment in it. I agree it was terrible to support and write against, but I don't see any problem with using a payroll system that was written 10 years ago and dependant on IE6 if your needs haven't changed. It seems silly to constantly update or completely rewrite something that's working just fine if needs haven't changed. It just sucks that they would use the same browser for payroll as they do for browsing the Internet.