My first deliverable is creating a proposal on a given brief. A proposal is a document which outlines the project for the client. A proposal is typically made to make sure that the client understands all aspects of the project. For example, the timescale of the project will be included in the proposal for the client to see. A proposal is only made when discussed with the client and other stakeholders.

 

WHERE is not before HOW. This means that where the project will be discussed will be less efficient than how the project will be made. It is important that the stakeholders are involved in every step of the project. This can be ensured through daily meetings or meetings according to their availability. Additionally, if for some reason the client is unable to attend the meeting in person, a typeform can be used to communicate. A typeform is basically  a collaboration tool that lets clients communicate and look at documents. Collaboration prevents design issues and overall increases the visibility of UX design.

 

The first part of the proposal document is to create a title page and contents. I will also be developing a simple logo for Hill street Belfast. I will also be thinking about colours and limiting them to two colours. Firstly, the problem needs to be identified. Why is the project being developed?  What does this project lead up-to? What is the purpose of this project?

It is important that the client understand the problem in a clear and concise way. Explain the solution to this problem and how it will benefit the client. A problem statement will be develop for my own proposal.

 

A proposal will need:

 

Name, date and details of stakeholders. The name of the project will be displayed in the title page in a clear font. The date is to show the timescale of the project. The stakeholders involved will also be addressed.

 

Some techniques to capture data can be:

 

Interviews

Observation

Research

 

These techniques can be applied to find out about the user goals.

 

Defining some deliverables:

 

User personas

Wireframing

User testing

Competitor analysis

 

Assumptions are another part of proposals. These are any problems or disturbance that might pop up in the middle of the project. Designers outline all the issues that they could face and go from there. They work to solve those issues.