Aug 30 2010

Basic Principle #1 of 9

People love lists. Lists of things like “…Myths”, “Dos & Don’ts of…” and of course my favorite “10 Ways to Get Rich Quick…”. So, on that note I’ll present the first of a list of 9 principles shamelessly derived from a favorite book of mine called GUI Bloopers 2.0.

Basic Principle #1

Focus on the Users and their Tasks, not on the Technology.

This is unfortunately far too vague, open and susceptible to interpretation.

What does “focus on the users and their tasks mean”? Lets pose several questions that will help us understand how to answer that.

  • For whom is the software being designed? Who are the intended users? Who are the intended customers (not necessarily the users)?
  • What is the software for? What activity is it intended to support? What problems will it help users solve? What value will it provide?
  • What problems do the intended users have now? What do they like and dislike about the way they work now?
  • What are the skills and knowledge of the intended users? Are they motivated to learn? How? Are there different classes of users, with different skills, knowledge, and motivation?
  • How do users conceptualize the data that the software will manage?
  • What are the intended users’ preferred ways of working? How will the software fit into those ways? How will it change them?

The only way to answers these tough but extremely time and money saving questions is for the development team to make a focused and concerted effort to do so. This costs time and money but it is crucial, because the cost of neglecting to answer these questions is much, much higher.

I recommend creating a requirements definition document to facilitate answering these questions.

Next upBasic Principe #2: Consider Function First, Presentation Later


Aug 24 2010

5 Web Page Title Tips

Page titles are one the most powerful on-site search engine ranking factors that we have control over but are often neglected by website owners.

What are web page titles? A web page title is string of text placed between the opening and closing <title> tags  inside the <head> tag of an HTML document. This title is important for more than just SEO, it shows up in the title menu in the browser window and in the browser tabs. Page titles are very handy for at-a-glance identification.

Here’s some examples:

Web Page Titles

This is how Google displays the <title> after searching for “seo tips remember”.

How Google Displays Web Page Titles in Search Results

1. Have a Title

Don’t be one of those websites plagued with the “I was developed by a high-school student” stigma flaunting the infamous “untitled document” page title. Go ahead, do a search on Google for “untitled document”.

Not having a title ensures search results become meaningless very quickly. Page titles are helpful for those good Google spiders out there (web robots) that facilitate the indexing of your site.

2. Too long or Too short

Google can display up to 70 characters in their search engine results page (SERP). Be sure to take advantage of that but don’t go crazy. Remember the more keywords crammed into the title the more diluted they become. Having too many keywords in the page title may lead to keyword cannibalization (we’ll define that in a moment).

Terms that appear first carry more weight. For example, if a web page talks about how to repair a broken hard drive on a Dell XPS laptop and the main keywords are “repair”, “Dell”, and “XPS”, a title like:

<title>DIY: How to Repair a Broken Hard Drive on a Dell XPS Laptop</title>

Can be revised to:

<title>Repair a Dell XPS Laptop’s Broken Hard Drive<title>

Remember, users want information quickly so try to be considerate and construct meaningful page titles.

3 Keyword Cannibalization

This refers to a page title that is jam-packed with too many keywords. Keyword jam-packing is a tactic that a few SEO consultants use to improve their clients’ search engine rankings. Not only does this affect your search engine ranking’s effectiveness, but it also can be the reason we sometimes see non-relevant web pages ranking highly for a specific keyword.

Repeating keywords in pages may not help for two reasons:

  1. Irrelevant web pages may be picked up by the search engines, but will have high bounce rates as it doesn’t convert effectively due to the fact that the page isn’t what the searcher is looking for
  2. It violates Google’s mantra of “Don’t be evil” (which is slightly in question these days)

4. Using the Company/Site Name in all Web pages

Give consideration to those 70 characters that reside in the page title we spoke of earlier. Many websites tend to include their business name in the title, many of which can be quite lengthy.  What may be worse and quite unnecessary is placing the company name first on every page.

For example:

<title>ACME Exporting/Importing Company, LLC: Export Surfboards to Hawaii<title>

That’s 37 more characters than is necessary. Search engine ranking might be better if was simplified:

<title>Export Surfboards to Hawaii</title>

It makes sense to display the company name on the homepage, contact page and about pages but avoid them in the content pages.

5. Don’t Duplicate Page Titles

This makes it difficult to ascertain which page is which when they‘re  all displayed in the search engine results page (not to mention the confusion to be had within the browsers itself…just imagine all those tabs having the same title!). Web pages should be unique, thus logically all page titles should also be unique.


Aug 16 2010

Perceived Affordances & Web Conventions

Never heard of that word before have you? Well, “Affordance” refers to what you can to an object. For example, on the web a checkbox affords turning on and off (checking and un-checking) and a slider affords moving up or down, or side to side. More importantly, on the web are “Perceived Affordances”, or actions you understand just by looking at the object before you start interacting with it.

Perceived affordances are critical in screen UI design. Why? The entire screen is made up of pixels and those pixels afford clicking on, hovering over and dragging etc. Potentially there can be many objects displayed in a given UI but users generally don’t have time for a game of mine sweeper, clicking around anticipating some event to be triggered. Okay, my kids love to click on screens and explore what happens, but let’s assume a more typical user base here.

Drag-and-drop designs are notorious offenders when it’s not readily apparent that something can be dragged or where that something can be dropped (or what happens after it’s been dropped). Some people can become confused when that intimidating ‘arrows pointing everywhere, OMG what does it mean?!’ cursor (commonly known as the move cursor) shows itself.
Contrast a drag and drop control to a checkbox or a radio button. They make it painfully obvious what can be clicked.

Web conventions play a large role in how web designers use objects to increase the perceived affordances of graphics or objects. Often, designers feel pressured (are pressured) to innovate new UI controls to represent actions that are far better discerned using simple and established web conventions. Sometimes, perceived affordance is sacrificed for a snazzy or creative method for accomplishing a given task. Usually (not always), but usually, this ends badly for both the user and the company as it can mean lost revenue due to low checkout conversions or a high bounce rate.

When faced with a decision to create something that is innovative and edgy versus something that is ubiquitous (we designers can easily succumb to temptation), I would recommend asking yourself to identify the perceived affordances of both UI possibilities and make your choice accordingly. There are many factors that play a part in how acceptable and successful the use of innovative design is as opposed to a web convention but I’d take my chances with a web convention over an innovative UI solution any day (okay…most days).

Let me give you some examples of good perceived affordances:

Good Perceived Affordances

Amazon Add to Shopping Cart

Amazon Add to Shopping Cart Screenshot

Amazon Add to Shopping Cart Button

Amazon Add to Shopping Cart Button

As demonstrated above, Amazon.com uses many design elements to generate high perceived affordance of their Add to Shopping Cart button, including use of:

  • Strongly contrasting yellow button color
  • Only use of that yellow color on the page
  • Heavy outline border around button
  • Round strongly contrasting icon of shopping basket
  • Text in button Add to Shopping Cart
  • Larger font for button text
  • Elongated shape, round on left side, squared on right side
  • Gradient fill in top of button to visually mimic 3-D shape
  • Dark blue background color for surrounding box

-source: http://www.usefulusability.com/increase-your-usability-and-website-roi-with-perceived-affordance/

Ebay Scree

Ebay Screen

Ebay Buy it now

Ebay Buy it Now Button

For eBay, the Buy It Now button uses multiple design elements to effectively communicate perceived affordance:

  • Strongly contrasting blue button color
  • Only use of that blue button color on the page
  • Largest sized button on page
  • Text in button Buy It Now
  • Larger font for button text
  • Strong contrasting colors, white text on blue background
  • Dark gray background color for surrounding box

-source: http://www.usefulusability.com/increase-your-usability-and-website-roi-with-perceived-affordance/

Bad or No Perceived Affordances

eTolys Featured Gift

eTolys Featured Gift

Etoys Featured Gift

Etoys Featured Gift

In this example, the prominently displayed Featured Gift and photo of the toy seem to indicate that more information about the toy might be available by clicking, but where?  Web site visitors who come across the display are left wondering, because no clear action button seems available for this toy.

A common tool many web site designers use is to make the image of the product clickable.  But that is not the case here.

In fact, there is no action available, the image of the toy is not clickable, nor is the heading Featured Gift.  There is no way to navigate to the featured toy using the visual designs offered, thus the connection with a false affordance.

There are many types of designs that can lead to false affordance, some of the more common being:

  • Objects that look like buttons, but are not
  • Photos of objects that are not links, especially if place with photos that are links
  • Placing a blue outline around an image or link, yet no link is present
  • Underlined text that is not a link
  • Use of blue in text that is not a link
  • Form data entry fields that are not active

-source: http://www.usefulusability.com/increase-your-usability-and-website-roi-with-perceived-affordance/

Dancing Bear Screen

Dancing Bear Screen

Dancing Bear Checkout Now

Dancing Bear Checkout Now

The example above demonstrates a site that provides web site visitors with a display of products available for purchase.  However, the function associated with Checkout Now in this case a link to an online order form – is poorly displayed because it has minimal visual clues as to its function, and thus has low perceived affordance.

Among the perceived affordance problems with the Checkout Now button are:

  • No button shape around the text
  • Yellow text color is not a strong contrast against the white page
  • No underline when mouse rolls over text
  • Text in button visually close to Back to results text
  • Missing a background color to call attention to location
  • Upper left location not typically associated with continue action

-source: http://www.usefulusability.com/increase-your-usability-and-website-roi-with-perceived-affordance/


Aug 9 2010

A Dash of Personality

Is it enough for a website to be usable? Usability is becoming more of a buzz word these days and that’s a good thing. Businesses and website start-ups are realizing the value in offering their customers good experiences. Customers are realizing they don’t have to put up with un-usable sites (Jakob Nielsons’ law: “Users spend most of their time on other sites.”) and can spend their money and time elsewhere.

Are we (web designers and friends) doing enough to ensure the “user” is having a memorable experience? When was the last time you smiled or laughed (out loud) while using a website or online service?

I visit woot.com on a regular basis. They typically have decent deals on gadgets and other miscellaneous stuff that I convince myself I need. Some days the product is not particularly alluring but the description always is. Woot’s content writers are amazingly creative and unconventional. But that’s not the point. The point is this; each visit elicits an emotion. I laugh while reading their product descriptions. Even Woot’s product statistics are worded humorously (e.g.; “speed to first woot 0m 46.157s” or “First Sucker: usernameOfFirstSucker”). Because each visit usually procures an emotion from me I remember it and I come back for more.

I re-visit woot because it’s usually a pleasant experience. Woot is sprinkled with personality. We remember those things that instill powerful emotions within us. In his book, The Alchemies of The Mind, Jon Elster states that “Emotions matter because if we did not have them nothing else would matter. Creatures without emotion would have no reason for living, nor, for that matter, for committing suicide. Emotions are the stuff of life…. Emotions are the most important bond or glue that links us to others…. Objectively, emotions matter because many forms of human behavior would be unintelligible if we did not see them through the prism of emotion.”

Now, I’m not saying that I had a ‘powerful emotional experience’ by visiting woot…c’mon…I’m not a weirdo. But using emotion in web design can create a sort of bond with your users that couldn’t otherwise be created. This bond can create a desire to come back and visit again. It can create loyalty and a wider customer base as people share their experiences with others.

Let’s take a look at two 404 pages. The first one is dry, boring and almost robotic sounding. As you read it you probably heard yourself talking like a monotone robot. This excerpt is from an actual project I’m currently working on. I originally proposed text that would be helpful and (possibly) bring a smile to the users’ face should they be presented with it but my project manager vetoed and we got this:

Error 404 Dry and Boring

Error 404. Not Found. The document that has been requested either no longer exists, or has never existed on the server. Visit Exemplar Finance's contact page if you need support.

Contrast the above with Woot’s 404 page.

Woot's Error 404

Woot's Error 404

Which one is not only more usable but almost anthropomorphizing itself? Typically it’s very frustrating to find yourself staring at a 404 page but Woot aims to reduce that frustration by acknowledging the user as a Human and in turn responding like one. The first one carries an almost accusatory feel while Woot’s is much gentler in letting you know what happened, why, and what you can do about it.

An error 404 page is not commonly encountered these days on professionally done sites. But Woot has taken the time to make even the most uncommon encounters pleasant ones.

We need to think about perception and not just composition. If we can answer a few vital questions about how the users are feeling then we can begin working out how to better please them.

As one speaker at the Future of Web Design in London put it: “Designing a website to be usable is like baking a cake to be edible. It’s simply not enough. A usable website should be the minimum requirement; it should go without saying that a website should be absolutely usable. It’s time to look beyond that.”

Just because something is functional doesn’t mean it’s any good. Let’s look past usability and think about our users emotionally.


Aug 2 2010

10 Most Common Misconceptions About User Experience Design

I was hired as a web designer almost 5 years ago. Back then I was mainly tasked with creating graphics and redesigning homepages, basically a “pixel pusher”. Only recently have I realized that I do a lot more (and am expected to do a lot more) than “push pixels” and make things look “pretty”. I don’t think many people (my employer included) realizes the many roles I try to fill but the following titles have all been applicable in some degree at one time or another: graphic artist, information architect, user experience architect, interaction designer, usability engineer, design analyst.

I have experienced frustration like many others when what I do isn’t recognized as “valuable” or “worth the time and money”. Time spent dedicated to a sites’ UX has been proven to have a very high ROI. However, nowadays businesses are only slowly realizing this and are even slower to act on it. What we (again, UX people) do is quite valuable and we are selflessly passionate about it.

I’m not whining or complaining or want a gold star on my forehead. Rather, I simply wish to educate people regarding what we (UX people) do and that it is a rapidly developing industry that can and does have a dramatic and direct influence on a website’s success.

I intended to write my own definition of what UX (sprinkled with my own experiences) is about, however, this article from Whitney Hess cleverly describes what UX is NOT, and therefore one can get a better idea of what UX is. I quote her article in full and inject my own thoughts throughout.You’ll find my thoughts are italicized and begin after a dash “–“.

Begin Article:

Whitney Hess is an independent user experience designer, writer and consultant based in New York City. She authors the blog Pleasure and Pain.

When I tell people that I am a user experience designer, I usually get a blank stare. I try to follow it up quickly by saying that I make stuff easy and pleasurable to use. That’s the repeatable one-liner, but it’s a gross oversimplification and isn’t doing me any favors.

The term “user experience” or UX has been getting a lot of play, but many businesses are confused about what it actually is and how crucial it is to their success.

I asked some of the most influential and widely respected practitioners in UX what they consider to be the biggest misperceptions of what we do. The result is a top 10 list to debunk the myths. Read it, learn it, live it.

User experience design is NOT


1. …user interface design


It’s not uncommon to confuse “user experience” with “user interface” — after all it’s a big part of what users interact with while experiencing digital products and services. But the UI is just one piece of the puzzle.

“Interface is a component of user experience, but there’s much more,” says Peter Merholz, founding partner and president of Adaptive Path. Christian Crumlish, curator of the Yahoo! Design Pattern Library, explains that design “isn’t about cosmetics, pixel-pushing, and button placement. It’s holistic and it’s everyone’s concern, not just the realm of ‘artistic’ types.”

Dan Saffer, founder and principal at Kicker Studio, agrees that it’s common for design to be mistaken for being solely about decoration or styling. “I’ve had clients tell me not to worry about what their strategy is,” he says, “because why would a designer care about that? UX is more than just skin deep.”

I too have endured meetings where representing the UX guy I’m completely ignored or never called upon for input until the aesthetics of the site is brought up. You’re UX guy benefits by understanding the business model. We try to match the goals of the business with the goals of the user! The more we know the more effective we can be.


2. …a step in the process


It is the process. In order to create a great experience for your users, not just design something that we’d like to use, we need to keep listening and iterating. It doesn’t have to be a rigid process, but it does need to exist.

“User experience design isn’t a checkbox,” says Liz Danzico, an independent user experience consultant and chairperson of the new MFA in Interaction Design program at the School of Visual Arts. “You don’t do it and then move on. It needs to be integrated into everything you do.”

Dan Brown, co-founder and principal at EightShapes notes, “Most [clients] expect experience design to be a discrete activity, solving all their problems with a single functional specification or a single research study. It must be an ongoing effort, a process of continually learning about users, responding to their behaviors, and evolving the product or service.”

I would love to tell you that I’ve worked on numerous projects where we “respond to user behavior” regarding a particular interface. All too often we’re busy putting out fires elsewhere and our project managers are unwilling to devote time and energy into something that is already built and working (or at least working in their eyes). Good UX is never “finished”.


3. …about technology


User experience isn’t even about technology, says Mario Bourque, manager of information architecture and content management at Trapeze Group. “It’s about how we live. It’s about everything we do; it surrounds us.”

Like a painter uses paint to communicate concepts and emotions, user experience designers use technology to help people accomplish their goals. But the primary objective is to help people, not to make great technology.

“User experience design is not limited to the confines of the computer. It doesn’t even need a screen,” argues Bill DeRouchey, director of interaction design at Ziba Design. “User experience is any interaction with any product, any artifact, any system.”

Really, a user experience designer could help to improve a person’s experience with just about anything — a doorknob, a faucet, a shopping cart. We just don’t typically refer to the people using those things as “users,” but they are.

Think about that for a moment…Yeah, I really should be making a lot more money.


4. …just about usability


“People often think that [UX design] is a way to make products that suck into products that don’t suck by dedicating resources to the product’s design,” says Chris Fahey, founding partner and principal of Behavior. Making stuff easy and intuitive is far from our only goal. In order to get people to change their behavior, we need to create stuff they want to use, too.

David Malouf, professor of interaction design at Savannah College of Art & Design, explains that “while usability is important, its focus on efficiency and effectiveness seems to blur the other important factors in UX, which include learnability and visceral and behavioral emotional responses to the products and services we use.” Not everything has to be dead simple if it can be easily learned, and it’s critical that the thing be appealing or people might never interact with it in the first place.

“Usability is not a synecdoche for UX,” asserts Will Evans, principal user experience architect at Semantic Foundry. He points to Peter Morville’s UX honeycomb, which in addition to usable, recognizes useful, desirable, accessible, credible, findable, and ultimately valuable as the essential facets of user experience.

Bonus points if you knew what the word “synecdoche” meant…more points if you knew how to correctly pronounce it. Thank God for Webster’s online dictionary eh?


5. …just about the user


Russ Unger, experience design strategist, likes to say that the biggest misconception of UX design is the “U.” “There are a set of business objectives that are needing to be met—and we’re designing to that, as well,” he explains. “We just can’t always do what is best for the users. We have to try to make sure that we are presenting an overall experience that can meet as many goals and needs as possible for the business and the users.”

As user experience designers we have to find the sweet spot between the user’s needs and the business goals, and furthermore ensure that the design is on brand.

Don’t sell your UX guy short. He may just surprise you by coming up with some creative (and lucrative) idea because he was involved in that boring meeting where you talked about your business model.


6. …expensive


Every project requires a custom-tailored approach based on the business’s available resources, capabilities, timeline, and budget, and a whole slew of real-world constraints. But that doesn’t always mean that it needs to be costly or take forever.

Steve Baty, principal and user experience strategist at Meld Consulting, combats the fallacy that UX design adds too much time to a project. “Sometimes a fully-fledged, formal UCD process may not be the best thing to try first time,” he says. “It’s extremely important – and totally possible no matter where you’re working or when you arrive on a project – to make small improvements to both the project and the product by introducing some user experience design techniques.”

“People cling to things like personas, user research, drawing comics, etc.,” notes Saffer. “In reality the best designers have a toolbox of options, picking and choosing methods for each project what makes sense for that particular project.”

Some (even a teensy weensy bit of) usability testing is better than none. Again, the ROI on usability testing is extremely high.


7. …easy


Just because we know how to conduct some cool and useful activities and you know your business really well doesn’t mean that this whole process is a breeze. And cutting corners on some important steps is a recipe for disaster.

Saffer maintains that a misconception “as common among designers as it is among clients, is that there is one secret method that will solve all their design problems.”

A trap that a lot of companies fall into is in thinking that they are their own end users. Erin Malone, principal at Tangible UX, finds that both product managers and programmers believe they will create the experience as they build it. “UX designers are caught in the middle trying to speak the business language and the developer language to justify why we need to do our jobs and why it’s important to success.”

If you make assumptions about the people you expect to use your product or service — who they are, how they behave, what makes them tick — you’ll probably always be wrong. But take the time to get to know them, and hire the appropriate person to facilitate the process, and you can ensure you’ll get it right.

I’ll never forget a response I received from a project manager after I pointed out several usability concerns I had with a particular interface. I plainly told him that we would be “punishing our users if we implemented the proposed interface design”. He responded thus: “Our users are too stupid to know their being punished”. Don’t forget to remind your key stakeholders that the design you’re working on is not for them but for their customers. You know, the people who make them money.


8. …the role of one person or department


User experience designers are liaisons, not subject matter experts, doctors or any type of magical beings. We don’t have a set of best practices that we can robotically implement, nor do we have all of the answers. Our greatest skill is that we know how to listen. While we can help evangelize the most effective process within your organization, it’s ultimately up to all members of the business to make it a success.

“User experience isn’t just the responsibility of a department or a person,” says Livia Labate, principal of information architecture and user experience at Comcast Interactive Media. “That compartmentalist view of UX is evidence that it is not part of the organizational culture and hints to teams not having a common goal or vision for the experience they should deliver collectively.”

Malone highlights the fact that there are many different breeds of practitioners that fall within the user experience umbrella. “We, as an industry, have not done a good job of separating out specialties and roles with enough unique language so that clients and businesses get that they need to hire (on staff or consultant) different types of people at different points in a project lifecycle.”

I disagree, we are magical beings.


9. …a single discipline


The truth is that we’re all still very new at this. Louis Rosenfeld, publisher at Rosenfeld Media, publishing books on user experience design, and co-author of the seminal 2002 book Information Architecture for the World Wide Web argues that user experience may not yet even be a discipline. “It may not even be a community just yet,” he asserts. “At best, it’s a common awareness, a thread that ties together people from different disciplines who care about good design, and who realize that today’s increasingly complex design challenges require the synthesis of different varieties of design expertise.”

We have proliferation of nebulous titles: information architect, user experience architect, interaction designer, usability engineer, design analyst, and on and on. And they don’t mean the same thing to every person or company.

Different people specialize in different parts of the process. Some UX practitioners focus on a specific technique, like Indi Young and mental models, or a single challenge, like Luke Wroblewski and web forms, or a focused activity, like Steve Krug and usability testing. Just like you wouldn’t go to a cardiologist to heal your broken foot, don’t expect any professional in the realm of user experience to accomplish everything you need.


10. …a choice


For those of you who think you don’t really need a user experience designer, keep this in mind: “Nobody wants to believe that what they are offering is of poor-quality or deficient,” says Kaleem Khan, an independent UX consultant, “because nobody sets out to achieve a bad design as a goal. It’s always a risk. Bad designs and bad experiences happen.”

Jared Spool, founding principal and CEO at User Interface Engineering (UIE), the world’s largest usability research firm, has done extensive investigation on the qualities of the satisfied and successful product teams. Simply put, the most common flaw he has found is that companies think “good experience design is an add-on, not a base requirement.”

Josh Porter, formerly of UIE and now principal at Bokardo Design, echoes Spool when he says, “The biggest misconception is that [companies] have a choice to invest in their user’s experience. To survive, they don’t.”


Looking forward


2009 is going to be a year of scaling back, but let it also be a call for pragmatism. It’s time to adopt more streamlined, smart, progressive and effective practices. We’ve reached a level of technological maturity where functional just isn’t good enough.

It’s how we engage people and the respect and value we provide to them that will separate the wheat from the chaff. Which side will you be on?


Jul 29 2010

Die Sign-up Form, Die!

We’ve all been there. You’re told of a great web service from a trusted friend. The web service you’ve heard so much about promises to be innovative and useable. You arrive at their web site hoping to experience something grand, you click their “Get Started Now” button and then you see it. The dreaded sign-up form.

Several things happen next. First, you curse. Next, you immediately start trying to find a way to circumvent the form, you start thinking to yourself “I wonder if Joe would let me use his credentials so I don’t have to fill out this blasted form…” or “Great, more fake credentials I’ll have to keep track of…”. Then you realize that while you would prefer not to divulge your private information to yet another online service you’re reminded that all those “We care about your privacy and won’t share you information with anyone…blah blah blah” is really bullshit and even your next door neighbor knows your social security number, the names of your last 18 pets and even what city you proposed to your 3rd wife in. You give in, embark on those eager blank textbox fields and glaze over as the password strength meter grows into a giant happy smiley face. Consigned to the next 8 years of constantly deleting this web site’s newsletter from your inbox and vainly pressing the “Unsubscribe” button in their “You’re a valued customer…” emails you finally begin using their web service.

As Luke Wroblewski put it “We can do better. In fact, I believe we can get people engaged with digital services in a way that tells them how such services work and why they should care enough to use them. I also believe we can do this without explicitly making them fill out a sign-up form as a first step.”

Gradual engagement is like a free test-drive for online web services. Rather than tout what your web service can do, why not provide your potential customers with a few lightweight interactions and collect the necessary information much less painfully while they use it.

Contrast the aforementioned web service experience with another online family tree service called “Geni”. The first thing potential customers see is not an annoying registration form but a call to action that immediately has them using their product. Geni makes it clear on their homepage what they offer so you can get started making a family tree by offering your name and email address. Next, you can add your parents, their siblings or your siblings etc. While you were at it Geni sent you an email with your username and password so can get back to your family tree at anytime.

Geni's Homepage
Geni’s Homepage
Adding siblings through Geni
Adding family members through Geni

You may be thinking “Hey, they asked the customer for their name and e-mail address first!” Gradual engagement doesn’t mean that you have to hand over your entire product and then cross your fingers that they’ll sign up. It does mean that you gradually engage them in using your product while presenting them with form fields that are reasonable to collect during a particular stage of the interaction.

Through gradual engagement customers can understand the value of a web service without being required to reluctantly and may I add begrudgingly fork over their personal and private information first. In Geni’s case gradual engagement has given them over 5 million profiles in 5 months. Not bad.

It is important to note that because the customer didn’t explicitly create an account with that web service it may leave some confused about whether they have an account or not. Such web services need to provide an easy way for people to access their information if they didn’t see or chose to ignore the email sent to them regarding their account information.

Wondering if gradual engagement can be implemented effectively for your web service? First, think about how a series of lightweight interactions with your service can show a potential customer how they can use your product and why they should care. Your customers won’t be gradually engaged by you asking them for their information one sign-up form field at a time in a wizard-like style.

Points to Consider if you’re planning on killing sign-up forms and using gradual engagement for you next online service:

  1. When visualizing the customers’ initial experience with your web service think about how you can get them to utilize it rather than collecting information
  2. If you do employ gradual engagement ensure the customer can clearly see how they can use your service and show them why they should care.
  3. If you auto-generate accounts provide a clear way to access their information. Many customers will not realize an account exists for them.
  4. Avoid gradual engagement solutions that merely gradually engage them in form completion.

Jul 28 2010

UX Related Books

The following is a list of UX related books we recommend and either want or have read.

Steve Krug's Don't Make Me Think Steve Krug’s “Don’t Make Me Think“A Common Sense Approach to Web Usability.

Rocket Surgery Made Easy  The Do-It-Yourself Guide to Finding and Fixing Usability Problems Rocket Surgery Made Easy“. The Do-It-Yourself Guide to Finding and Fixing Usability Problems. Nine years after writing Don’t Make Me Think, I finally decided it was time to write another book. This time, it’s a how-to book that explains exactly how to do your own usability testing. I wrote it because I really do believe that everyone can—and should—be doing their own testing.

GUI Bloopers 2.0 Jeff Johnson’s “GUI Bloopers 2.0“.  Common user interface design don’ts and dos.

Web Form DesignIn “Web Form Design“, Luke Wroblewski draws on original research, his considerable experience at Yahoo! and eBay, and the perspectives of many of the field’s leading designers to show you everything you need to know about designing effective and engaging Web forms.

The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the SanityThe Inmates Are Running the Asylum“: Why High Tech Products Drive Us Crazy and How to Restore the Sanity. Imagine, at a terrifyingly aggressive rate, everything you regularly use is being equipped with computer technology. Think about your phone, cameras, cars – everything – being automated and programmed by people who in their rush to accept the many benefits of the silicon chip, have abdicated their responsibility to make these products easy to use.

About Face 3 : The Essentials of Interaction DesignAbout Face 3: The Essentials of Interaction Design“. You’ll learn the principles of good product behavior and gain an understanding of Cooper’s Goal-Directed Design method, which involves everything from conducting user research to defining your product using personas and scenarios.

Designing the Obvious: A Common Sense Approach to Web Application DesignDesigning the Obvious: A Common Sense Approach to Web Application Design“. Designing the Obvious belongs in the toolbox of every person charged with the design and development of Web-based software, from the CEO to the programming team. Designing the Obvious explores the character traits of great Web applications and uses them as guiding principles of application design so the end result of every project instills customer satisfaction and loyalty.

Designing the Moment: Web Interface Design Concepts in ActionDesigning the Moment: Web Interface Design Concepts in Action“. The trick to great design is knowing how to think through each decision so that users don’t have to. In Designing the Moment: Web Interface Design Concepts in Action, Robert Hoekman, Jr., author of Designing the Obvious, presents over 30 stories that illustrate how to put good design principles to work on real-world web application interfaces to make them obvious and compelling.

Forms that Work: Designing Web Forms for Usability Forms that Work: Designing Web Forms for Usability“. Forms are everywhere on the web – for registration and communicating, for commerce and government. Good forms make for happier customers, better data, and reduced support costs. Bad forms fill your organization’s databases with inaccuracies and duplicates and can cause loss of potential consumers.

Designing Web Interfaces: Principles and Patterns for Rich Interactions Designing Web Interfaces: Principles and Patterns for Rich Interactions“. With the recent advent of Ajax and the resurgence of Flash for developing web sites and applications, new patterns of interaction have emerged on the Web. In this book, Bill Scott provides insight on how to best take advantage of the power of these technologies for designing a great user experience through a series of best practices, summarized as eight key principles.

The Back of the Napkin: Solving Problems and Selling Ideas with Pictures The Back of the Napkin: Solving Problems and Selling Ideas with Pictures“. The premise behind Roam’s book is simple: anybody with a pen and a scrap of paper can use visual thinking to work through complex business ideas. Management consultant and lecturer Roam begins with a watershed moment: asked, at the last minute, to give a talk to top government officials, he sketched a diagram on a napkin.

Talent Is Not Enough: Business Secrets For Designers, 2nd Edition Talent Is Not Enough: Business Secrets For Designers, 2nd Edition“. The best business guide for design professionals just got better! This revised and expanded second edition includes everything designers need—besides talent—to turn their artistic success into business success. You’ll find information on key issues facing designers from freelancing to managing established design firms.

HTML 5 for Web Designers HTML 5 for Web Designers“. HTML5 is the longest HTML specification ever written. It is also the most powerful, and in some ways, the most confusing. What do accessible, content-focused standards-based web designers and front-end developers need to know? And how can we harness the power of HTML5 in today’s browsers?