...
The design brief serves as the foundational overview for the project, outlining the key objectives, constraints, and deliverables. This section provides the necessary context for both the design and engineering teams to understand the scope of work.
Name of the project |
...
Clearly state the project’s name for easy identification. This should align with our |
...
Problem statement |
...
Define the problem the design is intended to solve. This should be a succinct description of the user’s pain point or the business challenge being addressed. For example, " |
...
users are having difficulty navigating the payment flow, leading to a drop in successful transactions." |
User story |
...
The user story provided by the PM (Jira ticket) should be documented here, reflecting the end-user’s need in the format "As a [user type], I want to [goal], so that I can [benefit]." | |
Task description |
...
Describe the specific tasks involved in delivering the design solution. This should break down the key steps that the design team will focus on to solve the problem. | |
Acceptance criteria |
...
This will primarily be provided by the PM (view acceptance criteria documentation) and sets the conditions that need to be met for the design to be approved. However, designers must also consider additional criteria, including:
|
...
|
...
|
...
|
...
|
...
|
...
|
Deliverables |
...
& success metrics | Define the expected design outputs and how success will be measured.
|
Relevant links | Include links to related tickets, product requirement documents, research, or any other documentation essential to the project. This ensures easy navigation for stakeholders reviewing the design. |
Align with user stories and acceptance criteria
...