Should we ask users what they want?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
We are taking users opinion as shown in the image. Is it fine asking users if they would like to use voice search or not?
user-expectation user-research ux-designer
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
1
down vote
favorite
We are taking users opinion as shown in the image. Is it fine asking users if they would like to use voice search or not?
user-expectation user-research ux-designer
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
We are taking users opinion as shown in the image. Is it fine asking users if they would like to use voice search or not?
user-expectation user-research ux-designer
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
We are taking users opinion as shown in the image. Is it fine asking users if they would like to use voice search or not?
user-expectation user-research ux-designer
user-expectation user-research ux-designer
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago


ssharma
1062
1062
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
ssharma is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
I feel like this question can be answered in 2 ways, regarding asking users in general and your current specific problem/image.
Asking users in general
Asking the user for an opinion can, in some cases be a good thing. The answers you get however should in most cases be used as a way to see if there is an underlying problem.
For instance, a small example. Say your company has a lot of people that use public transport to get to work and it takes a long time. You ask your workers, what can we do to ease your life?
They answer that they want a company car to get to work faster. In most cases this 'car' will just reduce the travel time by a small margin. What they might really want is to reduce the travel time, so a better solution to the problem can be allowing them to work from home on certain days. Another solution can be to set up a system that lets employees travel together, spending time with someone to talk to can make the travel time feel less.
If you want to know more about interviewing users, nngroup has some great articles on the subject.
- First Rule of Usability? Don't Listen to Users
- Interviewing Users
Your current image/problem
I believe that your current way of asking the users is a bit misleading. The question you ask can be seen in 2 ways: 'Do you maybe want it in the future' or 'Do you want to use it now?'.
For a user, it currently looks more like if he/she answers yes you can use voice search to find a product/service (small extra hickup might be that I start talking to my phone and say 'yes' but your system does not respond because I should first click yes).
However, I believe you are more looking for information if you should implement it in the future. So now, you have a clash in your intention and what the user can do. I would advice to ask questions to gather information later, maybe after they used the service (so after they bought your product) or you can email them later (remember, EU law requires you to ask permission first!) with this question.
Implementation
Voice search, is currently to my understanding an advanced search feature for people other than millenniums (apparently 35.8% of the millenniums use voice search). As Zuluk mentioned, just implementing the function could be the best option rather then asking (However, make sure it works correctly. Voice search that does not work properly is bad UX). I even would go as far not to offer a question box but just use an icon like Google uses in the search bar.
I believe an icon like that will be more or less the standard in the future.
+1 for taking a step back and analyzing the bigger picture
– Big_Chair
2 hours ago
add a comment |Â
up vote
1
down vote
In my opinion it is a very good idea to give the user the choice to type into textfield or to use voice assitance.
The best implementation might be not to ask the user, but to support both or support text input at standard and give the user the choice to activate (just say yes, I want to use voice assistance) voice input. Because the user has no added value by clicking NO
in your screenshot, except you save his decision in a cookie to use this answer for further cases.
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Agreed, + users may change opinion. I have clicked NO, and have no more voice option. In 4 months I see at my colleague he is using that feature and change my opinion that is cool now and I want it.
– xul
2 hours ago
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
I feel like this question can be answered in 2 ways, regarding asking users in general and your current specific problem/image.
Asking users in general
Asking the user for an opinion can, in some cases be a good thing. The answers you get however should in most cases be used as a way to see if there is an underlying problem.
For instance, a small example. Say your company has a lot of people that use public transport to get to work and it takes a long time. You ask your workers, what can we do to ease your life?
They answer that they want a company car to get to work faster. In most cases this 'car' will just reduce the travel time by a small margin. What they might really want is to reduce the travel time, so a better solution to the problem can be allowing them to work from home on certain days. Another solution can be to set up a system that lets employees travel together, spending time with someone to talk to can make the travel time feel less.
If you want to know more about interviewing users, nngroup has some great articles on the subject.
- First Rule of Usability? Don't Listen to Users
- Interviewing Users
Your current image/problem
I believe that your current way of asking the users is a bit misleading. The question you ask can be seen in 2 ways: 'Do you maybe want it in the future' or 'Do you want to use it now?'.
For a user, it currently looks more like if he/she answers yes you can use voice search to find a product/service (small extra hickup might be that I start talking to my phone and say 'yes' but your system does not respond because I should first click yes).
However, I believe you are more looking for information if you should implement it in the future. So now, you have a clash in your intention and what the user can do. I would advice to ask questions to gather information later, maybe after they used the service (so after they bought your product) or you can email them later (remember, EU law requires you to ask permission first!) with this question.
Implementation
Voice search, is currently to my understanding an advanced search feature for people other than millenniums (apparently 35.8% of the millenniums use voice search). As Zuluk mentioned, just implementing the function could be the best option rather then asking (However, make sure it works correctly. Voice search that does not work properly is bad UX). I even would go as far not to offer a question box but just use an icon like Google uses in the search bar.
I believe an icon like that will be more or less the standard in the future.
+1 for taking a step back and analyzing the bigger picture
– Big_Chair
2 hours ago
add a comment |Â
up vote
3
down vote
I feel like this question can be answered in 2 ways, regarding asking users in general and your current specific problem/image.
Asking users in general
Asking the user for an opinion can, in some cases be a good thing. The answers you get however should in most cases be used as a way to see if there is an underlying problem.
For instance, a small example. Say your company has a lot of people that use public transport to get to work and it takes a long time. You ask your workers, what can we do to ease your life?
They answer that they want a company car to get to work faster. In most cases this 'car' will just reduce the travel time by a small margin. What they might really want is to reduce the travel time, so a better solution to the problem can be allowing them to work from home on certain days. Another solution can be to set up a system that lets employees travel together, spending time with someone to talk to can make the travel time feel less.
If you want to know more about interviewing users, nngroup has some great articles on the subject.
- First Rule of Usability? Don't Listen to Users
- Interviewing Users
Your current image/problem
I believe that your current way of asking the users is a bit misleading. The question you ask can be seen in 2 ways: 'Do you maybe want it in the future' or 'Do you want to use it now?'.
For a user, it currently looks more like if he/she answers yes you can use voice search to find a product/service (small extra hickup might be that I start talking to my phone and say 'yes' but your system does not respond because I should first click yes).
However, I believe you are more looking for information if you should implement it in the future. So now, you have a clash in your intention and what the user can do. I would advice to ask questions to gather information later, maybe after they used the service (so after they bought your product) or you can email them later (remember, EU law requires you to ask permission first!) with this question.
Implementation
Voice search, is currently to my understanding an advanced search feature for people other than millenniums (apparently 35.8% of the millenniums use voice search). As Zuluk mentioned, just implementing the function could be the best option rather then asking (However, make sure it works correctly. Voice search that does not work properly is bad UX). I even would go as far not to offer a question box but just use an icon like Google uses in the search bar.
I believe an icon like that will be more or less the standard in the future.
+1 for taking a step back and analyzing the bigger picture
– Big_Chair
2 hours ago
add a comment |Â
up vote
3
down vote
up vote
3
down vote
I feel like this question can be answered in 2 ways, regarding asking users in general and your current specific problem/image.
Asking users in general
Asking the user for an opinion can, in some cases be a good thing. The answers you get however should in most cases be used as a way to see if there is an underlying problem.
For instance, a small example. Say your company has a lot of people that use public transport to get to work and it takes a long time. You ask your workers, what can we do to ease your life?
They answer that they want a company car to get to work faster. In most cases this 'car' will just reduce the travel time by a small margin. What they might really want is to reduce the travel time, so a better solution to the problem can be allowing them to work from home on certain days. Another solution can be to set up a system that lets employees travel together, spending time with someone to talk to can make the travel time feel less.
If you want to know more about interviewing users, nngroup has some great articles on the subject.
- First Rule of Usability? Don't Listen to Users
- Interviewing Users
Your current image/problem
I believe that your current way of asking the users is a bit misleading. The question you ask can be seen in 2 ways: 'Do you maybe want it in the future' or 'Do you want to use it now?'.
For a user, it currently looks more like if he/she answers yes you can use voice search to find a product/service (small extra hickup might be that I start talking to my phone and say 'yes' but your system does not respond because I should first click yes).
However, I believe you are more looking for information if you should implement it in the future. So now, you have a clash in your intention and what the user can do. I would advice to ask questions to gather information later, maybe after they used the service (so after they bought your product) or you can email them later (remember, EU law requires you to ask permission first!) with this question.
Implementation
Voice search, is currently to my understanding an advanced search feature for people other than millenniums (apparently 35.8% of the millenniums use voice search). As Zuluk mentioned, just implementing the function could be the best option rather then asking (However, make sure it works correctly. Voice search that does not work properly is bad UX). I even would go as far not to offer a question box but just use an icon like Google uses in the search bar.
I believe an icon like that will be more or less the standard in the future.
I feel like this question can be answered in 2 ways, regarding asking users in general and your current specific problem/image.
Asking users in general
Asking the user for an opinion can, in some cases be a good thing. The answers you get however should in most cases be used as a way to see if there is an underlying problem.
For instance, a small example. Say your company has a lot of people that use public transport to get to work and it takes a long time. You ask your workers, what can we do to ease your life?
They answer that they want a company car to get to work faster. In most cases this 'car' will just reduce the travel time by a small margin. What they might really want is to reduce the travel time, so a better solution to the problem can be allowing them to work from home on certain days. Another solution can be to set up a system that lets employees travel together, spending time with someone to talk to can make the travel time feel less.
If you want to know more about interviewing users, nngroup has some great articles on the subject.
- First Rule of Usability? Don't Listen to Users
- Interviewing Users
Your current image/problem
I believe that your current way of asking the users is a bit misleading. The question you ask can be seen in 2 ways: 'Do you maybe want it in the future' or 'Do you want to use it now?'.
For a user, it currently looks more like if he/she answers yes you can use voice search to find a product/service (small extra hickup might be that I start talking to my phone and say 'yes' but your system does not respond because I should first click yes).
However, I believe you are more looking for information if you should implement it in the future. So now, you have a clash in your intention and what the user can do. I would advice to ask questions to gather information later, maybe after they used the service (so after they bought your product) or you can email them later (remember, EU law requires you to ask permission first!) with this question.
Implementation
Voice search, is currently to my understanding an advanced search feature for people other than millenniums (apparently 35.8% of the millenniums use voice search). As Zuluk mentioned, just implementing the function could be the best option rather then asking (However, make sure it works correctly. Voice search that does not work properly is bad UX). I even would go as far not to offer a question box but just use an icon like Google uses in the search bar.
I believe an icon like that will be more or less the standard in the future.
answered 3 hours ago
Kevin M.
450111
450111
+1 for taking a step back and analyzing the bigger picture
– Big_Chair
2 hours ago
add a comment |Â
+1 for taking a step back and analyzing the bigger picture
– Big_Chair
2 hours ago
+1 for taking a step back and analyzing the bigger picture
– Big_Chair
2 hours ago
+1 for taking a step back and analyzing the bigger picture
– Big_Chair
2 hours ago
add a comment |Â
up vote
1
down vote
In my opinion it is a very good idea to give the user the choice to type into textfield or to use voice assitance.
The best implementation might be not to ask the user, but to support both or support text input at standard and give the user the choice to activate (just say yes, I want to use voice assistance) voice input. Because the user has no added value by clicking NO
in your screenshot, except you save his decision in a cookie to use this answer for further cases.
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Agreed, + users may change opinion. I have clicked NO, and have no more voice option. In 4 months I see at my colleague he is using that feature and change my opinion that is cool now and I want it.
– xul
2 hours ago
add a comment |Â
up vote
1
down vote
In my opinion it is a very good idea to give the user the choice to type into textfield or to use voice assitance.
The best implementation might be not to ask the user, but to support both or support text input at standard and give the user the choice to activate (just say yes, I want to use voice assistance) voice input. Because the user has no added value by clicking NO
in your screenshot, except you save his decision in a cookie to use this answer for further cases.
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Agreed, + users may change opinion. I have clicked NO, and have no more voice option. In 4 months I see at my colleague he is using that feature and change my opinion that is cool now and I want it.
– xul
2 hours ago
add a comment |Â
up vote
1
down vote
up vote
1
down vote
In my opinion it is a very good idea to give the user the choice to type into textfield or to use voice assitance.
The best implementation might be not to ask the user, but to support both or support text input at standard and give the user the choice to activate (just say yes, I want to use voice assistance) voice input. Because the user has no added value by clicking NO
in your screenshot, except you save his decision in a cookie to use this answer for further cases.
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
In my opinion it is a very good idea to give the user the choice to type into textfield or to use voice assitance.
The best implementation might be not to ask the user, but to support both or support text input at standard and give the user the choice to activate (just say yes, I want to use voice assistance) voice input. Because the user has no added value by clicking NO
in your screenshot, except you save his decision in a cookie to use this answer for further cases.
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 4 hours ago
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 4 hours ago
zuluk
1115
1115
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
zuluk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Agreed, + users may change opinion. I have clicked NO, and have no more voice option. In 4 months I see at my colleague he is using that feature and change my opinion that is cool now and I want it.
– xul
2 hours ago
add a comment |Â
Agreed, + users may change opinion. I have clicked NO, and have no more voice option. In 4 months I see at my colleague he is using that feature and change my opinion that is cool now and I want it.
– xul
2 hours ago
Agreed, + users may change opinion. I have clicked NO, and have no more voice option. In 4 months I see at my colleague he is using that feature and change my opinion that is cool now and I want it.
– xul
2 hours ago
Agreed, + users may change opinion. I have clicked NO, and have no more voice option. In 4 months I see at my colleague he is using that feature and change my opinion that is cool now and I want it.
– xul
2 hours ago
add a comment |Â
ssharma is a new contributor. Be nice, and check out our Code of Conduct.
ssharma is a new contributor. Be nice, and check out our Code of Conduct.
ssharma is a new contributor. Be nice, and check out our Code of Conduct.
ssharma is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f121338%2fshould-we-ask-users-what-they-want%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password