While reviewing the research and interviews completed over the previous semester I decided that some changes in my project aims were required based on my research.

At the start of the project I had originally envisaged the application to be a project management system that the user would use throughout the project and that would contain project information. Both the Designer/Design team and their Client(s) would access this information, I realise now that I was trying to create a content management system that had a design process as its navigation. There are several project management applications available that have the facility to add content and give feedback, so I wanted to move away from my original idea and produce an application which models the design process and the relationship between Client and Designer to try to ease some of the anxiety issues that I discovered during my research and summer placement.

I decided to focus on informing the Client of the key principles of the design process with the aim of easing anxiety while giving them increased knowledge of how Designers work through a typical project. I think this will give more value, as the Client will gain knowledge and an appreciation of the design process rather than just using it as a navigation method.

The application that I produce will have informative pages about the key stages, theories and practices in the process. The user will navigate through the process in order to access the information pages, allowing them to gain knowledge as to where and how that information is related within the process.

The Client will receive my application at the start of the project with the Design team which they can then refer to during the project, helping them understand the process the Designer(s) are going through in order to create their application or product. This will help communication and understanding between both organisations and prevent anxiety gaps.

After this reflection I clarified my thoughts and wrote down the main aims and challenges that I wanted my final application to meet and overcome.

The application should: -

• Explain and demonstrate the concepts within the design process (e.g. iteration)
• Visually show the design process as a journey that both client and designer can navigate through.
• Help the client understand the design process, preventing frustration and anxiety.

By using my previous research into various design processes I tried to narrow down the process into what I considered to be the five key stages or steps for the process. Each stage would contain information about the design process at that point in the project including design techniques and principles that the Client could explore to help them improve their understanding of the process.

Brief
This stage explains to the Client about the importance of providing as much information about the final outcome of the process. The more information about the users of the final outcome and its context of use the quicker the design team can analyse the problem to its fullest extent. If the Client is unsure about preparing the Brief then the Designer could assist in developing this by conducting a requirements analysis at this stage.

Proposal
The proposal stage is the Designer or Design teams response to the Clients briefing. A good proposal will help clarify the problem and the potential format of viable solutions to the client and should also contain a proposed stage payment system. This stage is particularly important if the Client is not entirely certain of the outcome that they want.

Development
In this section most of the design concepts and principles will be explained in the application. The ideas and their generation will be explained as well as freezing the concept so that the final design can be developed and produced.

Implementation
Implementing the finished solution covers the testing of the final produced design by both users and tests carried out on the solution itself. Also within the application there will be information about User training and tutorials and how they can help prevent anxiety about change.

Conclusion
The conclusion of the project will explain about the final payments and the value of reflection both throughout the process and at its conclusion to allow any problems encountered to be prevented in future projects.