Problem Statement
I was tasked with creating the first ever experience for the Ratings product used by Insurance carriers. Every Insurance carrier uses proprietary and confidential Ratings algorithms while creating new products.
We started out by clearly stating the problem definition, the type of users we want to address, what are their needs, and what success meant for this product.
The interface for Ratings needed to have a list view on steroids. In a common case, every company that uses Ratings algorithms will be dealing with hundreds of such algorithms. So, the ability to filter and store these filters so that they are available at a later point became very important.
Once a Ratings algorithm product was ready to be uploaded to a system, the user can specify meta data regarding that product and it is ready to be in the system. The user can then trigger a review by submitting it to others. Other users can then test it, and approve it. After a Ratings product is approved it is ready to be pushed to production.
