It is too easy for executives to say "I don't know where to start" when defining new requirements for a product. The truth is, product requirements should be one of the simplest procecesses about building a new product.
 
Most of the time the requirements process is inconsistent across industries, departments and teams - even when building the samet ype of product. The methodology doesn't impact the overall success of the product if you do not start with the right questions.
 
Any leader can take a small block of time and work through the following questions
 
Requirements should not be complicated.
 
  • In 10 words or less what problem am I trying to solve? 
  • In 10 words or less what am I trying to build? 
  • In 3 sentences or less what does this product do? 
  • In a list form, what benefit will users have from this product?
  • In 10 words or less, how will users realize each benefit?