In rondesignlab we often have to work with briefs. Generally, what the customers send us doesn't really disclose the purpose and objectives of the future project. What they send is a formal document with a list of pages describing possible functionality. Many developers as well as customers face with this issue.
Standard briefs do not help to identify the key issues or identify the ways of solving them. At best, they will contain links referring to competitors.
We would like to note that this article is likely to be useful for those who have never faced with the development of the product, since more experienced customers usually already have their own experience and views on the subject.
There are many options how to write briefs for the site. All of them are quite standard and are brought to the general pattern. Unfortunately most of them are of small information for the performers, so there are several ways how to solve the problem with the task for developers
1. Hire a manager who is familiar with the sphere of your project.
2. Make sketches on the paper and attach them to the formal brief.
3. Start with creating the prototype and design for the future project.
The first two steps are all more or less clear, but the last step must be considered in detail.
Any competent project starts with wireframes and design for them. This is how the approximate diagram of the stages of creating the project in our studio looks.
This development process solves the main key development issues
1. After the customer answers the list of standard questions he will have an idea of what he needs and what he wants on the first phase.
2. As a result we get the working clickable prototype with the design ready and logically connected pages.
3. When the developers start working there is a clear detailed task of what is needed to be implemented.
4. The time of team working hours for creating the project reduces.
We believe that there are no perfect briefs for projects as all projects are unique, but there are key issues that must be considered. These questions will help designers to quickly plunge into the project and recommend useful and interesting solutions for your project.
Here is a list of questions that need to be mentioned in the brief.
1. What you do not like about the current situation (if you have a finished product)?
2. What problems should solve the future product (increase sales, enhance brand awareness, inform the users)?
3. The main competitors, description and links (preferably examples of competitors doing better than you)?
4. What do you actually do (what problems you help to solve for your customers)?
5. Why do you need your future product?
6. What must necessarily be?
7. Who is your target audience?
After the answer, as a rule, there are specifying questions that are usually solved personally in dealing with customer and developers.
We also would like to note that the creation of any product is a marathon, you need to go through many stages to achieve the desired result. Therefore, we must have patience and try to answer all the questions that you are asked, as the customer is, in any case, more familiar with the subject than a performer.
This article describes only our vision of the process, it has been described to help customers make better briefs that will be more informative and useful for developers.
P.S. If this article is useful to you, please share it with your friends.