Popular posts

Ask them what exact requirements you are talking about? And for a requirement breakdowns :)

A tricky question without a simple answer...but in an ideal situation:

• I would have done user/audience testing on what was created and validated the product. I find that clients find it harder to argue with users feedback (though some find a way! sighhh) but most will understand and appreciate that you went and made sure it worked for those that intended to use it.

After all, our clients might not know everything about their audience and that's what product experts are hired for 👏

I believe a proper discovery session with the client, would help you understand what the client defines as "requirements".

Also, it's true that a lot of clients do not have a complete understanding of what they want their products to do, hence, a usability test is also advised, and if it meets their requirements, then that should be a go.

Finally, I also think it'll be a good move to carry your client along in your design process, so they're aware of what is, and what is not. That way, any iterations that need to be made, are made during the process, not after completed efforts.