Funware is only fun if people understand what the hell is going on. How hard is it to confuse people by putting a game where they weren’t expecting a game? Well, it depends on the user experience… and sometimes users are more easily confused than you ever imagined.
This post will explain the potential usability problems if you add funware to your existing user experience, and what types of users are most likely to be impacted (hint: it’s not the dumb-as-dirt minority you are probably scoffing at already). In the conclusion, I’ll give 4 actionable tips to improve the usability of your funware (and drastically lower the chance that your funware will drive users to drive their tech support staff crazy).
“I Have the Pac-Man Game and I Want to Disable That?”
Have you heard the audio recording of a tech support call resulting from Google’s super-cute interactive Pac-Man logo? This poor woman uses Google for productivity and instead she found a noisy game on the Google search page, so she called tech support to try to get the game removed.
Awkwardness ensues, but the tech support hero helps her work through the problem (which is mainly that the game sounds are still audible while she is trying to do other stuff in her browser, the way she probably does every day). If you’re a good software designer you are going “oh that’s a problem, hm… how could they have avoided this issue” but if you’re a less user-focused software designer you’re thinking “what a dumbass, there were several ways for her to work around this without calling tech support.”
If you’re in the latter camp, you need to go work in tech support for a while. Seriously, it is boring and repetitive and you rarely get to solve any interesting problems but you can’t design good software unless you understand what it’s like to be a “pure user” with no idea how to troubleshoot or work around a software experience that doesn’t match your mental model. Continue reading N00b Proof Your Funware. Tech Support Will Thank You.