Convincing users to update software
Evidently, last week was International Technology Upgrade Week, as christened by an unlikely brand-band: Skype, Adobe, Norton, and TomTom. The goal of this self-styled ITUW was to raise awareness, chiefly among consumers, about why it's important to keep software updated. The initiative armed itself with the results of a Skype-commissioned survey, the gist of which was that a large chunk of people (40%) don't (always) update their software when they're prompted to. Why? Because it's inconvenient, they don't understand how updates benefit them, and they get nervous about computer security when they see update notifications.
The good news is that of the people who do claim to update software promptly, the number one reason for their doing so was to secure themselves against viruses and hacks. Obviously, we're advocates of anything that gets the message across to users that keeping software updated is crucial for security. In honor of the week gone by, here's my own take on how companies might better convince users to update software:
- A quick (and extremely unofficial) field test of browser and software update options revealed that update options were under the "Advanced" tab as often as not. Something that everyone should know how to configure should not be buried in a section that will daunt and dissuade the average user.
- Each of the companies promoting ITUW took a different tack in explaining why users should keep their software up-to-date, and one of the common threads was the "Get cool new features!" spin. Does anyone else remember the collective moaning and groaning that accompanied The Great Facebook Timeline Push? Cool new features are exciting for early adopters and for the companies initiating said changes, but consumers on the whole are a lot more resistant to change. Reliable or better performance, in my view, makes a much more effective incentive for users to update.
- More companies have been building automatic update capability into their software and either enabling it by default or giving users a clear option to do so. One place I haven't seen this option a lot, surprisingly, is in the update notifications themselves. Letting people know right in the annoying notification that they can avoid the annoying notification = good move.
- It's both gratifying and frustrating that users don't download updates they're supposed to because they're afraid of downloading something bad. Caution is good; lack of knowledge driving that caution is a problem. Reliable communications –clear language, simple explanations, predictable frequency –can go a long way toward building trust here. As for methodology, I'll just say it: Pop-up notifications seem hopelessly outdated to me. They're frequently aped by bad actors, they're annoying, and they aren't self-contained (the actual update usually occurs outside the notification). In other words, they don't inspire trust. In an increasingly app-centric digital world, it's becoming easier to manage software settings and permissions, centrally and in a way that users know is reliable and trustworthy. Update options and notifications shouldn't be any different.