1. MIT Orbit Knowledgebase
  2. Product Management
  3. Defining a product

How do I define my product requirements?

Elaine Chen

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.)

Articles in this section

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

This website and all posts and content are intended for educational purposes only and for no other purposes including without limitation commercial purposes. Any other use must give proper attribution to the Martin Trust Center and is subject to certain legal rights contained in our license and terms of use. See full legal disclaimer HERE .
The content in this knowledgebase is subject to a non-exclusive license with share-alike restrictions and the terms of use of this site – which is available for your review HERE .

Have more questions?
Submit a request
Share it, if you like it.