Relationships, Knowing Knewton & Visions of July!

theproductgroup_logo_200909_thumb752
balsamiq_logo2_thumb263333
sunshine_suites_logo
RymaLogoHighRes257_thumb5222

A big thank you to everyone who made it to our latest roundtable meet-up of The Product Group, as well as to our sponsors, Balsamiq Studios, Sunshine Suites, and Ryma Technology Solutions.IMG_1785

Over the course of the night a few of the highlights were…

 

Featured Product: Knewton
exploring the product, its challenges and successes, from dashboard design to effective team management
(a big thanks to the Knewton team: Sara Petry, Brian Fitzgerald)

Building and Maintaining Relationships with Customers
from the customer strategies of popular products, Mint, Zappos, Twine, and others, to the values of surveying

The Product Group meet-ups are an opportunity for Product People (managers, strategies, marketers, etc.) to come together to meet, interact, and network in a roundtable setting. It’s awesome to meet fellow Product People in a laid-back, conversational gathering.

DSC06373If you are a Product Person who would like to have your product or methodology featured at an upcoming meetup of The Product Group, contact me.

I am looking forward to seeing everyone at our next meetup …

 

Thursday, July 1st @ 7PM
@ Pace (163 William Street, 2nd Floor, NYC)
RSVP Now!

And, stay tuned for more announcements about July’s Featured Product, OlaPic.

If you would like to attend our next meet-up, RSVP today or visit our group webpage at…

http://meetup.com/TheProductGroup

Enjoy!

Jeremy Horn

The Product Guy

P.S. Interested in becoming a sponsor or host of The Product Group? contact me.

About these ads

Twine Tied Up in Load Time

image_thumb25A company can have the best product around, but if the pages are too sluggish, if the product suffers recurring outages, if the user-product interaction is varied and inconsistent, the product’s overall Usability can, and does, suffer.

Quick-UX provides for the rapid, simple and quantifiable assessment of a product’s User Experience (UX). Among the various components that define a product’s Usability, as well as Quick-UX‘s, are Accessibility, Consistency, Recognition, Navigation, and Page Load Time.

In answering the question of Usability, "Can I use it?" the sub-category of Page Load plays an instrumental role. Page Load, often obfuscated or connected with other perceived causes of a product’s dissatisfaction, ultimately, either positively or negatively, presents an unquestionable influence on a product’s overall Usability.

Example: Poor Load Time (value = 0.0)

Based on a recent study commissioned by Akamai…

2 seconds = Page Load Time when customers become impatient

Twine is a web product that goes beyond the basic user contributed content model of more familiar sites, like Digg and Mixx, and performs semantic analysis on your contributed content and interests to help identify both related content, as well as additional information of potential interest to each active user.

00_twine-homepage

I have been a user of Twine since being accepted into the early Beta. Beginning with my initial interaction with the product, and despite the evolutions of the user interface, it is apparent that the product’s Usability has been degrading over time — most notably in the department of Page Load Time, earning Twine a Page Load Time variable value of 0.

From the inability to login due to page timeouts…

01_bad-login

… to the incredible unresponsive (or barely responsive) interfaces…

02_twine-slow-loading

10+ seconds later

03_twine-slow-loading-10sec

… Page Load Time is a present and seemingly growing issue of Usability with this product.

One set of interactions, experienced in December 2009, best exemplify the negative impact on Usability of this product experienced due to Poor Load Time. In addition to sluggish interface interactions, for example when expanding the ‘related people,’ that would leave all but the most patient of patient people to conclude the product was merely unusable/broken, was the common and (hopefully) trivial task of accepting a friend request.

04_twine-friends

From the time starting with clicking the link within the email to accept or check out the friend request, to finally accepting, many minutes of delays and frustration transpired. For every click on the inbox, every time, every action involved in the process, 3-5 seconds was spent waiting, locked in a frozen state, unable to use the product in another way, locked into the current glacial path, of click, wait, click, wait, click, wait…etc.

dali-clock-500x500

While the Twine product does have its good moments and days, performing lickety split, the Page Load Time experience is one of (increasingly) frequent and long delays as well as the inability to access and load content.

Should Do

In addition to a basic focus on reliability and duration of Page Load Time, there are other improvements that a product, such as Twine, would benefit…

  • For the times where delay is unavoidable…
    • provide better user feedback to better align the user expectations of time remaining — e.g. progress bars instead of endlessly spinning wheels, clear messaging of server timeouts and delays instead of generic ‘unable to login’ messages
    • allow for the asynchronous performing of actions within the product, so that while one action processes, other actions, by the user, can be taken and content explored

Next…

Over the next several weeks I will be providing real-world examples of Page Load Time values…

Poor Load Time (value 0) [Twitter, Twine]
Delayed Load Time (value 0.5) [Conversation Pieces]
Prompt Load Time (value 1) [Facebook]

Subscribe now (click here) to make sure you don’t miss any part of this series exploring the Usability and Page Load Time of Quick-UX, the quick and easy method of generating quantifiable and comparable metrics representing the understanding of the overall User Experience of a product, as well as other insightful posts from The Product Guy.

Enjoy, Discuss & Tweet!

Jeremy Horn
The Product Guy

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

Somewhat Less Del.icio.us

deliciouslogo_thumb3…because Delicious is synonymous with tagging online. With all of the improvements made within the latest upgrade to Delicious, the functionality and procedures surrounding tagging remain minimally and indirectly altered. Primarily, the changes to Delicious (its domain name included) were limited to desirability and usability (discussed last week), with its usefulness marginally augmented.

Lacking

There were no improvements nor innovations of any parts related to tagging. I look forward to seeing a more innovative stance from Delicious and seeing resolute efforts made to…

  • Encourage and facilitate more tagging,
  • Add structure and order to the tagging process, and
  • Improve the searching, exploration, and discovery process.

By no means are any of these (Delicious) next steps trivial, but rather they are steps (most specifically related to the Usefulness of the product) that will need to be continually presented and refined, by whichever company that desires to be a leader in describing the context and content of the web.

Encourage

Tagging is critical to Delicious. Central to success for a user and to the Delicious community- at- large, is the frequent and descriptive usage of tags. With less tagging, or less accurate tagging, users will have a more difficult time locating older content. With more tagging, users are able to better organize, filter, and find saved and new information. With more tagging, the community will be able to better understand the extent of the existing system-wide knowledge, and how it is evolving, as well as the potential it has for impacting themselves.

Today, Delicious encourages tagging by way of simple user interface presentations, inline editing…

01_inline_edit

…and the display of Popular tags and Recommended tags within the full-screen edit of new content…

02_recommended

In addition, the new Sidebars, by allowing for easier, to both modify and view, access of tags, also facilitate their bundling and usage.

03_sidebars

In some sense Delicious has made tagging a little bit easier to understand, read, and do. Substantial in encouraging any sort of online activity is the simplification of that activity. In this sense, there are many avenues to explore. Some of them being…

Make tag suggestions based on the actual content of the new destination page being submitted to Delicious. Then, let the user select tags they feel are appropriate — it is much easier to click a suggestion, than think up a word and type it (e.g. corrected spelling, finer-tuned additions, alternate similar tags). More information can be coaxed from the user with the simple encouragement via intelligent suggestions, which can be appended to a new (or existing) entry with the click of the mouse.

Infer deeper meta information, again based, on the context of the target page or tags already typed. For example, if the user is typing “New York, ” suggest “state” and “city.” Continuing this example, should the user select “city,” additional geo-tags can then be automatically appended.

Identify potential sub-tags based on the context of the already entered tags, leveraging the power of the crowd, and offer suggestions of tags that are frequently related. If an individual enters the tag “person,” suggest some common types of people. If someone types “person” and “moon,” Delicious may identify the other related tags like “scientist,” “astronaut,” and “astronomer.”

Encourage alternate or corrected tags (spelling, more common or specific descriptors)

Add

The most obvious injection of structure is introduced to the tagging process within the latest update via the orderless tags of the Tag Bar…

04_tagbar

From more structure comes a reduction in the information / content noise. Presenting just a little bit of structure, or means of organization, has a significant impact on the system utility – from the introduction of a minimally common way of thinking and organizing to helping people focus their tagging descriptions and find new information within different, and possibly foreign, domains.

Simple personal structure, like folders and private tags, would have a greater impact upon this goal — and for those people, and there are more than a handful that use multiple Delicious accounts to organize their bookmarks, they would be able to use a single account to accomplish everything (and probably more, especially without the burden of maintaining multiple accounts).

On the non-personal, i.e. public, additions of increased structure, merely a level or two of hierarchical guidance (e.g. tag categories) could exist to help the user quickly zero in on an accurate description of the new content directly resulting in reducing the “strain” on the user to figure out the right tags to assign, as well as letting them come back later and add more details as they occur to the user, all while still being able to filter and zero back in on the item in the future.

Improve

The latest upgrade added the ability for context-based searching and Tag Bar usability enhancements in an effort to improve the searching, exploration, and knowledge discovery processes.

05_search

In the end, this upgrade was quite incremental in nature in so far as the purpose of exploration and discovery are concerned. Here too, knowledge discovery and searching can greatly benefit from an increase in simplification.

Instead of entering, or guessing, one tag at a time, to browse or find content, semi-hierarchical tag clusters, representing concepts and groups of varying scope, could be automatically generated. Individuals would be able to gain broader understanding of the current state of the Delicious environment, the coalescing of tags and ideas, and use them as an alternate means of drilling down.

Another method of simplifying the discovery and search actions can be done through the offering of suggestions for alternate and additional words related to the tags being entered for the search (just like those suggestions that can be made when submitting new content).

Improving the exploration and discovery processes will directly lead to the increased utility and usefulness of Delicious.

…and…

Since Delicious had been acquired by Yahoo (Dec. 2005) change has come very slowly to the product and created a plethora of opportunities within the tagging (and semantic tagging) space that have yet to be fully taken advantage of — but, eventually, either Delicious will choose to lead or other companies, like flickr or twine.

Delicious accomplished a good deal in the way of improving the tagging experience. Now they need to continue, and evolve the functionality of Delicious, (the tagging) and improve the usefulness — lest the mantel for tagging leadership be taken up by other innovators, like flickr, twine, or another up-and-comer.

Share & Enjoy!

Jeremy Horn
The Product Guy

Add to Social Bookmarks: Stumbleupon Del.ico.us Furl Reddit Magnolia Google Add to Mixx!