Notebook

Designing Websites with Purpose

13 Nov 2009 at 9 PM

Purpose provides a framework for web design. For a while I have felt that List of One was lacking something. The site design was nice, the code was all standards based, the information was all accurate, yet I wasn't happy with it. The site lacked a clear purpose.

I recently gave a talk on web development to Academic IT staff from several Big Ten Universities. A focal point was building web sites with a purpose. Through my career with Purdue University I've had the opportunity to work on many web sites without a purpose, at very least, the wrong purpose.

Small paper cups for condiments

This photo serves no purpose on this page, or does it?

The story goes like this. An internal client approaches the web team with a request for a web site. Usually, they have an idea of the topic areas the web site should cover. Sometimes they have some content to reuse. The graphic designers create a template, the writers write some copy, and the developers code the pages. The client pays the bill, everyone seems happy.

But, is it a good web site? Probably not!

A good web site needs is a purpose, and explicit objective. The purpose should guide development with each decision and each piece of content building to achieve it.

Is the objective to inform, sell, collect, share, or something else?

When redesigning List of One I started by defining a purpose. The process involved deciding what I wanted the site to do for visitors and what I wanted the site to do for me.

The purpose of List of One is to:

These objectives helped frame the whole site redesign. Each decision in the design process was evaluated against the written purpose. I also have a guide for the future.

Having a written purpose sparked some innovation. For example, I learned the Django Framework to build on the sandbox goal and the recreated portfolio section focuses on showcasing design.

As web professionals we should help our clients get the most out of the web sites we create. It's not enough to build a web site. Clients should expect us to design them.

Identify problems, create solutions.

When a client comes to you with a navigational structure, they're providing a solution. It's not their job! It's our job to solve the problems. Work with the client to identify the problems.

The first problem, defining a purpose.

When defining a purpose, ask what questions.

Use these and other questions to understand client's goals, their purpose.

With a written purpose in hand, think long and hard about the best way to achieve it. Don't limit yourself to any one approach. When your client comes to you with ideas, judge them against their purpose. If it doesn't fit don't include it.