How can you know what "maybe" means? In the context of a web service, you can't.He also rails against five-star ratings since those have an implicit "maybe" (three stars) that tells you very little. Thoughts?
Maybe you should decide?
June 20, 2007 · 13 Comments
Jeffrey Zeldman suggests that "maybe" is not an appropriate choice and should not be offered to users.
As someone building a social networking website, I know what he means and, whilst "maybe" was part of our earlier design, when we launch, you will only be able to say "yes" or "no" to an event. Zeldman says:
Tags: programming · scazu

13 responses so far ↓
1 Brian Rinaldi // Jun 20, 2007 at 5:12 PM
2 Mark // Jun 20, 2007 at 6:48 PM
3 Joe // Jun 20, 2007 at 9:01 PM
4 Andy J // Jun 21, 2007 at 12:19 AM
5 Nathan D // Jun 21, 2007 at 12:25 AM
6 Jeremy French // Jun 21, 2007 at 4:31 AM
On the other hand, if you're less worried about the data collected, and more concerned with the user experience (like say, a poll on a social networking site), perhaps giving your users "someplace to hide" is a good thing. If I'm asked to rate something, and I'm truly ambivalent about it, I don't feel comfortable giving it 2 stars out of 4, nor 3 out of 4. I feel like I'm lying a little bit, thereby skewing the data. That discomfort is a very small part of my day, obviuosly, but when you're talking in terms of a web-based user experience, that small amount of discomfort might be the tipping point between a one-time visitor and a returning customer.
7 tony of the weeg clan // Jun 21, 2007 at 5:06 AM
its almost like there needs to be an "im interested, but i still have to think about it" setting then.
since maybe is truly a position on something. i use maybe when i want to express an interest in something, but i cannot commit. i want the person to know that i acknowledge what they are doing/saying, but i dont have enough facts to FULLY decide what side of the fence im on...
:) tw
8 Sammy Larbi // Jun 21, 2007 at 6:02 AM
9 Ouz Demirkap1 // Jun 21, 2007 at 6:09 AM
If you have a "may be", try to supply more details to help the decision and force to decide.
In business perspective I have this problem where I work now. I say always that we must be satisfied before delivering the client side. But unfortunately in real world, time and budget is the main key. On the other hand satisfaction is a subjective thema and the main question is "who decide". :)
10 Peter Ladage // Jun 21, 2007 at 6:42 AM
11 rob // Jun 21, 2007 at 8:20 AM
If I was offered the chose yes / no and that's all (in some situations) I just wouldn't answer.
With an event, some people don't know till the last minute if they can go - I'd rather know that 50 people are going to show up and another 10 might - as opposed to thinking 60 will show up "for sure" or all 60 might possibly show up.
I guess it depends on if you find gathering information / people participating more important than "good" aggregated data (which could be argued that more data even if just the middle is still more data - welcome to the bell curve.)
12 Eric // Jun 21, 2007 at 2:41 PM
The reason people pick 3 our of 5 stars when reviewing something is that they didn't <i>have</i> a strong impression either way. Sure, the numbers get more exciting if you force people to arbitrarily choose 2/4 or 3/4 when they don't really think something is notably good or bad, but it's just a matter of adding noise to the signal. People familiar with such a system will learn to disregard 2/4 and 3/4 as anything more than a very fat 3/5.
13 Luke Kilpatrick // Jun 22, 2007 at 7:03 AM
Leave a Comment