- One of the most important tools to help you communicate, is a well-written Product Requirements Document, or PRD.
- A PRD is an explanation of the specific product, you're building. It clearly explains why you're building this product, both for your internal goals, and for your customers, along with the exact scope, the features, and functionality in the product. Similarly, they should convey what you're not building. So the PRD tools for everyone involved in the product.
- At first, you'll use it to get all of the key stakeholders on the same page, and help the team understand the project.
- And then later, it will be continuing, as a living document.To be updated periodically, to document changes, and to evolve until the product is finally released.
- The outline for the PRD, begins with the title. It will include a change history, that notes what changes were made, by who, why, and when.
- There will be an overview section of describing what the product is all about. Objectives will be clearly stated and quantified. The success metrics will be noted. Messaging will be included, including with the orientation and a detail of the product messaging marketing.
- The overall schedule will be listed in the timeline. Target personas, your customer user personas will be defined.
- You'd include stories about how those target customers will actually use the product, in these user scenarios. You'll have distinct prioritized features with the explanations, as to why the various requirements are important. You will address features out, what are you not doing.
- What features might someone think could fit, that are not included, and why? You'll include your design sketches, both the originals and the actuals. You'll note whatever open issues are present and you'll include documentation of prior Q & A. And when you bring those all together, you'll have an effective Product Requirements Document, to guide your process.
