Open question to everyone.
Most of the requirements Product Managers create are functional requirements. i.e. indicating what the product or service must do or provide. i.e. the what.
But in many cases it’s not sufficient to simply define the “what“, and certainly with respect to software products, usability is a key issue to address.
There are many ways to address this, but I’m wondering if people out there have defined usability requirements, and if so, how and when (during the development cycle) they did it.
And just to be clear, by usability requirements, I’m talking about things like efficiency, intuitiveness and efficacy of the product/solution. These are subjective things in many cases, so they are harder to define and describe.
I’ll leave it there, but I’d really love to hear your thoughts. Leave a comment or send an email to onproductmanagement at gmail dot com.
Saeed