I’m noticing more and more that there are systems on the web, and we’ve even built some of them, that are designed to save us from ourselves. The particular system I’m talking about is made to retain information that a user has technically deleted, on the off chance that they didn’t mean to actually delete the information.
This is bad training.
I understand that in some cases there is a need to hold on to this information because to recreate it would be much more difficult than just storing it for future reactivation, and in these cases, the user should be told that is the case. But the problem arises when enough of these types of systems are built for easily recreated information, without notification, that people begin to expect it everywhere. And expectation of use is an extremely frustrating thing for both us as developers, and for our clients who run the sites we develop.
We recently had this happen with a client of ours. They had user accounts on their site which allowed the user to delete their own account if they wanted to. Well, someone deleted their account, then called back some time later and asked to reinstate it. Apparently this user got fairly upset when they found out their account was actually gone.
I’m curious about what he thought “delete” meant.
There’s also the other side of this issue, in that if I delete sensitive information on a site, I want to be comfortable in the knowledge that the company behind that site isn’t actually keeping my information. I want to know that my actions have consequences.
I think people get trained in processes, and expectation plants itself, pretty quickly (consider this; how many people do you know who double click on web page links?). Because of this, we have to think about the more complex automatic processes we put in to place on our web sites, and when we do, be sure to inform the user about what is happening behind the scenes. Because as a user, that’s one thing that I think it’s OK to expect.