For The Client

Good Form To Increase Conversions

Monday, February 22nd, 2010


Entrance Barriers

If you had to guess at the largest entrance barrier for a website what would guess? Maybe there is a cost involved and its too high? The website design is bad? Its a complicated website and not enough instructions?

Sure the cost might be more than the market will bear. More than likely your just trying to get that initial contact, an email, newsletter sign-up, anything to get more information to a potential customer. Cost to the user, $0.00 and your still only getting a small percentage of visitors to take the next step, whatever that may be.

Is your site ugly? Maybe, an ugly site to one person is artwork to another. Do ugly sites get less use? Unless your making the visitors eyes bleed and not distracting them with flashing or scrolling text this is more than likely not the cause. Some would say Amazon is ugly or Gmail, certainly Craiglist isn’t the pinnacle of design. As long as the user can get around easily without getting a migraine this probably isn’t what is holding you back.

Maybe you just need more instructions because they get confused? Here is the truth, nobody is going to read your directions if its more than a couple sentences. You can use all caps bold flashing text to tell a user what to do and they will not read it if its too long. If you already have instructions and you think you need more detail your only making it worse.


Its all in the forms.

Well designed forms aren’t the end all metric of usability however I would argue its a majority. Its all in the little details. Here are some of the basics.

  • Are required fields clearly marked?
  • Are those fields really required? The longer the form the less likely it will get submitted
  • If a user puts in the wrong input is it immediately obvious what went wrong?
  • Did you erase the whole form on failure causing the user to start over?
  • Can a user easily fill out the form by just typing and tabbing to the next field?


An example of bad form.

The federal government uses a site called My Pay. This is by far the craziest process I have ever seen to fill out a form. Recently they asked all their user’s to change log in credentials and what a nightmare.

My Pay Log In

The first thing that happens when you try to login is it opens up a new window in full screen. So if you have a large monitor your now staring at 23″ of login form. Annoying, but not the end of the world.

The complete insanity is you can’t use the keyboard. You have to actually click on each character with a Virtual Keyboard. But lets take it one step further down the crazy path. The letters an numbers are generated in random locations with each attempt.

This is for “security” purposes. I wonder why banks don’t use this practice? There is a notice message up now. They’ve disabled right click function as well … nice.

To all myPay Customers

Although most users have established their new login credentials with no trouble, some users are calling the Central Customer Support Unit for assistance. As a result, customer support is experiencing high call volume, and many customers are waiting on hold longer than usual.

We apologize for any inconvenience this may cause. We are doing everything possible to remedy this situation.


Good Form

Mint has an example of a great sign-up form. As soon as the page loads the the cursor is focused on the first field so you can start typing right away. You can tab to the next field and you’ll notice the current field is clearly highlighted. Furthermore by clicking on the label it brings the field in focus. You can click anywhere after the check-box field and it will toggle the check-box. You can actually fill out the whole form without even touching your mouse.

Usability is increased by validating on the fly. Each time you go to the next field the form will check if you have a valid entry and display the error if there is one or simply OK if there isn’t.

Suckage To Usage Ratio – The Ultimate Formula

Wednesday, December 30th, 2009

I have tried to explain the idea behind this many times with varying levels of success. Well, the guys at 37 Signals hit the nail on the head with a formula in their post, “What’s the suckage to usage ratio?”

Suckage to usage ratio 101

The 37 signals post uses the Amazon Kindle as an example of how a single feature can have massive suckage but still produce a great product. It sucks to type on a kindle but how often do you actually type on your Kindle? Not often, the kindle is for reading not typing. I only type to search for a book which is probably less than 5% of my use.

Suckage to usage ratio and you

As your building your website there will always be features and pages that need love. Maybe its a bad layout, maybe its bad programming or maybe its a bad idea. If its rarely used how much time should you spend making it perfect? Websites have finite resources (time, budget and manpower), choose their allocation carefully.

Consequences of Suckage

At best failure to understand this principal will lead to late milestones and blow your budget. Worst case scenario it will blow your whole project. Developers can only do so much to keep you on track but in the end we will usually write it the way you want it.

Applying the suckage to usage ratio

Come to think of it you can apply this formula to everything. People, places, things, anything that takes up time and money.

  • Purchase of a home or car
  • A book or movie
  • Where to go for vacation
  • Who your going to vote for
  • Your Relatives
  • Your dog

The key to a full life may very well be in the suckage to usage ratio. Certainly worth applying to your website.

Developing Applications For The Less Saavy User

Wednesday, July 1st, 2009

I hear this one allot from my clients, “I need my application to be really simple and easy to use, my users aren’t very technical”.

The first thing I need to do is remind myself and the client of my own limitations with this. By default developers are not always the best usability testers. This is especially true for the developer who built the application. We have our own lingo and we have pre-conceptions about how the application is used. In nearly every circumstance I hand over a finished application and the client will find a sequence of events that leads to a scenario I simply never thought of. I expect this on every build and make adjustments based on feedback.

From 37signals book Getting Real

You need to speak the same language as your audience too. Just because you’re writing a web app doesn’t mean you can get away with technical jargon. Think about your customers and think about what those buttons and words mean to them. Don’t use acronyms or words that most people don’t understand. Don’t use internal lingo. Don’t sound like an engineer talking to another engineer. Keep it short and sweet. Say what you need to and no more.

You can take this methodology too far. If we assume the users knowledge is only slightly beyond checking their email we should not be creating new standards and terminology that don’t exist on common websites. Take a look at some of the popular mainstream applications that are used daily by users of all technical levels.

Should the button say “Update” or should it say “Save”, or should the button say “Press this button to update the page”? Clearly the last example is overkill, take a look around at other applications and see how similar user interfaces are handled.

Another example is using “click here” for links. This is one of my pet peaves. Your site should have a layout that makes it very obvious what pieces of text are links. Instead of I found this really interesting article click here to read the interesting article. Consider I found this interesting article. Aside from poor usability, “click here” is counter productive to search engine rankings.

If the user base truly has a low technical level your doing them a disservice by introducing them to your custom user experience that does not represent the standard.

Trying to anticipate users perceptions can be like trying to hit a moving target on boat from another boat in heavy seas at night (clearly there are those skilled enough to accomplish this, but that is a rare breed). You’ll waste valuable time getting your product out spending hours to think of the best name for a button or link. The best approach is to get someone who has never seen your shiny new app. Sit them down, give them a task and just watch. You’ll see very quickly when they reach a roadblock. You’ll quickly find things you would of never thought of while they quickly overcome your perceived roadblocks.