As web designers we put a lot of thought into our designs to try and achieve the best end result. This result may vary from project to project, business to business – depending on the specific objectives of each client we work with. Here at ireckon, when we’re designing a new web site for a customer – our web design department (yes – we have a whole department of Programmers too) strives for the best end results we can; producing a design that we are proud of and one that our clients love. This is not always an easy result to achieve.
We currently step through a process which involves meeting with every client for a design briefing. This design meeting is the time where we discuss goals and objectives for the website, colours and styles that the client likes and doesn’t like, and often, if we are replacing an existing website – we also go through what they do and don’t like about that website.
We then take any artwork that has been provided and get stuck into creating an awesome design.
Before any designs are delivered to our clients, the members of our web design team meet to explore and discuss the design, and provide constructive criticism where necessary to help achieve the best possible new web design in accordance with the requirements.
When this is complete – the design is then sent off to the client.
As happens with any process, after this had been ‘the way’ for some time we discovered some drawbacks. As we supply most of our initial designs as images, rather than as working HTML pages, it’s not always clear what some of the on-page objects or elements will do, or – how they will work when the site is all built. A fellow ireckoner came up with the idea to provide visual documentation that describes different sections of the design, how they work and their purpose on the web site and in the big picture.
This has been working well, and there has been far less confusion and ambiguity about the web designs and web site element designs we send. This new process has been ticking along for some time and just recently the discussion came up about another potential drawback. Most of our clients provide their design feedback either via email or over the phone to their Account Manager – which then gets passed on to the designer. In either case, because design is not an exact science – there is always the risk of misunderstandings happening. There are too many opportunities for misinterpretation – from the initial client feedback to the points that it’s delivered within the office. And of course, because design is subjective, we designers don’t always agree with some of the changes our clients ask us to make. Opinions aside – any confusion or misinterpretation makes getting to the desired end result not only harder, but a more drawn out process with phone calls and emails going back and forth.
So it came to our attention that we should be ‘selling’ our web designs and ideas to our clients. By having our customers in to the office to discuss what we have done and why we have designed certain elements, they can get a better look into our thoughts and reasoning behind the web site designs. When we give the opportunity for immediate feedback, and have a client identify exactly what they do and do not like – we can discuss and debate each item – and come to a decision on the spot. We also find we are able to answer questions, and share our professional opinion on some of the feedback and requests that come from seeing the initial web site design.
No doubt this process will need to adapt and evolve as we find new hurdles and new solutions throughout the whole web design process, but for now – we’re finding that with more face-time with our clients it’s running smoother than ever.
About Erin
