
Websites are Taxis. Products are Trains.
November 24th, 2009Recently we’ve been having extremely interesting conversations with friends working as web/graphic designers in Dublin. We inevitably encounter the same hurdles as we progress through our respective projects, all be it in different guises. At the end of the day the overarching design process is the same across disciplines and this is particularly true of client-based commercial work. Everyone has their individual repertoire of minor successes and the corresponding disasters – this is why we do what we do.
One particular conversation in the past week touched on a topic I have been considering for some time. How does the cycle time of a project, from conception to full production, effect the manner in which that project is undertaken?
Put it this way; designing a product for mass production is like boarding a train. Inevitably the process is lengthy, the opportunity to be a part of it is rare, significant changes in direction are impossible and the number of people involved is high. Imagine trying to convince a train driver to take a different track, think of the quantity of passengers who need to be convinced that going to a different city is a great idea.
On the other hand; designing a piece of print or a (small to medium sized) website is like grabbing a taxi. The streets are full of taxis, the journey is short, the people involved are few, and if you remember at the last minute that you need to collect your cat on the other side of town it will cost you, but it’s ok.
This fundamental difference has implications for what is and isn’t possible on each project. When the train pulls out of the station you’re either on it or you are not.
I will use this analogy over the next couple of weeks to draw conclusions on the possibility for open-source design, crowd sourcing, design direction and any other topics which become relevant.