Managing a web design project: The do’s and dont’s
June 3rd, 2014
Posted by Mihajlo Kitanoski - Founder, Owner and CEO at CENTROG Information and Communication Technologies
Follow me on:
In many ways the first impression that your website makes is
critical to your client’s online behavior. Today it is simply
unacceptable to have a poorly designed website. On the other
hand - nice looking design is a subjective category. Also,
there are a variety of devices (smart phones and tablets) your visitors are accessing your
website nowadays which makes the designer’s job a lot more
difficult. Disagreeing on a subjective topic may lead to a
dead end on a certain projects, so make sure you follow some
basic do’s and dont’s when managing a web design project.
Don’t start with design
Redesigning your website just because your new manager “doesn’t like it”, without analyzing the time users spend on your website and the web pages they visit is rarely worth it.
The main functions a website has nowadays are informing visitors about your company, and converting them to quality leads. When the web design project begins you as a project manager need to make sure all stakeholders are informed about the goals of the website (ways of attracting visitors and leads) and have given commitment to these goals. Then you can proceed to defining the technical and functional requirements of the website cover the main user scenarios.
In addition this the sales and marketing processes, initiatives and the actions visitors are suppose to take need to be clearly defined. Many IT mangers fail to realize that the websites are a powerful marketing tool nowadays, not an IT project that needs to be written in the latest programming language available.
Do manage design expectations during the project
The best way to go through the web design project is not to even start the designing the website until all the required info is gathered and the goals are defined. This way your designers will have a clear picture of what is expected from them. Also, the set goals will act as good directions of how to lead user through the process of conversion from visitor to lead.
In addition to this, as we mentioned before, be advised that design is subjective so most issues after the design process will not be solved by consensus. You will need to run on your authority here and go with proposals that look the best to you. Just make sure you have user experience on your mind when you are evaluating proposals.
To quickly summarize, if a web design project starts with setting design it has great potential to miss expectations, which results in rework, being over budget, and being late. But requirements are defined up front and the whole team is informed about them the design process should run smoother and your designers should have a clear picture of user experience they are supposed to deliver.