UX Product Design Project Brief

 As a UX product designer, the Project Brief is the first major document I need to have for building a product. If there is not one already, I create one or add to one.

The following are the key questions that the brief needs to answer. I don’t always use every question, but I try to fill in as much as possible. It becomes the foundation of the project and becomes the source of truth. For this reason it must be updated should truths be changed or discovered. It is shared and open to all members of the project.

Project Name

Project title, code name and AKAs.

Dates & Milestones        

Start date. Launch date. Major deadlines and targets if any. Other critical project dates.

Description

An overall description of the product. What problems are we solving and why? What is the goal?

Key Team Members

Stakeholders and project owners. Who signs off? Product Owner, Project Manager, BA, Designers, Developers, QA, others.

Target Audience

Who are the users? What types are there? What is the sector? What are the typical characteristics such as education level, gender, profession. Are there any personas? If not, what might the persona types be?

Business Requirements

Why is the project going ahead? Objectives & expected outcomes. What does success look like? What ROI? Link to a roadmap. What KPIs?

User Requirements

User needs? Special needs? What problem does this product solve for the user? Internationalisation?

Other Requirements

Must haves & must nots. Required elements.

Unique Selling Point

What makes this product different from the competition? What marks it out? Why use our product instead of another’s.

Brand Guidelines

Requirements to convey brand personality such as tone, logo, images etc. Link to guidelines.

Elevator Pitch

For (customer) who has (customer need), (product name) is a (market category) that (one key benefit). Unlike (competition), the product (unique differentiator).        

Design

Describe the product’s desired look and feel by using adjectives and short phrases e.g.: Easy to look at, edgy, classic, up-to-date, crisp, modern, traditional, comical, serious, friendly, understated, minimalist etc.        

Past Work

What has work well? What could work better? What did not work? Do we have any analytics?

Technology        

Describe the technology used and any limitations or special features. What is the database? What is the user interface? How is the project viewed? Mobile first responsive design? Multiple platforms requiring different designs?        

Related Products & Projects & Dependencies

What is the product based on? Does it intersect with another product? Who are the competitors? What is a good example and a bad example? What is a good source of inspiration?

Other Notes

Anything else relevant to the project? How do we communicate and track work? Slack? Jira?

Comments

Post a Comment

Popular posts from this blog

What are the Four Steps of the Design Cycle?

  1. Requirements Gathering Understanding the business needs and what its goals are. Be sure to understand the problem or challenge the business wants you to solve. Understanding the users and what their needs are. Understanding the capabilities and limitations of the technology being used. 2. Design Alternatives Begin to create solutions. Brainstorm ideas that meet the needs of the user and solve the problems of the business. See how others have solved similar problems. 3. Prototyping Model potential solutions so they can be tried out and tested. On paper or using tools. (see Figma, Invision, AdobeXD etc.) Prototypes can be simple sketches and wireframes or rich, interactive demos. 4. Evaluation Test and evaluate the prototypes on users. See what works and what needs adjusting. Go back to steps one, two or three as needed. Bonus step: Development Once a design has been tested and agreed upon it goes to development, but the designer’s job is not finished. The design will inevitably...
Read more

Where do you sit?

As a manager of people (UX designers and front end developers in my case), where should I sit? I am being literal here. Where should my desk be? Should I sit together with the other managers and heads of, or should I sit with the team? I know this sounds petty but it is important. This question was raised the other day and of course this other manager did not think that I should be sitting with the team. She is one of those managers that thinks that they are above mortal worker drones and should be aloof to the lower levels of creativity (you can probably guess that this attitude annoys me). Of course it can be useful to sit as a group of managers. This is great of high level planning and epic thinking, but to be honest, that stuff does not take too long and most time is spent putting them into effect. This all happens “lower down the food chain” where the creatives and builders get to work making the dream come true. This is where a manager should be seated. Not so that he or she can ...
Read more