How to PRD

One of the jobs of a product manager is to write a PRD. PRD stands for Product Requirements Document. It is a ‘word of truth’ for the product and lists everything this is to know about it.

A PRD consists of the following components:

  1. Title — Self explanatory.
  2. Change History — Write down what version you’re editing and what changes you make to the document.
  3. Overview — Give a brief description of what the product is about and what your main motivations are.
  4. Objectives — What are you trying to let the customer do, why are you doing it?
  5. Success Metrics — What key metrics are you trying to hit and what are the numbers that you want to hit to indicate that you are doing something successfully?
  6. Messaging — What is the product tagline to tell your customers about the feature?
  7. Timeline — Describe the overall time schedule that you’ll be working with.
  8. Personas — Who are the target personas for this product and who is the key persona?
  9. User Scenarios — How will they use your product. Write out a full story about their experience.
  10. User Stories — Write out the distinct features along with a reason why each feature is important (same as Features In).
  11. Features Out — Write out what you explicitly will not put into the product and why. Remember, when creating an MVP you want to get rid of as much fluff as possible and only work on things to validate your hypothesis.
  12. Designs — Put in any early sketches and start linking them to the actual designs once they come out.
  13. Open Issues — What factors do you still need to figure out?
  14. Q&A — This is a place to put in any frequently asked questions as well as their answers. It allows you to point people to one center of truth instead of having people constantly email you.
  15. Others — This is a catch-basket for any miscellaneous things that don’t fit in the other categories.

If you don’t know the answer to some of these, write TBD (to be decided) as a placeholder and fill it in once you find out the answer. Once you’re done creating the PRD, shop it around and get input from your major stakeholders and people who will be working on the product. Go to your boss, your designer, and your lead engineer. Creating a solid PRD is a great way to ensure you will be delivering a great product.

Looking forward to the future, the possibilities are endless.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.