March 28, 2007 at 1:31 am
Recently I've been trying to reorganize my efforts and pull my clients and coworkers closer during the planning and early design stages of a websites. In doing so, I've decided to hard nose myself into using prototypes (also called wireframes) for every project, not just the big ones. It's easy to think, "this site is so small, why take the time to prototype it — let's just bust it out and move on". What happens more often than not is that we end up with twice as much back-and-forth work and a muddled end result.
For those who are uninformed, or have never used prototyping as a method of planning, a prototype is a draft version of a website and is often the best way to gather feedback while planning and designing a website.
Low-fidelity prototypes are the fastest way to brainstorm and see your ideas, make your mistakes [and build off of them] and to see your progression.
Using low-fidelity prototypes (such as paper-based prototypes) is also the quickest way to get feedback on preliminary site architecture, design, and content. Use simple tools like paper, pen or pencil, scissors, Sharpie markers and sticky notes to create these low-fidelity prototypes.
Traditionally you would transition from a low-fidelity prototype to a high-fidelity prototype to present a more visual illustration of the website. However, each high-fidelity option can be used on its own, or in conjunction with additional options.
I hope this information helps clarify some of the prototyping options available to designers, or perhaps it will inspire the use of prototyping as part of every project undertaking for those who stumble upon this entry blindly. Only recently have I began using prototypes to the extents described in this entry; for years I completely skipped over most prototyping methods (occasionally doing only a site plan) and began each project with comprehensive illustrations. This negligence cost me an abundance of time and profits over the years, however it has made me a proficient comp artist — so I guess it's not all bad...
I would also like to add that prototyping isn't just for website design, it can be applied just the same in other types of design or development projects; from print design to UI design.
Develop a Prototype – Design | Usability.gov
Jason Santa Maria | Grey Box Methodology
Comprehensive layout – Wikipedia, the free encyclopedia
You’re currently reading “Brush up on your Prototyping,” an entry on Jeremy Helms
for this entry. If you have something to say, please consider adding your own.
You can also subscribe to an RSS feed of this entry's comments.
Categories: Design, Development
Be the first to leave a comment!

I am Jeremy Helms, 29 year old graphic designer, web designer, site architect, programmer, copywriter and ambitious entrepreneur. I was born and live in Fort Walton Beach, Florida. This site is my personal periodical for design, code, business and other topics. When I'm not glued to the computer, I enjoy music, movies, late-night television and sometimes a good night out on the town with friends.
I began professional work in the IT industry 14 years ago in September, 1995. I started my first business in 1998, incorporated my second business in 2001, my third in 2002 and my fourth and most recent in 2006. I am a sponge — I am constantly exploring and learning — about business, design, programming, history, society, and whatever pops up on blogs across the web.
If somehow I've managed to keep you interested this long, you might as well check out:
The following feeds are available to meet all your syndication and aggregation fantasies. There are also per-post comment feeds available on each blog entry page.