The statement at the beginning has a format, its purpose is to identify the task user and environment. This answers the what who and where which concentrates the focus of the project. Scope creep is a real threat to any project it can make a project literally unmake-able with additions and features that don't actually help alleviate the original problem. Bloatware is an example of this, its just a tacked on addition that no one asked for that has a very limited customer base, only the marketing team thought it was a good idea.  To make a product opportunity statement simply plug in your parameters in to this

Improve the [task] for [user] in [environment].

Remember to make it solution independent, the idea is to create a statement that demands a solution, not one that will embody the solution.

My original statement was, improve the computer and widget production flow for a 23 year old adult male in a limited indoor environment.

This was to long so I shortened it to,

To improve the desk experience for me in a small apartment.

If its a new product that has never been seen before or a copy of an old product, a customer will eventually use the thing. Even if it is just for your personal use, write down your needs so you can hit all your goals.

For this project I wrote down what I wanted in a desk.

Movable, clean, designated storage, expandable (plenty of room on desk surface), durable, clean European design, not white, plenty of leg room, always organized, standing desk with ability to sit down. 

if you actually interview a customer then observing them using a similar product or several products is the best way to understand how it can be improved. In addition to comments they make watch for minor issues they have and write them down.

Also this website is a great place to look for feedback, as most likely there is someone who has a similar project and has some suggestions of how it could be improved.

Next its time to simplify the comments and notes in to specific actionable solution independent items. For instance movable is not an easily quantified action so I will split it up in to if it can fit in to my car as a pas fail test and weight . the reason this is important is we are trying to take the burden of managing all the requirements and simplifying them where we can. Also some requirements are going to be more important as we will see later.

Movable => lightweight + fits in car

Clean => this is an aesthetic which is up to the designer however copying good design can help  with this part. 

Designated storage => organized

Expandable => variable working surface area

Durable => Tough (Mechanical engineering definition)

not white => low light reflection

leg room =>  open area beneath desk

standing desk with ability to sit down => adjustable working surface height