Hands On Approach To Site Development

Many sites are launched every day. Some are good, and some aren’t. One of the main reasons I think small projects fail is because not enough thought is given to the process. Most folks start up Photoshop, design a site and put it online. Most of the times, this will result in time being spent afterwards on changing and adapting your site because it wasn’t really clear what it was supposed to do. Because of that reason I have decided to write this 8 step process for the creation of (my own) projects.

  1. Define a Problem
  2. The first step in developing a site is defining what role that site should fulfill. Sometimes this role is predefined by the client or project briefing, sometimes you have to define it yourself, but regardless of who defines it, you need a starting point from which to work. Important questions to ask here are: “Who am I making this for, what will it’s function be?” etc.

  3. Find a Solution
  4. Now that a problem has been defined, a solution needs to be sought. In my experience, a “Problem Based” brainstorm does wonders for this. Instead of the traditional way of just wildly suggesting solutions, work in a more structured way. Write down the problem definition and try, with each brainstorm idea to solve one or all of the problems defined.

  5. Refine Concept
  6. By now, a concept should start to materialize. Take a look at the concept as it is now. Does it solve the problem defined in step 1? Can it be improved? Once you defined your concept it is time to start the fun parts.

  7. Define Tasks
  8. Now that you have a concept, take a look at what the user will be using your site or service for. What is it’s main purpose? Does it have a core function? If not, should it? It is of vital importance to look at the tasks people will be performing on your application or site.

  9. Design a Work Flow
  10. Before even starting to make wire frames start thinking about the tasks in step 4. How can these tasks be fulfilled? What can be done to make the fulfillment of these tasks as easy as possible? Map out all the ways possible to fulfill the tasks at hand. Remember, less is almost always more, keep things simple. Don’t overwhelm our users with a multitude of options.

  11. Create Wire Frames
  12. Now that you know how tasks will be fulfilled and how they relate to each other, it is time to put that information to use. Because you already know all the different ways to get a task done, it is much easier to design the interfaces which will aid the user in performing these tasks.

  13. Define a Visual Identity
  14. This is a rather important step. People tend to be attracted to things that look attractive. Design a visual identity for your product, make sure it is distinguishable from your competitors (if you have any) and that it has easily recognizable features.

  15. Build It
  16. By now your project should have a clear structure and goal. There is a visual identity, a work flow and task definition. Time to put all that together. Because you already know how the structure of the site will be (thanks to your wire frames) and you already know what the visual feel should be (thanks to your visual identity) this shouldn’t be all that hard.

This list is by no means complete. It can never be, but it is good starting point from which you can work. And believe me, once some of the boring parts of your project has been decided, the fun parts are even better to do.

technorati tags:, , ,

Blogged with Flock

Date Posted

Monday, May 14th, 2007

Category

Design Guidelines, Interaction, Usability, Web 2.0. Both comments and pings are currently closed. follow me

Similiar Posts

Difference in Design
Software Updates and How It’s Done Wrong
Identifying Links
Grid Resources
Previous post: «

2 Responses to “Hands On Approach To Site Development”

Fredrik Wärnsberg Says:

You should check out some books on HCI. http://www.amazon.com/Designing-Interactive-Systems-Activities-Technologies/dp/0321116291
is a good start that covers many areas, such as PACT and MOSCOW analysis, heuristics etcetera.

You only need to read about half the book though, the later sections are pretty much more in-depth looks at each method explained in the first half, which isn’t really needed if you got the idea at first.

Peter Says:

Thanks for the tip Frederik!