IXD302 – A Project Guide to UX Design

Beginning our new proposal deliverable, Daniel told us to read a book called “A Project Guide to UX Design”. For this project, we have to design a UX proposal (Website & Brand) for a nonexisting company which is Hill Street.

What is the purpose of having a proposal? 

A proposal is a document that is useful for freelancers that creates a set of structured standards between a freelancer and another company; it is an agreement. At face value, it is a manual of proposed ideation of a project whether that be for any type of design or freelancing job. A proposal will contain a set of standards such as the idea, reasons, goals, legality, deadlines and much more. When freelancing, most often a person is on their own without any safety defenses. This is another part of the proposal that comes into maintaining a sense of direction and conciseness. Without a proposal, there is no definitive direction that either companies or freelancers can follow which can ultimately create failure, incorporation or confusion from either side. Upon signing from a company this means that they have agreed to everything in your proposal so if something goes wrong it is clearly outlined.

This book is very informative taking you step by step on how to create a proposal for beginners covering 11 areas such as:

  • Front Page
  • Revision page
  • Project Overview
  • Project Approach
  • Scope of Work
  • Assumptions
  • Deliverables
  • Ownership & Rights
  • Additional Costs & Fees
  • Project Pricing
  • Payment Schedule
  • Acknowledgment & Sign-Off


Title Page 

This part is basically the front page of the manual; the introduction page. It can be designed however you like, although appropriately.

The main things that should be considered are:

  • Clients company name
  • Clients company logo
  • Project title
  • Document type
  • Version of proposal
  • Submission date
  • My company name
  • proposal authors
  • Project reference number (if used)
  • Cost (optional)
  • Confidentiality

Revision Page

As with any other structural system, there must be a page to monitor any changes that have been made and how many revisions there are. Although, when additional modifications are made, it is important to read them carefully in case the two parties disagree on something. An example of this would be below:


Project Overview 

The project overview page is basically a beginning section that describes how I will create the proposal from my own words. It should be clear and profound, acknowledging each deliverable in a concise manner. It should also contain all vital information of the project’s vision in a highly detailed description.

Project Approach

This page tells the client what process will be conscripted. It gives the author to identify and define the plan of the project. This means whatever the author has defined is set as the standard rules/process for the work.

An interesting process which this book presents is the 6 part “PUREITE” process: Prepare, Understand, Render, Iterate, Test, Enable

This process can be additionally confined into 4 stages

01. Plan

  • Prepare – Competitor analysis, ground research, etc.

02. Define

  • Understand – Surveys, confinements & constraints, etc.

03. Develop

  • Render – Mock-ups, prototypes and products.
  • Iterate – Communication from both parties to redefine.
  • Test  – Testing from both interior and exterior sources.

04 – Enable

  • Enable – Completion of project.


Scope of Work 

The scope of work is where the author identifies the ‘division of labor’ for the whole project. This means it lays a set of guides down for who is responsible for what to avoid confusion and failure. This will be able to justify any price markup as you have supporting evidence and a breakdown of specific deliverables.


Assumptions is a nice way of saying “expectations” as you are telling the client what is needed from them to avoid any mishaps or failures. It is basically a laid flat article telling what an author needs from the client.


Now this is the more technical section as it describes what exactly you will be expected as a finished product. This gives the chance for the client to see what they will receive and expect through the course of project completion.

Ownership and Rights

This page explains the legality and ownership of things, basically, in most cases, it should be responsible for the author to own the rights of the project until the papers are signed off. Although this varies from the case.

Although, there are two categories which ownership & rights fall into:

  • Work for Hire – Authors don’t have the right, instead, the clients own the work.
  • Licensed work – Authors own the right but grant other parties the right to copy/distribute it.

Additional Costs and Fees

This is for any additional costs or fees outside of your job e.g. as a UX designer you may need stock photos, etc. This is where you state the prices you need from them to cover the costs of gaining these additional additives.

Project Pricing 

This page contains all of the pricing for everything. Although I must take into account the amount of time I think it will take me to do the project as well as consider the revisions.

Payment Schedule

This page contains all the invoices and what is to be expected from the structural outcome.

Acknowledgment & Sign-Off

Lastly, the acknowledgment and sign off-page must be presented in a clear and concise manner ensuring the client understands what they are signing. This is the “page of approval”  that ignites the start of your work.

What did I learn?

This book that Daniel has recommended us to read was worth it! The book simplifies pretty sophisticated stuff as it has allowed me to understand what a proposal is and what content is involved.





Leave a Reply

Your email address will not be published.