
A Product Brief is a stable, widely shared, "one-page" document describing the goals and benefits of a feature as well as the scope of a project.
The Product Brief is broken into 6 sections. (How to write a product brief:)
- Release Notes Summary: Describe the project as if writing release notes or a short press release. What are the key features? Why are they exciting? What is the benefit? (Like at amazon.com; here's a suggestion)
- User Problem Statement(s): What problems are we trying to solve? Be sure to define which users these problems effect as precisely as possible.
- Project Rationale: Why should this project be a priority? How does it drive revenue, cost reductions or customer-happiness? What research have we done? How wide-spread is the problem?
- Project Scope and Scale: What's in and what's out?
- Measuring Success: How do we measure success? How will we know when we are successful?
- Dependencies: Do customers need to upgrade? Are other features dependent on this one?What do we need from partners? What do we need outside of engineering?
- Key Links: Links to requirements documentation, wireframes/mock-ups, research, etc.
References:
- http://www.deviant9studios.com/blog/?p=474
- http://productdesignmanagement.com/how-to-write-a-product-brief/
- http://www.webdesignerdepot.com/2011/03/7-basics-to-create-a-good-design-brief/
- http://justcreative.com/2008/09/26/how-to-write-an-effective-design-brief/
- https://designschool.canva.com/blog/effective-design-brief/
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.