Web development in 4 simple steps (kinda')

All web sites have a purpose and goals. Based on those, an Interaction design (IxD) can be created to specify how the site should work. Graphical design build on the IxD to define how the site feel and look. Implementation then actually make it work.

My IxD method, as outlined elsewhere, is based on the problems and issues that the site owner and visitors encounter. Together with pattern languages and user testing, a prototype (often on paper) is created.

In graphical design, color and shape are used to further the goals of the IxD. Relative importance of elements, relationships between elements etc are communicated via graphics. The grahpical designer is also in charge of creating a visual identity for the site. That the identity is suitable and polished is important–studies have shown that the visual design of sites greatly impact visitor's confidence. While designing, IxD issues will likely come to the surface and will need to be addressed. Delivery is often in the form of user tested digital prototypes.

Implementation is of cause the stage where the site is built, both on the front- and back end. During the build phase several IxD and visual issues will surely be discovered and will need to be addressed. Since the IxD has been done thoroughly the issues will likely be small and easy to overcome. After user testing the site is ready to go like and the circle starts again.

Am I reeeally needed, and if so, how much?

Which design tasks need Interaction Design knowledge to be properly solved?

1. If the task has been solved successfully before by the project group, they should solve it again. I.E. already done == do it again.
   
2. If the number of possible interaction related misfits in the task is small, or the possible misfits are almost irrelevant, the project group can probably handle them themselves. I.E. simple problem == simple solution.
   
3. If the task at hand has interactive elements that are difficult to get a grasp of (I.E. has a large number of possible misfits) and thus the solution is not obvious, specific knowledge of Interaction Design has great value. I.E. complex problem == IxD useful.
   
4. If previous attempts at solving the problem has failed, IxD might help. I.E. repeat failures == IxD to the rescue.
   

Once the need for IxD has been established, the question turns to: how much resources will be needed? The answer, of cause, depends on project scope (I.E. the number of possible misfits to take into account) but it also depends on how well the design should fit – sometimes even a large project can manage with a rather skimpy design.

Possible steps in my work include 1. interviews with the client, 2. interviews with their customers, 3. discussions with the project group, 4. own contemplation, 5. analysis and hierarchy-creation, 6. pattern reuse, 7. pattern creation and 8. pattern synthesis (to create the final form for task). Steps 1, 2 & 3 can be skipped, steps 4 & 5 can be rushed, step 6 cam be maximized at the cost of step 7. But some contemplation, analysis, pattern creation has to be done and pattern reuse and the synthesis has to be allowed to take it's time.