Proposals were the topic of this weeks lecture. Proposals was not a new term to me as I have previously heard of business proposals, project proposals and obviously marriage proposals. All of these forms of proposals have some thing in common, which is they are all suggesting or proposing a deal of some sort to a person, business, investor etc. The proper definition of a proposal is-
“a plan or suggestion, especially a formal or written one, put forward for consideration by others”
In relation to Interaction design proposals are very important as they can outline the purpose, scope, responsibilities, pricing etc. which are is very important in relation to the project.
A proposal would be needed before the project begins so that both parties involved are aware of what the project includes and what they may need to provide. this ensures that there is no miscommunication or problems in regards to the project and if one does arrive the proposal can be used to review the original guidelines.
The proposal would be created by the individual or the team that is offering their service. It can then be shown to whoever is hiring them and together they can decide if any changes or revisions need to be made or if both parties are happy with the proposal as it is.
When writing a proposal there is a guideline that can be followed to ensure that nothing has been left out:
- Title Page
- Project Overview – What needs done + experience
- Project Approach – How it’s going to be done
- Scope of Work – Who is involved
- Assumptions – What you need
- Deliverables – What you’ll produce
- Ownerships & Rights – Work for hire / Licensing
- Additional costs / fees – Expenses
- Pricing & Payment Schedule – Your quote
- Acknowledgement & Sign-off – Agreement to start
Chapter 3 in the book “A Project Guide to UX Design by Ross Unger and Caroline Chandler ” is all about proposals.