I’m Chanpory, and this is my site on how to live and work better as a designer.

You should follow me on Twitter here.

For more, check out the archives.

This summer, I’m interning at Dubberly Design Office, an interaction design studio in San Francisco. My first week consisted mostly of 10-hour days manning the copier in preparation for a week-long interaction design workshop we were putting together for Samsung’s design group. The next week, I got the incredible opportunity to assist with and sit in on the week’s lectures; manning the copier paid off. I heard Alan Cooper on user profiles, Rick Robinson on ethnographic research, and Shelley Evenson on making models out of research data. It was an educational smorgasbord. I’m still digesting it all, but what stuck with me was the concept of rapid prototyping.

The basic process goes like this: research, think, prototype, think prototype (repeat as many times as you can afford to,) then create! The idea is to learn as much as you can in the beginning of a project by “front loading” it with research, prototypes, and conversation among the parties involved.

After the workshop, my next project was to generate several very simple working demos of how poetry could be enhanced via the interactivity of the web. These would be shown to clients and other designers to stoke their creativity, leading to the generation of more ideas.

My first instinct was to learn Javascript to create a demo of the effects I had in mind. I have decent HTML and CSS skills, and had been looking forward to learning a little Javascript. So for the first few days, I scoured the web for tutorials, camped at Borders bookstore, and went cross-eyed looking at code. After a few days, I knew I was in over my head, and wasting time quickly.

The situation didn’t call for nerdy-beautiful, standards-compliant web pages. This was a brainstorm, an interactive sketch, not a golden master. I recalled the rapid prototyping credo: “Fail early (when you can still afford to,) fail often (so you can learn as much as possible.)”

I decided to use a tool I knew well, Adobe ImageReady’s rollover effects. My web page mock-ups became screenshots linked with hacky rollovers. Sure, the code was bloated, but I did it in an afternoon and got feedback the same day. I quickly gained new insights into my initial ideas and was able to alter my course of action before investing loads of time and resources learning a scripting language.

This experience taught me:

  1. Don’t be perfect, just get it done In early stages of the planning process, get something—a model, a demo, a prototype—working as quickly and cheaply as possible.
  2. Interate often Test it and do it again and again. This way, you can begin steering a design in the right direction before it becomes too costly to change course.

6 Comments

  • RyanH

    gravatarJun 29, 2006
    12:56 pm

    When you are putting early prototypes in front of users, there are additional benefits to using less polished prototypes. When they see the rough prototypes, users often feel less constrained about giving more critical feedback then they might with a more polished prototype. I’ve had success using simple paper prototypes that allow for rapid iteration during testing, and Omnigraffle’s actions palette also makes it a useful tool for quickly generating linked html prototypes.

  • Sean

    gravatarJun 30, 2006
    1:21 am

    I\’m glad you mentioned Omnigraffle, RyanH. There is a rebel faction (the Illustrator traitors,) in the office that likes to use it instead of Illustrator for the flowchart specific features AI lacks. I\’m on the fence but am interested in checking out the interactive tools it has. Very cool, thanks.

  • Go to the web, brave video journalist « reportr.net

    gravatarMay 4, 2007
    10:08 am

    […] The point is not to read a big book on HTML, or wait for someone to build you a website. There are enough online tools to create content without any technical knowledge. The idea is to try, fail, learn and try again. […]

  • Teaching Online Journalism

    gravatarMay 4, 2007
    5:33 pm

    So you want to become a video journalist?…

    […] In software and Web application design (as well as manufacturing), a related idea is rapid prototyping. An apt example of that: You’re supposed to create a demo, and you decide to learn a new technology to get it done. BAD IDEA! […]…

  • Mitch Milam’s Microsoft Discussions » Blog Archive » Random thought of the day: Failure

    gravatarDec 7, 2007
    8:33 am

    […] http://www.lifeclever.com/fail-early-fail-often-my-first-taste-of-rapid-prototyping/ […]

  • The moons of Verthandi – A random blog by Dani Giribet » Blog Archive » Les generacions de l’audiovisual es troben a Edinburg

    gravatarSep 6, 2008
    6:57 am

    […] mirem al present. Una de les poques lliçons que han sortit de la revolució de la Web és “equivoca’t, però fes-ho aviat, sovint i barat“. Amb aquest mantra molta gent s’ha fet milionària, sobretot als USA. Com podem […]