Bob Angus 5 Comments A creative brief also known as a design brief is the best way to communicate key elements and objectives of your creative project.
The product-brief writing is perhaps the activity with the highest ROI, as it costs very little and brings great value, as well as saves a lot of time and money while preventing wrong directions and unexpected outcomes. Here is a list of eleven guidelines and insights about how to manage your product-brief.
The product-brief is a map. A few working hours on a good brief writing at the beginning of the project can save you a great deal of time and money. A design project without a brief is like an outdoor trip without a map.
It is much faster and safer to reach your destination when you have a map with a planned route. All should be involved in writing and approving the brief, and of course, acting according to it 3. The product-brief is under the design manager responsibility Writing and managing the product-brief is a crucial part of a design process.
Keep it short and simple The product-brief should define the product in a simple and short way. Avoid complicated and long text with too much background details. A typical product-brief should be between 1 to 3 pages long.
The product-brief is a live document The product-brief is written at the beginning of the project, yet it is necessary to keep updating it all project long. You never know everything in advance; new information, insights, and decisions are usually raised during the project and affect the product-brief.
It is important to keep your brief and all project members up-to-date. Product-brief can and should include questions Of course it is better to have all the answers in the product-brief, but it is absolutely normal to have open questions as part of the brief at the beginning of the project.
In such cases, you should add notes to the brief about the actions and timetable needed to answer these questions. Product-brief should also include the excluded It is much easier to illustrate and define a product when describing both the included and the excluded parts and aspects.
This might save some misunderstanding and mistakes. The soft-attributes are more elusive and complicated to define, but not less important. Here is a simple way to distinguish between the two — a product-brief should focus on the long-term aspects of the product — the ones that last forever.
I prefer to use a Product-Brief Checklist just to remind me the main titles it never covers the whole points that I have to consider.A creative brief is commonly used in advertising and design agencies, but it’s a useful tool for a project of any size, and for freelance designers and large corporations alike.
In an agency setting, project stakeholders may include a marketing team, creative team, executives, and clients.
Alistair Cockburn's Writing Effective Use Cases is an approachable, informative, and very intelligent treatment of an essential topic of software design. "Use cases" describe how "actors" interact with computer systems and are essential to software-modeling requirements.
For anyone who designs software, this title offers some real insight into writing use cases that are clear and correct and. The Online Writing Lab (OWL) at Purdue University houses writing resources and instructional material, and we provide these as a free service of the Writing Lab at Purdue.
A design brief is a written explanation - given to a designer - outlining the aims, objectives and milestones of a design project.
The Gateway to Up-To-Date Information on Integrated 'Whole Building' Design Techniques and Technologies. The goal of 'Whole Building' Design is to create a successful high-performance building by applying an integrated design and team approach to the project during the planning and programming phases..
WBDG Updates. 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.