@kevincrepin @ilmartyrk In user tests, there have been some insights to show that:
1. Some users assume that the dropdown box that appears with the email they are entering means that the email is saved in the system.
In one test, someone remarked on this "Oh, I'm here already!", thinking that by seeing their email pop-up it meant that they were already in the system.
In another test, my feeling (though it's just an intuition from what I saw, and what would make sense as a likely thought process) is that the user was confident in using the incorrect email she had entered for me because it popped up once she had entered the correct email format. Connected to the above, as users can understand the dropdown as meaning that the email is in the system (rather than what it actually means - simply that the email format is correct), they can then be more likely to go ahead and select it without checking what they have entered. Screenshot below of a user selecting my incorrect email when it popped up. I later told her what had happened (as I didn't get an invite), but she would have had no way of knowing this otherwise.
As per this video, the UX for selecting someone who is already in the system and the UX for selecting an email that simply has the correct format are very similar, so would make sense that they are easily confusable:
2. Users expect the system to remember emails they have previously entered
Connected to the above, users do expect and want the system to remember emails that they have entered previously. They find it annoying to have to keep typing in the whole email, every time they want to invite the same person - e.g. their colleague with whom they are co-creating topics.
@ilmartyrk is it currently only the case that the system remembers people who have opted into the "show my name and email" in the register/profile opt-in? Or how does it work?
3. One user was confused by the 'Search' as she just wanted to add an email address
She thought for a minute that this field wasn't the place to enter a new email address, but just to search for people already on the system. This would seem to add to the issues above, that it suggests you are searching for someone who is already within the system, rather than adding someone new (which is often the case).
Suggestions
Could we have UX for adding an email that is simply the correct format as something different to the UX for adding an email that is stored in the system?
Can the system remember email addresses that someone has previously entered, and have them autofill when they start typing them in?
Should we change the text for 'Search' (and maybe the search icon too) so it applies to both searching and entering emails? Not sure what to suggest though, maybe 'Search / add', but that feels a bit odd..
@kevincrepin @ilmartyrk In user tests, there have been some insights to show that:
1. Some users assume that the dropdown box that appears with the email they are entering means that the email is saved in the system.
In one test, someone remarked on this "Oh, I'm here already!", thinking that by seeing their email pop-up it meant that they were already in the system.
In another test, my feeling (though it's just an intuition from what I saw, and what would make sense as a likely thought process) is that the user was confident in using the incorrect email she had entered for me because it popped up once she had entered the correct email format. Connected to the above, as users can understand the dropdown as meaning that the email is in the system (rather than what it actually means - simply that the email format is correct), they can then be more likely to go ahead and select it without checking what they have entered. Screenshot below of a user selecting my incorrect email when it popped up. I later told her what had happened (as I didn't get an invite), but she would have had no way of knowing this otherwise.
As per this video, the UX for selecting someone who is already in the system and the UX for selecting an email that simply has the correct format are very similar, so would make sense that they are easily confusable:
https://www.loom.com/share/e9a8f82552eb4a95aee7a1dd86565978?sid=f2e09fc7-5dd4-437f-9f90-23e9434e1388
2. Users expect the system to remember emails they have previously entered
Connected to the above, users do expect and want the system to remember emails that they have entered previously. They find it annoying to have to keep typing in the whole email, every time they want to invite the same person - e.g. their colleague with whom they are co-creating topics.
@ilmartyrk is it currently only the case that the system remembers people who have opted into the "show my name and email" in the register/profile opt-in? Or how does it work?
3. One user was confused by the 'Search' as she just wanted to add an email address
She thought for a minute that this field wasn't the place to enter a new email address, but just to search for people already on the system. This would seem to add to the issues above, that it suggests you are searching for someone who is already within the system, rather than adding someone new (which is often the case).
Suggestions
Could we have UX for adding an email that is simply the correct format as something different to the UX for adding an email that is stored in the system?
Can the system remember email addresses that someone has previously entered, and have them autofill when they start typing them in?
Should we change the text for 'Search' (and maybe the search icon too) so it applies to both searching and entering emails? Not sure what to suggest though, maybe 'Search / add', but that feels a bit odd..