Lessons in Product Dev. - Because You Can, Doesn't Mean You Should
Product development, be it hardware or software, usually begins with a definition of product requirements. Best case, those requirements are informed by a hefty amount of market research and a preliminary engineering/development assessment. Worst case (and most commonly), the requirements is a list of "wouldn't it be cool if...s" that are based on a competitive product, which continue to change in the midst of developing your product.
In this session we'll talk about...
What makes a good product so good (they do one thing really well)
How to identify the feature that can make your product successful (your user testing may not reveal it)
How to manage feature creep along the way (grow a pair)