48

Currently I'm working on a branch banking application which is going to be used for all banking transactions such as Money deposit, EFT but also Campaign Management etc. (Some user roles are directly customer centered and some are employee centered)

We are thinking of using a funny language while giving user messages (error, success & info) in CRM related transactions (Not customer centered). By CRM related I mean, there are some transactions which are related with the user's own. Creating a task, Updating a campaign and viewing a customer etc.

But I'm not sure if its a good idea. Even though they're not customer related, they are still in the same application and this could decrease the consistency of our product.

What would you advise?

Hakan Isik
  • 1,372
  • 2
  • 11
  • 10
  • 5
    Depends what you mean by "funny" but what's more important is that they are "polite, illuminating, and helpful" (How do I get users to read error messages?). – Matt Obee Aug 26 '14 at 08:53
  • Looking at the financial and banking profession it's not usually the forum for humorous elements. Coming into work with "a funny shirt" for example is not as acceptable as it would be in other professions. So I would be very careful trying to do so here. – AndroidHustle Aug 26 '14 at 08:53
  • 115
    Have you got an example of what you mean by 'funny language'? Are we talking something like "LOL, U haz no monies left"? (because I hope not) – JonW Aug 26 '14 at 09:02
  • 1
    What is your primary reason to think about using funny messages? What they help to achieve from your point of view? – Serg Aug 26 '14 at 10:01
  • 5
    Our business unit came up with the idea. They think, if we use a less formal language in messages, users will feel less stressful and feel more connected to the application. Luckily they asked us first before changing the messages. – Hakan Isik Aug 26 '14 at 11:44
  • 6
    message in jest, user under duress, program failure – jwenting Aug 26 '14 at 13:27
  • 4
    And don't forget that after you have seen a message twice it just becomes stupid rather than funny. (If not sooner). – Dennis Jaheruddin Aug 26 '14 at 13:47
  • 31
    less formal is not the same as funny. – Gusdor Aug 26 '14 at 15:18
  • They should be actionable and relevant to the user above all. What's the point of buggering a user if they can't do anything about it and the error did not affect the user's expected outcome? – Steve Dodier-Lazaro Aug 27 '14 at 09:34
  • In my answer to 'Should error messages apologize', I include a summary of a study that compared apologetic error messages to joke error messages. – Graham Herrli Aug 31 '14 at 15:21
  • However funny you think your messages will be, I can assure you they will be considerably less funny to a finance officer or IT person when they're both stuck at work at 1.30am in the morning due to a bug in your code. Or even when the same bug is causing that message to appear during the normal working day for the 300th time in one hour. Your business unit are idiots. – Rob Moir Sep 01 '14 at 07:32
  • "Everything that you say should be true, kind and helpful, and be needed now." From the book: "At The Feet Of The Master" (available for free). –  Oct 21 '16 at 17:59

11 Answers11

148

When we’re dealing with Banking and money transfer, it is an exceptionally bad idea. Finance isn’t supposed to be funny, since it’s a very serious business. Instead, error messages should be clear and to the point what is actually wrong, and not some random fun message.

When a user receives an error message, she/he is already under pressure, since users don’t want to be wrong. Making fun of them or anything else won’t help the current stress the user is in. If you want to ease the stress for the user, a fun message could be wrongly interpreted.

What you can do is to make the error message have a nice friendly tone. Instead of “Integer expected” you could type, “This field needs a number”. That way you help the user explaining what is wrong and you lower the stress of the user, which is a good thing. However, please, stay away from funny error messages.

Nicolas Barbulesco
  • 1,457
  • 10
  • 12
Benny Skogberg
  • 54,996
  • 22
  • 140
  • 241
  • 8
    Completely agree with you. For more info on what's appropriate in which situation, MailChimp's done a great job documenting it in their Voice & Tone guide. – Vince C Aug 26 '14 at 12:25
  • 3
    I think as long as the message is informational and not just funny, it should be fine. But as you said, you should be very careful with the tone of what you do. You can't do funny things all the time, even in a less stressful environment. Just pick and choose when the appropriate time is. – UXerUIer Aug 26 '14 at 13:44
  • 1
    Thank you for the answer Benny, totally agree with you. As I mentioned above, our business unit came up with the idea and luckily they consulted us before changing the messages. – Hakan Isik Aug 26 '14 at 13:49
  • 2
    @HakanIsik Thanks! "Our business unit" - let me guess... Marketing? ;-) – Benny Skogberg Aug 26 '14 at 13:54
  • 4
    I would also add that a 'funny' error message might give the impression that the site has been compromised since in finance that would appear unprofessional and out of place. Nobody wants to feel like their banking information isn't in professional hands. – leigero Aug 27 '14 at 05:28
  • 2
    I strongly agree with the sentiment that "funny" error messages would never be appropriate in a banking or finance application under any circumstance. EVER. Seriously, consider your definition of funny. I'll bet your team couldn't even agree unanimously on the definition of "funny." Will you have any foreign users who don't understand English idioms, let alone clever humor in a non-native language? Is anything funny when you're dealing with finances and errors occur? – Craig Tullis Aug 28 '14 at 07:26
  • @VinceCgto does the voice and tone site work? I've tried a couple of browsers and devices, and can't seem to navigate the links. :( – Tim FitzGerald Aug 29 '14 at 18:29
  • @Tim FitzGerald yeah, it works perfectly for me. The website is responsive, so you can even view it on your smartphone, might wanna try that. – Vince C Aug 30 '14 at 10:00
  • "This filed needs a number" might however yield frustration when the user tried to input a float in an int field... – Tobias Kienzler Sep 01 '14 at 06:42
  • 1
    Finance isn’t supposed to be funny, since it’s a very serious business. Every business is a serious business when you're "in it" (or "part of it"). Being a clown is ALSO a serious business if you rely on it for supporting your family, as is trading stamps, selling pigs, cleaning gutters. If one insists on a scale of "seriousness" then I'd say finance is mildly serious; saving lives by surgery, research and similar stuff is "serious". I do, however, agree that financial applications aren't the place for "funny messages". Sorry, customer has insufficient funds. Squeeze harder yes/no? – RobIII Sep 01 '14 at 14:04
42

I would say that you can make the error messages more personal and "human sounding" without resorting to trying to be funny.

For example, a message that says

"Error processing transaction"

can be translated to

"We are very sorry, but something went wrong."

"We are very sorry, but something went wrong and we did not send this transaction."

They key is to make the messages sound like a real person who is trying their very best to help the user.

Franchesca
  • 12,525
  • 3
  • 23
  • 36
  • 47
    +1: agreed on the concept, yet I disagree of the exact example. Once in a while my bank's site gives me a similar message and it is not reassuring at all. I do not want my bank to say something went wrong after I just clicked to, say, make a transfer. It looks like the bank has lost its grip on the situation and it is not sure of what happened with my money. I do feel entitled to worry about the bank's ability to manage my money at all...I want to be told something about the 'something' (lost connection, timeout,...) and mostly how do I get to know the status of the action that just failed –  Aug 26 '14 at 19:22
  • 5
    Agree, "something went wrong" is not helpful at all. – Ally Aug 26 '14 at 21:24
  • 10
    FWIW: In our (non-banking) app, for unforeseen errors, we use something to the effect of "We've encountered an error. Our technical staff has been notified and will be looking into it very soon." We really have been notified, and do look into it. Trying to keep it generic, but let the user know that we know about it, and that we care. For banking, I would obviously tweak the message, but you get the point. – Adrian Carr Aug 27 '14 at 02:37
  • 3
    @RolazaroAzeveires Well, yes, of course there should be additional information / reassurances in a real life example. I was just giving an example of how the rather robotic sounding "error processing transaction" message can be made to sound like a real human. – Franchesca Aug 27 '14 at 07:28
  • 1
    @Ally I agree. When it comes to finance, it is serious business. As a user, I think I would appreciate a more specific answer like "Looks like the Transaction failed. Please try again", rather than "Something went wrong.", which is too vague. – harsimranb Aug 28 '14 at 00:43
  • 1
    What do you mean "oops," doctor?! – Craig Tullis Aug 28 '14 at 07:30
  • 1
    @Pathachiever11: Except for the "Please try again" part, that message, "Looks like the transaction failed", is not any more specific than "Something went wrong". – O. R. Mapper Aug 28 '14 at 13:48
  • @O.R.Mapper: at least "looks like the transaction failed" doesn't sound like they sent money to the wrong person; "something went wrong" could read as "crap, the money went to the wrong person!" I'd rather have the former than the latter. – Cornstalks Aug 28 '14 at 13:58
  • @Cornstalks: Maybe my imagination is just too active, but I can easily read "the transaction failed" as "the transaction failed: The money was correctly taken from your account, but somehow didn't arrive at its intended destination." The same is true for vague (and possibly misleading) phrases such as "the transaction could not be completed" - uh, fine ... not completed, but started? "failed" doesn't say anything about a successful rollback. – O. R. Mapper Aug 28 '14 at 14:43
  • @O.R.Mapper To me "transaction failed" sounds like, "Ok transaction failed. The money is still there". "Something went wrong" isn't as reassuring. Like Cornstalks said, it could mean many things. On the other hand something like "Something went wrong. Don't worry, you money is safe with us." would also assure the user. – harsimranb Aug 28 '14 at 17:07
  • Even the edited one just sounds overly drawn out and intentionally unspecific. Error messages should be short and sweet, and personal when possible. You could say something like "We're sorry, there was an error processing your transaction." – Keavon Aug 29 '14 at 05:13
  • I agree with making the mesaages less technical and more human, but I really dislike the overuse of apologies. Especially using "Sorry" as a dialog title. I would prefer: Something went wrong while processing your request. Link: Contact support. Buttons: [Try again] [Cancel] (if needed, a statement of assurance can be included: No changes were made to your account. or We have ensured that your funds are safe.) – ADTC Aug 29 '14 at 11:26
  • 1
    @ADTC I think saying sorry to users is generally a good thing (accepting responsibility so the user doesn't feel it's their fault), but I also think you have a point. The problem with using it in an automated message is that it can sound insincere in some contexts. – Franchesca Aug 29 '14 at 14:01
  • 3
    @Pathachiever11: The extra sentence "Don't worry, your money is safe with us" would actually worry me more. Because apparently you have to reassure me that I can trust you, which typically is a sign that I can't. Now, something like "The money is still on your account." would be reassuring. – celtschk Aug 30 '14 at 10:32
  • @Franchesca you get the point. :) – harsimranb Aug 30 '14 at 12:30
14

"Funny" error messages in a serious (very serious!) application are likely to come across as tone-deaf at best. Also, bear in mind that an error message might be seen repeatedly. No joke is still funny when you hear it five times in succession and being presented repeatedly with the same attempt at a joke is like being stuck with any person who won't behave appropriately for the circumstances: it gets very stale, very fast.

David Richerby
  • 1,583
  • 1
  • 11
  • 13
9

I would most definitely discourage doing this and apart from the reason already mentioned by Benny, one must always consider the overall personality of brand you represent.

An average user has a certain expectations from the kind of application he is using. The definition of user experience is different for him in different types of applications and banking is not one of the fun to do types.

On a general note though, that establishments with brick and mortar presence have a significantly more pressure of presenting themselves in similar manner on both online and offline, and banking is one such domain.

Harshal
  • 3,105
  • 16
  • 23
  • 1
    term here is "corporate voice." A funny error message violates it for a bank or financial tech product. – djechlin Aug 29 '14 at 16:59
9

Without a more concrete example, let me just say... I suggest you tread lightly. This can be very dangerous.

Consider a single mother of three at the end of the week struggling to make ends meet. As she goes to pay her last bill she gets the following "funny" error message.

Whoops! I think you put in the wrong number, because that's more money than what's in the account! hihi

Beyond ruining your brand's reputation with that person, that in-your-face reminder can actually ruin that person's morale... with very real consequences.

Making human-sounding error messages isn't enough. We need empathic error messages. The systems we make lack the information (tone, facial and body language cues) we would get in a human interaction. So when there's a possibility for a delicate situation, we should err on the side of caution and use simple, sober, sympathetic and considerate messaging.

Tim FitzGerald
  • 3,471
  • 1
  • 18
  • 22