How do I define my product requirements?

Here is a list of artifacts that you should generate to describe your product or service.  Everything should be concise, and you should not get stuck in analysis paralysis, but you do need to have enough definition to bring the team together so they can work towards a common goal.

  • Clear description of the market problem that is being solved
  • “Elevator pitch” of the solution (preferably with images)
  • Description / analysis of first target segment
  • Buyer and User Personas
  • Detailed storyboards on top 1-3 typical workflows
  • Specific examples for details encountered in each workflow
  • Considerations for human factors / human cognition
  • Top level design directions to be followed by product design team
  • Lightweight functional description of minimum viable product (MVP)
  • Quick and dirty 2 year product roadmap
  • Any external business drivers (e.g. trade shows, funding runway, etc.)
Was this article helpful?
0 out of 0 found this helpful


      This website provides general information related to legal and business matters. It is intended for educational purposes only. This website does not and is not intended to provide legal advice. Although we take great care to make sure that all of our information is accurate and useful, if you have a specific issue for which you need actionable advice, please come to the Martin Trust Center in person to speak to one of our Entrepreneurs in Residence or consult a licensed attorney or other professional. No attorney-client, advisor, or other confidential relationship exists or will be formed between you and the Martin Trust Center or the Massachusetts Institute of Technology.
Have more questions? Submit a request

Comments

Powered by Zendesk