It's also interesting to repeat the creative briefs at the beginning of every project meeting. It helps the team distinguish between what the design is aiming for and how it is done . This not only loses production details, but also keeps the team focused on the big picture . Can this design reach our goal?
How does it work?
The important thing is to keep it short and simple. Our rule is only one side of A4. No one reads a long "traditional" brief. They usually Cork E-Bikes Zone contain so much useless information that they tend to hide what really matters. The goal of dismantling the problem and solving it into four simple components:
Section 1: Purpose
A short sentence about what this project (or part of the project) is trying to achieve. What problem are we trying to solve?
The important thing is to keep the purpose simple and high level. That way, you're free from technical details and constraints.
Example: Build an automated system that allows users to buy coffee online. Website visitors can read about and select roasts of their choice, purchase subscriptions or one-off products, and pay courier fees online.
Section 2: Main Targets or Personas
List one or two major personas for which you are designing this feature. This eliminates discussions about the most irrelevant personas or scenarios at the time. This can be an existing persona or a simplified version of them. Exam