The Future: Gmail, Social Media, and You

The Future: Gmail, Social Media, and You

gmail_logo_stylized_thumb35555It’s been many weeks since my conversion has been wholly complete, many months since it became my primary means of email communication, when I was converted by an Android, and years since I first started using…. Gmail.

Over the past many weeks I have explored, elaborated, and exhausted the exercising of my resistance. Now, with such resistance both worn down and overcome, drawn out through my conversion by an Android, let’s explore what improvements remain undone, those of the ‘Should Do’ variety that would directly facilitate the conversions of many, many more to the ways of Gmail.

what brought about this conversion, (1) (2)
why it took so long, and (3) (4) (5) (6) (7)
what should be done to encourage greater Gmail adoption. (8) (9)

Should Do

00_gmail-all Perhaps the greatest challenge to Gmail is Information Overload and the ability to zero in on both what is desired and what is most important.

  • Gmail can often feel like a very, very long list of information with few visual cues assisting in the efficient user parsing of the data. Many things can be done to assist in this readability challenge.
    • Support grouping of emails / discussion threads, by tags, from, to, substrings, age, size, frequency of receipt as well as frequency of reply (or even average delay before reply to), etc.
    • The introduction of the concepts of hierarchy would allow users to zoom in on what is important, becoming less dependent on knowing the precise search, becoming less likely to miss the ever critical email buried in a long list or discussion thread. Beyond the custom coloring of tags (a labs feature) tags should be able to be grouped as well as support hierarchical concepts, sub-tags. This would allow for a bridging of the folder and tag paradigms within the Gmail experience. Of course, having the choice to use tags, tag groups, and sub-tags and their groups, together with folders would provide for even more flexibility of these means of thinking and empower the users to choose the paths best suited for them. Most importantly, these concepts, when implemented, should facilitate finding information without knowing the exact details incumbent to initiate a search, i.e. browsing, possessing the characteristic of easy historical reference of read and unread content within an organizational superstructure that can cut through the overwhelming list of lists experience of today’s Gmail.
    • Sorting and filters, dynamic, inline, and customizable, as well as saved filter rules, another concept that Outlook implemented very well by way of their Search Folders (the name itself almost necessitates a Google equivalent), would also help cut through the clutter.
    • Provide the option to display either the total number (read + unread) or total unread tagged items alongside the tags. In turn, this would provide the ability to immediately archive communications, while maintaining a visual cue of their existence. In this approach, tags could function as more than mere labels, but become more action oriented keeping track of such things as to-do items or other rapidly evolving and critical communication (that would benefit from being separated from the clutter of the Inbox).
  • Discussion threads for tracking communication evidently work well for some people. For others, the thread is a sure fire way to misplace an important subset of the conversation.
    • Enable the ability to disable threads altogether, establish new threads and sub-threads, remove components / emails / sub-threads from a thread.
    • Allow for archiving of selective portions of a discussion thread.
    • Permit discussion threads that consist of multiple modes of communication; a single discussion thread could consist of Google Talk, Twitter, and Email communications centered around a single topic.

Google has many products that have official, open API’s and hooks for cross-product integration; lacking in the case of Gmail . Open source and APIs play very google_apisimportant roles at Google. They …

  • accelerate idea creation — inspire and build upon,
  • leverage the power of the community — improving and extending the product through community ideas, learning and need discovery,
  • facilitate testing (and bug fixing) on greater scale,
  • increase the stickiness of Google products,
  • .. among many other value-added benefits.

And, greater attention to Integration and Consistency within Gmail would also greatly benefit its current and potential users by…

  • Enabling better cross-linking between Google products (e.g. between Google Calendar and Gmail) as well as amongst external properties (e.g. Gmail and OneNote). For example, including the Gmail live discussion thread from which the Google Calendar event was created would be a step in the right direction. In addition, Gmail and Google Docs could be more tightly integrated, with document revisions coordinated and displayed and accessible, alongside the messages within the discussion thread making use of the underlying document(s). Even integrating, to various degrees, with Google Analytics can provide greater understanding of effective communications, best times to reach out to people, best ways to get desired responses, etc.
  • Creating an open Gmail Labs, or Gmail App Store, for third party development of plugins and enhancements for Gmail.
  • Increasing openness, modularity and portability of Gmail and its parts by establishing an Open Development Platform to provide for the rapid evolution of the features and ideas of Gmail; leverage the strategy that has proven so successful in other Google products.
  • Blending the social media stream, from Picasa, YouTube, Facebook, and Orkut to micro-blogging, blog posts, and comments, building upon the current integration of Google Talk and Google Voice to further become the centralized, single place for all an individuals web communication.
  • Supplying a framework for the robust flexibility and customization of the UX and UI. For example, let users create their own buttons, button containers, and both custom and common actions.
  • Integrating more easily and seamlessly with the OS. Microsoft Windows allows the user to right-click ‘send to mail recipient’ on files.’ When Gmail is the primary email client of choice, performing such action should direct the straight to a newly composing Gmail message.
  • Experience and information management should be consistent from one Google product to another, most especially products like Gmail (tag-based organization) and Google Calendar (calendar-based organization) and Google Docs (folder-based organization).

Now

htc-hero-pictures-15 Now that I have switched to Gmail from Outlook, I couldn’t be happier that I was so coaxed into this long resisted position. But, the conversion could have been better facilitated, and more can be done to accelerate others still resisting. I only hope that this journey, together shared, was more than fun, but also illustrative and educational for those that use, may some day use, or are in positions of power and influence to improve the web-based email / communication platform, Gmail.

First converted to a fan of Android, the platform, then converted to a fan of Gmail, too. I resisted the Android, and succumbed. I, for much longer, both longed for and resisted the conversion to Gmail. Through all of this, despite the long path already journeyed, there remain many more steps to walk, specific steps that those overseers of Gmail can take to further enlighten the experience of ones as of now converted as well as those yet to be.

Remember & Share

Subscribe now (click here) to make sure you don’t miss out on other exciting product explorations and in-depth looks at the people and strategies behind them.

Enjoy & Tweet!

Jeremy Horn 
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Google Add to Mixx!
About these ads

Microsoft’s Mistakes. You too can learn from them.

microsoft (Part 2 of 2) The other day I briefly highlighted what I saw as the ‘Good parts’ and ‘Good starts’ within Windows Live Events to clearly distinguish where I feel the product has missed a golden opportunity; and highlight some broader takeaways that should be applied to the current and next generation of online web products and services.

Not so good parts…

Overall, I found the user experience pretty good, as long as I didn’t have to interact with the page and its components and features. In some cases I found the negatives to be in the simple user interaction and experience design, in others it was the sense of being mislead by the user interface to expect bigger and better functionality from my click.

Where’s the pop?

The User Interface didn’t POP. By pop, I am not referring to those annoying ads that everyone loves to hate, but to the responsiveness and feeling that goes along with the interaction of the user interface. Here, with Windows Live Events, I found the interface experience, my user experience, to be slow, sluggish, and, at times, sleep inducing.

When I log into my account and select an event that I want to update or invite people to… let me do it QUICKLY and painlessly. I want to login (pop), click (pop), invite (pop), and go (pop). The interface rendering times, the additional pages that were being loaded again and again, can all benefit from a major overhaul. Empower me, your potential user, to do what I want to do with my event…efficiently, productively.

Microsoft, did you ever hear of Ajax or dynamic page elements? My advice to you is to make the event overview and its management a single page, a page that loads the ‘dashboard’ view once and dynamically allows me to enter new information or be updated while I am looking at my event. Don’t force me to navigate back and forth, again and again, to manipulate my details and invite people. All those extra pages, all that extra loading, all that interruption in my workflow of planning and managing and ENJOYING my event just slows me down, ruins any potential happiness I may get from some of the features, and makes me want to look elsewhere for a UI that will be fast, responsive, and fun to interact with.

The sluggishness I found to be present within the UI goes beyond the unnecessary extra page loading that occurs, but is also found in the initial page downloading and rendering. I am not, as of the posting of this article, sure what is going on under the hood or what sort of processes at Microsoft are resulting in this bloated feeling that appears to be all too common to Microsoft products, that causes such a slow and sluggish feeling (I used IE , FF, and Opera browsers). The sluggish interface is not unique to Windows Live Events. I also experienced excessive sluggishness in Microsoft’s (now discontinued) Live Product Search — a product I thought was head and shoulders above the competition out there. With Live Product Search, a product that I truly enjoyed and recommended to people, as with Windows Live Events, its big negative was that it was slow in how it responded to user interaction . Back then, I stopped using Live Product Search, and most likely many other people did too, because it was just sooo slow.

The ‘fun potential’ of the user interface is present, but quickly dissipates when the actual interaction portion of the user experience equation is taken into account. Correcting this portion of Windows Live Events will go far towards user adoption, but is also the lesser of the ‘Not so good parts.’

The future is in Modular Innovation.

Within Windows Live Events It is nice that I can blog about my event; even though it is not readily obvious that I can do so at first glance at the event’s dashboard view. It is nice that I can share pictures and discuss the events with friends and other attendees. It is nice that it is an experience integrated with the Windows Live suite of web products.

Wouldn’t it be NICER (or great, or awesome) if I could blog, not just on Windows Live Spaces, but on WordPress (The Product Guy’s platform) or other blog formats? Wouldn’t it be NICER if I could share or integrate with my pictures on Flickr or other photo sharing platforms? Wouldn’t it be NICER if I could communicate with other people, in real-time, or via Twitter or receive updates when there are new bits of information being shared?

Answer: Yep.

While the layout of the page presents the promise of a sharp user experience and alludes to the potential of a great, integrated, centralizing event planning application through some obvious and some hard to find features, it falls far short. So far short, it only is integrated with Microsoft – a very limited web product audience.

Windows Live Events, what could have been a nice module that combined and brought together information from other web products (modules) online, instead is only a repackaging of a proprietary Microsoft-only event planner.

Those tougher to find features on the Event’s homepage are the ones that drew my greatest attention for which I also carefully chose my words when describing. I purposely described “the good” with words like “promising” and the “layout encourages.” While there are hints of good ideas, hints of implementing (a) Modular Innovation(s), Windows Live Events, in my opinion, missed a great opportunity. (Of course, I am not saying they cannot make a reattempt at this opportunity through a future release.)

The (missed?) opportunity…

Event planning is not unique to the Internet. What I did like seeing was their eye towards greater integration with other services. However, without allowing for integration with third-parties (Via an API? perhaps.), what could possibly be the incentive for people to sign-up and use Windows Live Events? For people that are not Windows Live-only users, there isn’t any.

Integration is the key to any chance of broad-based success for Live Events. Have I mentioned this a few times already? Hmmm… it must mean it is IMPORTANT! What is unique here? Microsoft Events does present a nice, simplified UI, but with so many other product options out there, there is nothing making this new service stand out. This is where the opportunity lies.

Windows Live Events would be more interesting to the public at large if events could just simply integrate with other blog platforms and social networks to invite friends from your social network to your created Live Events. Don’t limit the users to the Microsoft blogging platform and picture sharing — let me choose and customize my user experience by connecting it with other online products (that aren’t Microsoft, if I choose).

‘missed?’ well, one can hope that the Windows Live Events team will heed my advice and make many of these improvements.

Learning parts…

There are many constructive lessons that can be learned by poking at and experiencing Windows Live Events that, when applied to other web products, will result in broader acceptance and adoption, and an overall better experience that your users will come back for time and time again.

To build a larger base, secondarily, Microsoft will have to clean-up and make enjoyable (interactive, responsive, not slow) the user experience; but, primarily, at the very core, empower its users through modularity by…

  • Allowing integration. Enabling people to connect their Live Events to their other online experiences (Flickr, YouTube, Twitter, Blogger, IM, etc.). For example, let me invite people that are my close friends in MySpace to my party being planned via Live Events.
  • Allowing portability. Enabling people to download or move all of their event information for editing or manipulating on other event or related platforms. This will allow more people to try it out, without worrying about losing their information and experiment with different methods of interacting with and using and leveraging Windows Live Events. Also, how neat-o would it be to be able to download all of the plans, pictures, and discussions surrounding an event and burn them to a DVD to watch with your friends next time you meet up?
  • Allowing modules. Enable people to interact with Windows Live Events as a module. As a module, you can place features, actions, or other types of updates within any other service. Also, as a module, other services can transmit information to the Live Events module (e.g. friend X has accepted the invitation to your party).

In the end, some nice User Experience (UX) and integration (barely), but the 2 big problems that I have found to be all too familiar to the majority of Microsoft’s web products (not unlike their desktop products) are:

  1. sluggish UI and UX really hurt any gains made by some of the good UI decisions, and
  2. openness — connect to and give the people a way to connect complementary services and other platforms (social networks, IM, blog, flickr, twitter, etc.)

It will be interesting to watch Windows Live Events and see what of my advice is eventually adopted and the resulting consumer responses (and their corresponding UX gains).

Enjoy!

Jeremy Horn
The Product Guy