I often have problems about administrative communications, for example, emails to help you to reset your password; to update an application since I did not pass the approval etc.
There seems to be a general lack of attention to these communications, and it is very understandable, after all, they are not frequently used function nor they make money for the business. And they work anyway, maybe after several failed attempts, users find their way out (solve the problem or leave the site for good).
Nevertheless, there is a positive correlation found between sales conversion and easiness of maneuvering on a website. In Steve Krug’s book "Don't Make Me Think”, he emphasized the importance of visual clues for users to know where they are at anytime, and otherwise they may abandon your website and go for somewhere else.
You may be saying, wait a second, I read that book, there is nowhere mentioning administrative communications, it is all about navigation, articles, product detail page etc.
May be it is not such a big issue.
I would not agree with that.
The reasons are the following:
And it is not so hard to improve the experience.
I’ve summarized the key problems of administrative communication that I’ve encountered and the techniques I employ in products I’ve managed to avoid such problems:
Redundant and Irrelevant Content: I was evaluating Stormpath for the company, it provides user management and authorization services via API. By the nature of its business, I would expect they will be providing the best practices for administrative communication (I mean, password and authentication, that’s what they do right?)
So I was a bit surprised when I received a reset password from Stormpath with the following main body:
"I wander where else it can take me if it does not take me to the “change my password” page… …"
"What is rdegges.com doing here? Why is it not r@stormpath.com?"
"If I have an account and got this email by mistake, who do I contact, r@rdegges.com or support@stormpath.com?"
That is a lot of question for the 111 words in this email.
My colleague Jack heard that I am writing this article about administrative communication, he showed me his Zaiper “reset Password” email.
"Who is that someone?” I asked.
“Jack”, he answered.
The problem of redundant information is that it is distracting, it slows down users from completing the core tasks. We say too much when we are not supposed to say anything.
Information Are Not Actionable: administrative communication can be complex for merchant functions, application failed and need to be modified, work flow creation failed because it conflict with existing structure. To individuals that is working on these tasks, it can be quite stressful, especially when they can’t figure out how they can act on it.
I was trying to add Google AdSense onto my blog, my application failed and I received an email from Google on why the application was not approved.
As I read through the reason, I found I have complied with all the bullet points. And I am left with no idea what to do before I try to resubmit again.
In the end, I went to Google the question “How to Pass AdSense Application” and “Best Practices for AdSense Program”.
When a “call to Action” communication is not actionable, it is not a pleasant experience.
Inconsistency Throughout the User Journey: the most recent experience I had was with Blogger. I added my second Gmail account as a contributor to the blog. I need to send an invite to the second Gmail account and then activate the link in the email.
I did receive the invitation in the correct email, it is nice and clean. I click on “Accept Invitation”.
I click on the “Accept invitation” button on the webpage that popped up (we are not discussing why there need to be a page like this in this article).
And I was confused by why the second account was not added.
Until after several failure I finally figured out it is because Google failed to re-direct the webpage to the correct account. I am logged in on my primary Gmail account on the chrome browser and when it open the webpage, it took the primary account by default.
Maybe the problem is that companies don’t want you to have more than 1 account with them, and it uses such a way to tell me… …
As product manager, I don’t want to frustrates users when I don’t have to. And I don’t want these trivial tasks to distract them from enjoying the good content, services and products on my website and apps. To do so, I apply a 3 step approach to help me an my team
Step 1 Identify the Differences and Focus: many of such communication are standard flow, but there almost in all cases there are also unique flows. Dropbox, for example, sends me weekly update on what has been changed, but I will not expect such updates from e-commerce websites. I always start identifying what is unique because I know in these situations, I need to create the story because users can’t assume anything from their past experience. And these are also flows I make sure to test later on. While the common ones I can simply refer to the best practices.
Step 2 Find out the 5W+1H: where, when, what, why, who and how, it does not mean I need to have all of them, but I make sure I think about go through all of them and make sure nothing important is left out. Take “Reset password” email for example, I will have:
Step 3 Verify in the Context of Overall Experience: I usually take the user flow diagram and fill in the different emails, SMS and webpages at their place try to go through the flow by myself; I do think in the user test as well, especially if it is not something standard such as reset password or change mobile number. In my experience it has been a great way to optimize the experience (find what needs to be emphasized) and identify gaps (what is missing).
Adopting the 3-step approach to administrative communications helps to put things in perspective and reduce repeated works. It had worked very well for me and help it will be helpful for you as well.
Reference:
I got an email saying I requested a new password but I didn't make this request
https://www.facebook.com/help/226272054050348
Principles For Developing A Secure Password Reset System
https://www.wiredtree.com/blog/principles-developing-secure-password-reset-system/
Help to get your application approved
https://support.google.com/adsense/answer/75109
There seems to be a general lack of attention to these communications, and it is very understandable, after all, they are not frequently used function nor they make money for the business. And they work anyway, maybe after several failed attempts, users find their way out (solve the problem or leave the site for good).
Nevertheless, there is a positive correlation found between sales conversion and easiness of maneuvering on a website. In Steve Krug’s book "Don't Make Me Think”, he emphasized the importance of visual clues for users to know where they are at anytime, and otherwise they may abandon your website and go for somewhere else.
You may be saying, wait a second, I read that book, there is nowhere mentioning administrative communications, it is all about navigation, articles, product detail page etc.
May be it is not such a big issue.
I would not agree with that.
The reasons are the following:
- The majority of the communication happens in the middle of a work flow (e.g reset password; make a reservation; complete a checkout; create a new user etc), all of which are critical to the business objective (sale conversion or user on-board etc);
- Most users that get into these issues are repeated or even frequent users. To be honest, who needs “reset password” if they will shop with you once right? So these users are who you want to retain, and you don’t want to look bad in front of them;
- In some cases, it may cause errors and thus bad reputation. We don’t want to admit that we are wrong, sometime because we are wired in our brain to defend ourselves; sometimes because it hurts our ego; sometimes because it is unfair to do so. And we turn to social media to seek for revenge and support. In these cases, it creates trust and reputation issue in a much bigger community;
And it is not so hard to improve the experience.
I’ve summarized the key problems of administrative communication that I’ve encountered and the techniques I employ in products I’ve managed to avoid such problems:
Redundant and Irrelevant Content: I was evaluating Stormpath for the company, it provides user management and authorization services via API. By the nature of its business, I would expect they will be providing the best practices for administrative communication (I mean, password and authentication, that’s what they do right?)
So I was a bit surprised when I received a reset password from Stormpath with the following main body:
"I wander where else it can take me if it does not take me to the “change my password” page… …"
"What is rdegges.com doing here? Why is it not r@stormpath.com?"
"If I have an account and got this email by mistake, who do I contact, r@rdegges.com or support@stormpath.com?"
That is a lot of question for the 111 words in this email.
My colleague Jack heard that I am writing this article about administrative communication, he showed me his Zaiper “reset Password” email.
"Who is that someone?” I asked.
“Jack”, he answered.
The problem of redundant information is that it is distracting, it slows down users from completing the core tasks. We say too much when we are not supposed to say anything.
Information Are Not Actionable: administrative communication can be complex for merchant functions, application failed and need to be modified, work flow creation failed because it conflict with existing structure. To individuals that is working on these tasks, it can be quite stressful, especially when they can’t figure out how they can act on it.
I was trying to add Google AdSense onto my blog, my application failed and I received an email from Google on why the application was not approved.
As I read through the reason, I found I have complied with all the bullet points. And I am left with no idea what to do before I try to resubmit again.
In the end, I went to Google the question “How to Pass AdSense Application” and “Best Practices for AdSense Program”.
When a “call to Action” communication is not actionable, it is not a pleasant experience.
Inconsistency Throughout the User Journey: the most recent experience I had was with Blogger. I added my second Gmail account as a contributor to the blog. I need to send an invite to the second Gmail account and then activate the link in the email.
I did receive the invitation in the correct email, it is nice and clean. I click on “Accept Invitation”.
And I was confused by why the second account was not added.
Until after several failure I finally figured out it is because Google failed to re-direct the webpage to the correct account. I am logged in on my primary Gmail account on the chrome browser and when it open the webpage, it took the primary account by default.
Maybe the problem is that companies don’t want you to have more than 1 account with them, and it uses such a way to tell me… …
As product manager, I don’t want to frustrates users when I don’t have to. And I don’t want these trivial tasks to distract them from enjoying the good content, services and products on my website and apps. To do so, I apply a 3 step approach to help me an my team
Step 1 Identify the Differences and Focus: many of such communication are standard flow, but there almost in all cases there are also unique flows. Dropbox, for example, sends me weekly update on what has been changed, but I will not expect such updates from e-commerce websites. I always start identifying what is unique because I know in these situations, I need to create the story because users can’t assume anything from their past experience. And these are also flows I make sure to test later on. While the common ones I can simply refer to the best practices.
Step 2 Find out the 5W+1H: where, when, what, why, who and how, it does not mean I need to have all of them, but I make sure I think about go through all of them and make sure nothing important is left out. Take “Reset password” email for example, I will have:
- A Clear Subject Line that describe what the email is about;
- The User Name on the main body as whom this is addressing to;
- Contents related to how if:
- User want to proceed to reset (a reset password URL or HTML button)
- Users don’t want to proceed (text reassuring nothing happens to their password if reset is not complete)
- Contact support team email and/or telephone number (you have no idea how much they will appreciate a real person)
- Important times such as:
- When the URL will expire (and preferably not something like “24 Hours” but “2016-11-30 11:49:59”, your system should have such info anyway)
- When the hotline is available
Step 3 Verify in the Context of Overall Experience: I usually take the user flow diagram and fill in the different emails, SMS and webpages at their place try to go through the flow by myself; I do think in the user test as well, especially if it is not something standard such as reset password or change mobile number. In my experience it has been a great way to optimize the experience (find what needs to be emphasized) and identify gaps (what is missing).
Adopting the 3-step approach to administrative communications helps to put things in perspective and reduce repeated works. It had worked very well for me and help it will be helpful for you as well.
Reference:
I got an email saying I requested a new password but I didn't make this request
https://www.facebook.com/help/226272054050348
Principles For Developing A Secure Password Reset System
https://www.wiredtree.com/blog/principles-developing-secure-password-reset-system/
Help to get your application approved
https://support.google.com/adsense/answer/75109