ISG Playbook
APIs
INITIATE
IMMERSE
SYNTHESIZE
IDEATE
PROTOTYPE
IMPLEMENTWhat is a Project / Design Brief?
Project / Design brief sets the project tone by succinctly stating the Who, What, When, Why, and How.
A project brief helps you get aligned on expected outcomes for a user-centered design project.
A Project Brief is that essential document, which defines primary client's requirements for the project.
Typically, any project starts with this document. An executor sends the brief to the customer, whom should concretize the project. Based on the data provided, you initiate the project realization run-up or further discussion on the details.
A good brief should contain all the key information about the client’s project and businesses an executor needs to evaluate and proceed with the project development.
You should realize – there’s no universal brief template. Each type of project – design, web development, mobile app development, PR etc. - requires different briefs. Yet, the general brief structure stays same in most cases. It’s the niche specific elements that vary.
When outlining briefs, the amount of required data can vary significantly as well. In certain cases a few very short and general phrases are sufficient (when the brief’s just 1-2 pages long), while in some other cases all the major project points should be set out in details (then the brief can stretch up to 10-20 pages).
Here’s a quick winning formula for briefs: at the beginning 5-6 most important questions, aimed at getting the crucial information you cannot start without; next – detailed, additional information that may be required during the work phase.
Below is the list of the most common questions you are likely to find in any brief:
- Company profile/ description of the client:
- Project description
- Technical requirements
- Project Budget
- Project Timeline and Deadlines
IMAGE FROM: https://rosenfeldmedia.com/ux-team-of-one/3641/
HOW
- Write a Company Profile: Summarize who is client this is being created for, what is their focus, mission, and note who are their competitors.
- Determine what the project is about: List what are you hoping to achieve with this project and why, who is responsible for which areas, and any important details or focus points.
- What are the objectives of the project? SMART objectives = Specifics (who, what where when and why), Measurable (targeted metrics), Achievable (with resources and time frame currently have), Realistic (does it match organizational goals), Timely (able to complete within the targeted due date).
- Define your Target Audience? Who are you creating this for and why?
- Plan out the schedule and budget.
- What tasks / objectives are in scope and what are out of scope? If you don’t define this in the beginning, you will find your team with “scope creep”; asked to do work that wasn’t initially planned for that may add stress to your time and resources
- How will you measure success and definition of done?
For more information:
