Corvus Design System

Team member in reorganizing and restructuring an existing Design System.
CDS image.png


Corvus’s mission is a simple one: to make the world a safer place. This isn’t just a high-flown idea — Corvus is actively helping our policyholders to predict and prevent adverse events, as well as supplying the coverage that helps them withstand events when they do happen. In addition to helping our policyholders, Corvids are given the support they need to help make their worlds — big and small — safer, through a number of Corvus-led initiatives.


When quoting a policy, Underwriters have difficulty finding the most competitive range. Underwriters when quoting "do what they think feels best." Usually the more experienced Underwriters "go with their gut" but more junior Underwriters do not always know the baseline when quoting. They can ask more experienced Underwriters or even Brokers, but if they are busy they are usually left questioning and guessing. The Product team wants to help Underwriters make more confident decisions when quoting and not rely on emotions.


There is currently a tool available to Underwriters called a "Sold to Target" (STT) tool. It is very limited in terms of filtering and lives in Excel. We want to use this as a baseline to build something within the Crowbar.

In order to make sure our assumption is correct, we plan on interviewing at least 5 Underwriters and doing User Testing to make sure we are building what they need. 


If Underwriters are meeting profitability targets more often, then they will be able to send more quotes out and get them approved. This will profit Corvus and help speed up the quoting process while getting more clients.  

We will know this will be successful when Underwriters are hitting the premium more often.


As the Senior Product Designer, I worked within a scrum team of a Project Manager, 2 Engineers and 2 Data Science Analysts.  I was responsible for participating in user interviews and user testing, creating and wireframes to clarify product requirements, creating interactive prototypes, and designing high-fidelity mock-ups for engineers.



User Interviews



User Testing
Takeaways from Research & Planning :
  • Use some pages from our existing shopping flow to save time for design and developers

  • Redesign the flight search page to display price difference while utilizing spacing

  • Eliminate elements we don't need to create more time to launch an efficient MVP

  • Create a way to allow the user to select which leg of the flight they want to modify




Final Product

Key Takeaways

  • Great learning experience of working on a Scrum team with a big project and tight deadline.

  • Great collaboration with Tech Lead and Project Manager.

  • Overall myself and my team put a lot of work into this project. Unfortunately there were various technical restraints and allowances that were communicated to us with little time to adjust. Though we were able to make these adjustments when needed and really showed how quickly we were able to adapt.


  • Would have loved to have done user testing and A/B testing. This would have given more validation to the designs and would have solved design question faster, thus saving time on a project that already has a tight deadline.