Archive for January 2007

We should be woo'd and were not made to woo.

New Documentation!

By Kevin Hale · January 30th, 2007

While our fantasy here at Wufoo HQ is to create an application so easy that anyone can use it without looking at a single line of documentation, we’re not so foolish as to think our stuff is without confusion or need of clarification.

Over the last few weeks, we’ve been working feverishly to design and create, hopefully, some of the best documentation you’ll ever encounter for a web application. We’ve tried to incorporate as many learning styles as possible adding overviews, screenshots, faqs linked to our knowledge base and even video screencasts to help anyone looking to learn more about their Wufoo environment.

We’re really happy with the way things are shaping up and while we’ve got a long way to go with adding material and better integrating the help into Wufoo, we want everyone to know that we’re excited and dedicated to the task.

Many thanks goes to Brian Campbell for helping us out with the videos and composing very excellent screencast music.

Converting Paper Forms to Online Forms

By Ryan Campbell · January 17th, 2007

Usability.gov has an interesting article on converting paper forms to online forms. What is striking about the article is how many fields paper forms have, and how those fields do not translate to the web. Additionally, web forms with too many fields confuse users. Here is a list of lessons learned that the article points out:

  • A form that works on paper may not necessarily work online.
  • Don’t ask for the same information more than once; collect only information that you are going to use.
  • Provide a logical structure.

And then the article goes on to point out 6 usability issues to keep in mind when designing the web version of the form:

  • Avoid using jargon; use clear, simple language for all field labels and questions.
  • Provide a context for filling out the form.
  • Include field formatting instructions, if necessary.
  • Ensure form elements (widgets) can actually be used.
  • Ensure all questions are worded clearly.
  • Reduce cognitive load in a form; don’t make users think (humans don’t think like a database).

Overall, the change is drastic, and I find the web version of their form much more pleasant to look at. You can also note that they opted for label placement above rather than to the side. You can compare the paper version and the final web result. In addition, I created a copy of the form using Wufoo. 10 minutes later I had a fully functioning form with validation that met all of the usability requirements.