Archive for the 'Online Shopping' Category

Should A Website Design Show Its Precious Algorithm?

One of the great things about web2.0 is the use of social power to create product recommendations. For example, Amazon.com recommends books from similar authors and Last.fm recommends similar artists.

It’s more than magic

Behind those recommendations there are [usually] complicated algorithms looking for recommendations patterns and similarities among users.

In my opinion there are 3 important issues regarding recommendation algorithms:

1. The more users a website has, the better the recommendations.

2. The more users a website has, the higher the calculation price,

3. Should a website show users how the algorithm works?

There are different approaches  regarding the last point. Should the algorithm be kept as something precious that other websites should not access? An algorithm could improve its performance if the user gets at least some information about the way it works (see Amazon example). On the other side, letting users know about the algorithm could make the recommendation system hackable and someone could take advantage of that to promote his products.

This issues should be kept in mind at the moment to decide to show information or questions to improve the algorithm:

1. Making questions to users could make the system hackable (negative).

2. Hiding those questions would make a website look smarter and additional usability problems could be avoided (positive).

3. Not making those questions could decrease recommendation quality (negative).

Below there are some examples of recommendation algorithms embedded in websites design. 

The Amazon.com approach

Amazon show recommendations everywhere, they do that also as a marketing tool because they know that users love recommendations.  Amazon is so good recommending because they have a huge base of customers buying all those products to recommend. They also have a good algorithm but they don’t hide it as a precious secret, note "These recommendations are based on items you own".

Amazon Algorithm A

 

This is very important: Amazon is recommending a book because the user bought a "similar" one before. Amazon knows that recommending this way is dangerous and it offers a way to fix it.

Amazon Algorithm B

 

Here there is a pop-up window to solve the potential problem. Amazon might be recommending a book because the user bought a similar one, but that one could have been a gift for another person.

Amazon Algorithm C

 

Amazon is not only showing a part of how its algorithm works but it also asks users for input to improve results. Here there is another important thing to check: is it OK to ask users questions to improve website recommendation algorithms or should these algorithms be intelligent enough to avoid bothering users?

Amazon Algorithm D

 

The Amazon recommendation algorithm in action:

Amazon Algorithm E

 

The Last.fm approach

Last.fm, the music recommendation website, adopted a different design solution. At it, users don’t know where the recommendations come from. One might guess but nobody really knows if those artists are there because the user likes other similar artists or because someone is paying to push artists into that list. There is no message like "we recommend Shakira because you like Beyonce".

A valid approach? Last.fm makes a good job recommending music without disturbing users. On the other side this kind of state of user ignorance could be translated into a drop in trust.

Last.fm Recommendations A

 

Last.fm also has a radio set for each user with special recommendations. Here the recommendation algorithm behavior could be easier guessed, the player has controls to "love" or to ban a song. There is a serious problem here, once you ban a son there is no way back.

Last.fm Recommendations B  

 

StumbleUpon

StumbleUpon is a web browser plugin that let users discover new websites based on recommendations and ratings done by other users and the user himself. StumbleUpon works fine and improves the recommendation quality as the user rates more websites.

Like Last.fm, StumbleUpon also decided not to show the user why a particular website was recommended to him.  In this case the algorithm might be too complicated and [I guess] they decided to improve usability taking out additional information. But keep in mind that a lack of information also negatively impacts on usability and trust.

StumbleUpon Bar Recommendation Algorithm

 

External Resources About Recommendation Systems

- Amazon.com Recommendations: Item-to-Item Collaborative Filtering (PDF file)

- How Netflix Recommendations Works

- Recommender Systems on Wikipedia

Popularity: 62% [?]

Designing a Checkout Process: 8 Rules, 7 Examples

Users usually need to be guided in order to finish a task. Designing a process funnel right will keep your visitors in the process and will make them finish the task they want to commit. This tasks could be as important as the Checkout Process, I will focus on this particular one.

Here there are 8 tips to improve usability during a checkout process:

1. Keep it short. If the process has too many steps users will be scared and will probably leave without finishing it.

2. Keep it long. If the process is too short, well, it’s not a process. Sometimes it’s better to divide tasks that could be presented in one page into smaller steps. Keeping every step short gives a sense of simplicity.

3. Progress bar. It is very important for the user to have information about how long the process it will be. Maybe your process is not that long, but if you don’t show that to the user, she might decide that is not worth enough to finish with it.

4. Back button. Give users the possibility to go backwards to check what they filled in the previous step.

5. Unnecessary steps. Give users the chance to skip steps they don’t need (e.g. the Amazon "Gift-Wrap" step).

6. Online help. Use floating windows or other online help to solve problems without taking users out of the process. Remember not to distract users.

7. Next step button. Make this button or link highly visible.

8. Make clear that the process is finished, if not you could have a lot of users contacting your customer service, which could become extremely expensive.

I would like to show you 7 examples I took from different websites. I focus on the information the user should get to make important decisions just before or during a checkout process funnel:

 

Amazon’s design shows a shopping cart that seems to be rolling through the whole process. Users know what to expect as the steps have clear names, displayed from the beginning.

Amazon Process Funel Design

 

The Starbucks Store shows very clear steps and the name of each one in a prominent position (e.g. Sign In). Some usability tests show that users might prefer a longer process with smaller steps. Good naming for each step should represent the user mental model, something like what the people are used to when they buy off-line.

Starbucks Checkout Process Design

 

Buy.com has a sleek checkout process status information design. I like the red arrow clearly showing the actual step. Steps are clearly indicated and the end is also coherently indicated with an "Order Complete".

Buy.com Checkout Process Design 

 

Toy"R"Us checkout process is not going to prevent users to finish the purchase but it could create some confusion. Notice that the difference between the step "Addresses" and "Shipping" could be misunderstood and users have to go inside the step and read instructions in order to understand what are they about. Using "payments", the plural form, is not standard and could add even more worries.

Toyrus Checkout Process Design

 

The beginning of the checkout process at Petco adds some extra complexity. They require an extra decision to be made by the user: "check out", "Google Checkout" or "International Checkout"… I would avoid so many options.

Petco Checkout Process Design

 

Google Checkout has a special design. Coming from an online music store I landed at the Google Checkout page, at this point is not possible to delete products or change quantities. The whole information is displayed in a single page, including product to be paid, payment information, shipping address and term of service. Maybe the aim of this was to try to make the process short but in my opinion this design fires back and scare people, making users think that the whole form is too long (this happens to the first-time Google Checkout users).

Google Checkout Process Design

 

The PayPal process does not offer any information about how long the process it will be.

Paypal Checkout Process Design

 

At the end, once the user logins, the process is very short (if the user has an account and bought before with Paypal). Unfortunately, before the login the user could not guess how long the process could be. Something like

1. Login, 2. Confirm and Finish

in the login page wold give users the feeling that the process is really short and easy.

Paypal Process Funel Design 

 

Popularity: 33% [?]

Next Page »