{"id":11590,"date":"2023-11-26T14:39:13","date_gmt":"2023-11-26T04:39:13","guid":{"rendered":"https:\/\/nsrd.info\/blog\/?p=11590"},"modified":"2023-11-26T14:39:15","modified_gmt":"2023-11-26T04:39:15","slug":"nagifications-as-a-lesson-in-user-experience","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2023\/11\/26\/nagifications-as-a-lesson-in-user-experience\/","title":{"rendered":"Nagifications as a Lesson in User Experience"},"content":{"rendered":"\n

One of the things I’ve learned as a product manager \u2013 particularly given a lot of my focus is on user experience (UX) \u2013\u00a0is that it’s not sufficient to consider an action or activity as either a one-off, or in isolation. Yes, an activity should, by itself, be easy to perform, relatively satisfying (or at the minimum, not a negative experience), and fit for purpose. But the actions we do with a system \u2013 the interactions we have with it \u2013 should be evaluated in the context of all<\/em> our interactions with that system, too.<\/p>\n\n\n\n

The motto for this of course is: “death by a thousand paper cuts”. Something that might be useful when evaluated only<\/em> by itself, but when evaluated against all the other mildly irritating things<\/em> across an entire system though, it might be seen as something quite different.<\/p>\n\n\n\n

And there’s no-where more obvious for this than notifications on smart phones, tablets and wearables \u2013 because as soon as you build up a few applications that generate notifications, you end up with a system that generates nagifications<\/em>. What’s a nagification? It’s a notification that you either don’t need or in some other way feels more like you’re being pestered than prompted.<\/p>\n\n\n\n

In that, nagifications are an emergent property<\/strong><\/a> of a system that supports notifications: the individual notifications, taken on their own might indeed do their job at keeping you up to date for their specific application, but when they synergistically combine the emergent property of the system overall can be very different; what had been a delighter<\/em> becomes an annoyer<\/em>.<\/p>\n\n\n\n

Another thing that springs to mind is prisoner’s dilemma, but not the classic variety where it’s just two prisoners. This is like the flying-in-economy variety where all you need is a few inconsiderate people putting their chairs back all the way and everyone is stuck in an uncomfortable position; but instead it’s all about app makers thinking it’s OK for them<\/em> to abuse notifications because What They Are Sending Is Very Important<\/em>.<\/p>\n\n\n\n

Some applications are well behaved, of course. Increasingly though it seems these applications are in the minority. Some are particularly misbehaved. Uber springs to mind on this \u2013 if you have Uber Eats and Uber on your phone (as a user, not a driver\/delivery agent) you can sometimes get 6 or more notifications in a day. But they’re not notifications for actions you triggered; no, notifications for Uber are just a form of advertising: “Hey, got the munchies?” asks Uber Eats. “Special fares now”, advises Uber. “Saturday night’s a great night for going out!” says Uber, while Uber eats wants you to know that Saturday night is a great night for staying in and ordering from that restaurant whose menu you perused in the app 9 weeks ago. And so to escape being nagged, you turn off notifications entirely for Uber and Uber Eats except for when you actually<\/em> use them. If then.<\/p>\n\n\n\n

Social Media of course is the other Big Vomiter of nagifications. Facebook, Instagram, etc., love the option to pepper you with notifications; it’s ironic with Facebook for instance that you can turn notifications for Messenger off (because why would you want to get notifications on every<\/em> device?), but then have the notifications routed through regular Facebook because That Might Be Something You Really Need To See<\/em>.<\/p>\n\n\n\n

And don’t get me started on LinkedIn. (Yes, I know I’m veering into Old Man Shouts at Cloud<\/em> territory here, but LinkedIn deserves to be kicked in the posterior.) LinkedIn will always<\/em> find another reason to message you. It starts innocuously, of course. “Your connection just posted about getting a new job”, or “A connection commented on your post”. Phew. All seemingly normal and apropos of the sorts of notifications you might want from a professional networking service. But then the random stuff starts sneaking in too. “Someone you’re not connected to posted an article you might like to read”, “Someone you’re not connected to commented on a post made by someone else you’re not connected to”, or “There’s a janitorial position available in Ulaanbaatar that we think you might be interested in based on a job advertisement you weren’t interested in for a role that doesn’t match anything in your profile but you accidentally opened when we sent you a notification three weeks ago”. <\/p>\n\n\n\n

Such is LinkedIn’s pernicious and histrionic need for keeping you engaged that they’ve become a nagification engine all on their own. You can see just how ridiculous they’ve become by perusing Settings & Privacy > Notifications <\/strong>under your LinkedIn account. <\/p>\n\n\n\n

\"LinkedIn<\/a>
LinkedIn Notifications Episode One: The Phantom Privacy<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

But these are only the categories<\/em> under which notification settings are provided, not the actual notification options themselves. Each category leads to its own maze of other notification options:<\/p>\n\n\n\n

\"LinkedIn<\/a>
LinkedIn Notifications Episode Two: Attack of the Clowns<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

And it just goes on and on and on:<\/p>\n\n\n\n

\"LinkedIn<\/a>
LinkedIn Notifications Episode Seven Thousand One Hundred and Forty Five: The Farce Awakens<\/em><\/strong><\/figcaption><\/figure>\n\n\n\n

Left to its own devices, LinkedIn will find a way to notify you of Things You Should Know About<\/em> many times a day. Ironically for a professional network, regardless of whether that interrupts your work or not. I’ve seen less naggy behaviour from four year olds that spent all afternoon at a birthday party eating red lollies and cake non-stop.<\/p>\n\n\n\n

You might hope that the device vendors are on your side, but not fully<\/em>. Of course, both let you edit<\/em> your notification settings, but Google’s Android lets apps turn on notifications without checking with you first, even while giving you a Do Not Disturb option. Apple’s iOS\/iPadOS will let you define different Focus<\/em> times where you can choose which app notifications get through, but Hey Did You Know That Apple TV+ Just Released A New Movie Featuring An Actor You Don’t Like But It Cost A Bucket To Produce<\/em>? And heaven forbid if you’re on your longest move goal streak and the end of the week coincides with the end of the month. Bzzt, Apple Watch wants you to know you closed your Move ring today. And Apple Watch wants you to know that you’ve closed your Move ring every day this week. And Apple Watch wants you to know that you’ve closed your Move ring every day this month. And Apple Watch wants you to know that you’ve closed your Move ring for 1,075 days in a row. And Apple Watch wants you to know that you closed your Exercise ring today. And … well, you get the picture. These will generally be stacked (one interruption, multiple notifications), but even so, we’ve gone from delighter <\/em>to annoyer<\/em>. <\/p>\n\n\n\n

And returning to my stated risk of becoming Old Man Shouts at Cloud<\/em>, I know that you can tailor the notifications for every app; and yes, you can use options like Focus mode to give yourself a break, but you also have to sometimes stop and wonder about something that was initially heralded as being such a useful feature \u2013 when can still <\/em>be a useful feature when evaluated instance by isolated instance \u2013 has cascaded into such a potent, interruptive nagging function.<\/p>\n\n\n\t

\n\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t