User interfaces (what a user sees on a website) are designed for a few different reasons: they want to teach, they want to sell, they want information. Either way, it’s designed to perform a function. But what if it wasn’t? What if the interface was only pretty? Would you pay for pretty? Pretty with no ROI? I would, if were tasked with spending cash for the sake of art (read: balling out of control).

I’ve been thinking about the “call to action” lately. The call to action is too often an afterthought. Too often, I’m looking at a website wondering what action it’s target market is supposed to take. Before we get in too far, let’s review a few examples of a call to action–which, by the way, should be designed based on the website owner’s return on investment needs.

  • Newsletter sign up
  • Contact form submission
  • Online sales
  • Quote request
  • Consume information
  • Request information

There are a variety of actions a user can take but without a definitive, obvious, effective call-to-action a user’s action might just be to leave the website all together. When a user fulfills the intended call to action (completes a form, initiates contact, whatever), website analytics regard this as a “conversion.”

One way to determine how your call-to-action is performing is to first look at two things within your website analytics:

  1. Bounce rate (should be a low percent, at least under 30%) and
  2. Conversion rate (should be a high percent, depends on nature of your action).

If your website isn’t performing the way it should be, it’s time to take a look at its user interface. Let’s face it if your analytics aren’t where they need to be, you’re tying to bungee cord to your users’ feet making sure they’ll never convert.

Tagged with:
 

Mobile web buzz has been growing with increasing speed since iPhone business applications became norm. We’re using mobile applications to navigate KeyNote/PowerPoint presentations, email co-workers, and consume data. In my opinion, mobile APPLICATIONS (downloaded software) is best for automating processes. Business processes include: communication, transactions, tasks, etc. The point is business applications are successfully sought after because they save time (therefore money).

But the greatest failure by early mobile developers is their apparent disregard for usability–a huge time waster. It’s no wonder many design-and-usability-loving-websites have passed by mobile applications to be featured! The archaic looking designs were difficult to navigate and therefore made disposable by users.

Today there are over 15,000 iphone applications alone, in addition to another 2,000 Blackberry applications. And, finally, users have begun to demand aBickBot iPhone App: Strokesrespectable interface. Developers have teamed with information architecture and user experience planning rockstars to perform. The result has been applications I consider straight-up-sexy, example: Strokes, a golf game scoring app that allows users to export scores to Facebook or Twitter (by BickBot). Clearly I’m a big fan.

While building an iPhone application isn’t practical for all businesses, ignoring the mobile user is a big mistake. In the past 90 days, mobile web has been as hot of a topic as web development itself (well, darn close!).

(more…)