Here is a PRD template

Here is an Example PRD

Purpose of PRDs

• Map out initial project and features
• Understand what will be built, why, and for whom
• Intended audience
  • Informing clients of proposed solution and progress
  • Recruit and align engineers
  • Track and drive progress as product manager
  • Inform other teams in DAML about your progress

General Guidelines

• Easy to read / organized
  • Keep the most important information at the top of each section and move less important information to the appendix
  • Proofread and use complete sentences
• Should be kept up to date throughout the project
  • Initially created through conversations between the product manager and client
  • Once the project is underway, incorporates feedback from the client and progress of the team
  • Keep revision history in appendix
• Briefly justify solution and other decisions with data (either from clients, users, or external research)

Overview

• 2-3 sentence executive summary of the project
• Describe the problem, client and their need, and proposed solution
• To be used on external materials (DAML website, slide decks, etc)

Definitions (if appropriate)

• Terminology commonly used by the client
  • E.g. Snapstreak: meaning you and your friend have Snapped each other (not chatted) within 24 hours for more than three consecutive days
• Acronyms
  • E.g. CTR (Click-through-rate): the ratio of users who click through a link
• Technical terms
  • E.g. Interoperability: the ability of different information systems, devices and applications (systems) to access, exchange, integrate and cooperatively use data in a coordinated manner, within and across organizational, regional and national boundaries, to provide timely and seamless portability of information and optimize the health of individuals and populations globally

Company