Are you really suggesting that email should just be for work, and that we should ignore personal use cases: photo and link sharing, for example, or just writing a thoughtful message to a seldom-seen friend? Lots of Gmail users do those things, and I reject the notion that email providers should just cede that ground to proprietary communication silos.
The point that I was trying to get across in that article was not that all messages should be shorter. Rather, that the form of the composition UI sets expectations for what the message itself should look like. The form of Gmail's old compose set the expectation that it was a formal medium; that writing something short might not be appropriate, and that writing an email should be like writing a memo in a word processor. That makes messages feel less immediate, less personal, and as a result raises the bar for sending shorter and/or personal messages.
The goal was not to prevent users from writing long messages, but rather to provide a better balance between the two. Ultimately, though, this isn't a personal vs work issue. Facilitating short messages is arguably even more important in work settings where everybody tends to be inundated by large amounts of legitimate work-related email. There is real value in having a UI that gives users signals that it is ok to write shorter messages.
At the same time, on a 1366x768 browser window I can fit more than 3 paragraphs of lorem ipsem from http://www.lipsum.com/ in the default Gmail compose window before it even starts to scroll. In full screen mode at the same resolution you can fit 5 paragraphs before it starts to scroll. The UI isn't preventing you from writing something longer if that's what you need to do.
Hi Jason. thanks for replying. I was genuinely curious as to your opinion on the gmail UI since you are more experienced than me.
I don't have much issue with the spacing in compose. I have an issue with hiding the formatting and functionality of the email.
I was not suggesting ignoring personal use cases. Given the popularity of Gmail, a lot of people uses email to do work for personal use. However, SMS/whatsapp/fb chat is a much more effective medium for personal use cases. Picking up the phone to reply a text feels a lot more personal and less intimidating than email. The new redesign does not make it less intimidating to use email.
I agree that Gmail should "influence" users on their behaviors by changing the UI to some extent. However, you should facilitate the user's existing use cases. Most people would prefer to send an SMS for personal messages and send email for work. Forcing email to look more minimalistic like an SMS by removing formatting / forward button is not user friendly. Another example is the pop in compose button. I like to see other emails before I compose - naturally, you would think i would love the new pop in since I can see emails as I compose. However, I am used to having one tab open for composing and another for reading emails.
Out of curiosity:
How do you determine whether a redesign is successful or not? Are there particular metrics you pay attention to?
Actually, we care deeply about customer feedback and several of us on the product team read the threads on the product forums personally, especially when there is vocal feedback. We don't necessarily act on everything, of course. With a product that operates at global scale we have a huge responsibility to make sure we are making optimizations that improve Gmail for as many users as possible, and the only way to do that is to rely on metrics and surveys that capture the entire user base. Otherwise we would be, by definition, changing a UI used by hundreds of millions in response to a vocal, non-representative minority. Basically we use the product forums and social media to figure out of there are trends or issues that we should be concerned about, but then always validate those issues with real data before taking action.
Thanks for the reply Jason. Many of the movements of the Google properties have been toward the light over the last two years and it certainly is a very difficult task for the Google peeps. Props to them.
Alas, as a keen WebApp dev myself, I have found myself having to Google for how to do tasks I once did easily. Such searches eventually uncover the highly counter intuitive means to do the previously simple thing (via someone's blog post), or reveal that the feature has been dropped from the new and improved version. Such issues are not a subjective matter of color choice or icon design, but the reduction of functionality and confounding of user interaction.
Largely Google wins the efforts to improve their products, but I've seen a half dozen such failings in the last year that I am surprised managed to ship. Hopefully their batting average continues to improve.
The situation is actually a bit worse than that. As soon as Barry replies, Adam becomes the only person on the to line and everybody else is moved to cc despite all of Adam's hard work to distinguish recipient types up front. To vs CC is basically broken in threaded conversations. Moreover, unless you turn on some hidden options there is no visual indicator telling you who was on the to line vs the cc line in the Gmail inbox anyway. The distinction has become meaningless for the vast majority of cases.
The point that I was trying to get across in that article was not that all messages should be shorter. Rather, that the form of the composition UI sets expectations for what the message itself should look like. The form of Gmail's old compose set the expectation that it was a formal medium; that writing something short might not be appropriate, and that writing an email should be like writing a memo in a word processor. That makes messages feel less immediate, less personal, and as a result raises the bar for sending shorter and/or personal messages.
The goal was not to prevent users from writing long messages, but rather to provide a better balance between the two. Ultimately, though, this isn't a personal vs work issue. Facilitating short messages is arguably even more important in work settings where everybody tends to be inundated by large amounts of legitimate work-related email. There is real value in having a UI that gives users signals that it is ok to write shorter messages.
At the same time, on a 1366x768 browser window I can fit more than 3 paragraphs of lorem ipsem from http://www.lipsum.com/ in the default Gmail compose window before it even starts to scroll. In full screen mode at the same resolution you can fit 5 paragraphs before it starts to scroll. The UI isn't preventing you from writing something longer if that's what you need to do.