The process of web design can be broken into a number of distinct stages. Most would agree that these stages include producing a written specification detailing the requirement; defining the websites structure; producing a visual site design; developing the website; testing the website and finally launching the website.
However most of these descriptions seem to overlook any discussion of who the stakeholders are and what each stakeholder’s involvement should be at each stage.
Who are the stakeholders in the web design process?
In some cases it may be that a one individual takes two stakeholder roles within the process, most notably HTML/CSS work and visual design work is often completed by the same individual. That said we would define the stakeholder in the process to be:
The Account Manager – Typically the account manager would broad experience of web and application development, this is likely to include some experience of HTML /CSS development, programming and possibly graphic design. The account manager should also have a good understanding of the clients business. The key here is that the account manager should have a clear understanding of the web design process and of the needs of the client.
Client company representative – This might be the business owner or marketing manager who works for the client. This role might even be filled by a number of individuals who work for the client company.
HTML / CSS developer
Graphic Designer
Application developer – Often web development companies use an off the shelf package when developing a web application, in these cases the application developer does not work for the company providing the application to the client. However they are still involved in the process. For example, when an off the shelf package is used a web development company might send a request to the application developer to add a new feature to the application.
Programmer – The programmer is responsible for taking wire frame diagrams, design work and the specification and translating this into a working web application.
What is the involvement of stakeholders at each stage in the web design process?
All stakeholders should have some involvement at every stage in the web design process. However at any stage in the process only one stakeholder should have ownership of the project. This stakeholder will be responsible for ensuring the stage is completed and can be passed on to the next stakeholder.
Stages in the process and responsibilities of stakeholders at each stage
Production of written specification
Owner – Account manager
The account manager is the owner of the process at this stage and is responsible for ensuring that the web design project sets off in the correct direction and has a clearly defined scope.
However the programmer also should have a great deal of input at this stage ensuring that timescales and budgets given in the specification are accurate and realistic. The programmer should also liaise with the application developer and in order to make accurate judgements relating to cost and timescale.
Design of site structure and wireframe diagrams
Owner – Programmer
Many might assume that the account manager should have ownership of this stage of a web design project. However although the account manager and business owner should play a part in this part of the process the programmer should be responsible for producing wireframe diagrams for the project.
There are several reasons for this, most importantly the programmer must have a clear understanding of the business, its needs and how the application meets these needs. Another important reason is that a programmer will actually begin to plan an application whilst producing wire frame diagrams. Assigning ownership of this stage of the project to the programmer will ultimately save a great deal of time during the development stage of the project.
Producing a visual design / HTML and CSS development
Owner – HTML / CSS developer and/or graphic designer
Often a single individual has ownership of producing the website design as a graphics and breaking this design up into HTML pages. However there are advantages and disadvantages of this stage being completed by a one individual.
Often the most talented graphic designers are not the most skilled HTML / CSS developers. Therefore it can be beneficial for different individuals to be involved in this process. However if the design and HTML are completed by one individual there is less chance that a design will be produced which is difficult to break into HTML at the same time as achieving browser compatibility. The best option depends on the individuals involved in the process and on their skill set.
Developing the site
Owner – Programmer
In large applications the development process is iterative. If this is the case the account manager and business owner should periodically have input into the design process. However in small projects the development process is atomic and can be completed in a short time period. In these cases the programmer often has sole responsibility for this stage.
Testing and review
Owner – Account manager
Although the account manager owns the task in practice is best if the developer also plays an very active role in testing the application.