3 ms·
Great advice, except for: > Explicitly focus on "we" when the error is caused by an issue on your end The “we” language tends to create a distance between the
by layer8 4y ago
Great advice, except for:
> Explicitly focus on "we" when the error is caused by an issue on your end
The “we” language tends to create a distance between the user and the software, emphasizing that the user is at the mercy of an anonymous “we” (who seem to be in numerical superiority, to boot) that are in control of the software instead of the user, who is implied to lack agency in comparison. This can make users feel patronized and pushed into a passive, dependent, and ultimately powerless role.
Microsoft is particularly egregious in this, in messages like “We’re setting a few things up for you”, implying the user is not supposed to be in control of what is being set up for them, like they’re a child, and not even deemed worthy to be informed about what specifically is being set up.
- rozenmd 4y agoI think you're conflating two different things. In an error message on the Internet, "You broke our server" vs "Our server doesn't know how to respond to your input, our bad" is not a power play, it's a bad error message. Knowing who caused the issue helps the user figure out what to do next. 401/403? Better login/better annoy my boss for access. 5xx? Oh their server's broken, I'll try again later.
- layer8 4y agoThere is no need to insert a “we” group here. The user isn’t interested that it is “our” server. The user doesn’t think in terms of there being people behind the service. He/she is using the service, period. Introducing a group of other people only sets up an inappropriate social dynamics. It feels like the developers are self-inserting themselves into an interaction that is really only between the user and the service. Imagine you are using a ticket machine at the train station, the machine happens to malfunction, and it displays “sorry, our ticket machine is broken”. That is just weird, because the user is only interacting with the ticket machine, not with people operating the machine. It’s not like you’re at the restaurant and the waiter is saying “sorry, our credit card terminal is broken” (which would be an appropriate situation to say something like that). Rather, the ticket machine should display something along the lines of “System malfunction, please retry after pressing the red button. Apologies for the inconvenience.” And similar in the case of a server software.
- hamdouni 4y agoWe can use "I" then. "404 I don't find your page" "501 I'm broken"
- rozenmd 4y agoAh, I see
- rhn_mk1 4y agoThat the user doesn't think in terms of there being people is not a good thing. Compare "sorry, our ticket machine is broken" to the impersonal "System malfunction, please retry". The impersonal version waves any responsibility of the malfuction away. Was it the user? Was it the machine? Was it the machine's owner? Nobody knows. With "our machine", there's a clear message sent about the accountability of the situation: there is someone owning the machine, and they failed to provide you service. Ideally, there would be contact information, so that the user has the ability to influence their surroundings. A machine is not a law of nature, and should not be treated as such. Heck, a law of nature which gets in the way - a fallen tree, a stray stone - can usually be fixed/moved/destroyed without fear about civil liability. A malfunctioning machine will ruin your day without you being able to do anything about it.
- layer8 4y agoThat a machine or a service has an owner is self-evident, and I’m all for providing contact information or whatever for the entity behind it. This gives the user the choice of whether they want to enter into communication with them. But I don’t want them to speak to me through the machine or tool. As already mentioned, it’s like they are self-inserting themselves into the interaction the user has with the tool. It makes the use of the tool less intimate for the user, because suddenly there’s a third party mediating that interaction. It can feel like intruding into the user’s privacy and autonomy. In the Microsoft/Windows case, it certainly often feels like that. It’s bad enough for users when they don’t own the tool (as they would in case of a purchased local software) and only have temporary permission to use it, but they still like to think “this is my tool I’m using”, e.g. this is my Dropbox or my Google Sheet or my video game. A third party speaking through it however breaks that illusion, as it clearly brings the awareness of who’s really in control. The other thing is that the user knows that it’s just a stock message, in which case any emotional expression put into it can feel disingenuous.
- kqr 4y agoI agree. "We" should be reserved for someone in collaboration with the user. "Our" service is not down unless the user is part of the group that actually owns and maintains the service. "The" service may be down however, or better yet, "RetroEncabulator is down for maintenance".