Fulfilling multiple roles

For many companies the perception is a "web designer" is what you need to build your new site.

Back in the old days of web everything was produced in basic html, there was no social media and functionality was basic to say the least.

As technology has evolved web, media and brand companies have seen that they can offer so much more, but it is unrealistic to think that an all-rounder can provide everything you need from concept to design, build and strategy.

Even a small project will be more successful if the Stages are handled in a manner that creates a PUSH effect of information.   This diagram shows what we mean.

 

The above diagram shows a communication problem and could lead to a very unhappy client.

Now consider the following process.

Let's analyse this second process in more detail.

Stage 1 & 2:
Once the brief is received, the info architect, designer and developer need to meet to discuss the requirements.

Stage 3:
This meeting ensures that the info architect can accomodate functionality constraints and strong design thoughts.

Stage 4 & 5:
It is important to take time out of the schedule to ensure any work carried out is seen by both the designer and developer so they can tweak where necessary.

Stage 6:
The design is sent to the client for approval.   If the client is happy then we build and if not we tweak again.

Although this method is more time consuming, you will get better results.  Meetings keep everyone in the loop and give a clearer and growing understanding of the requirements.