Tremor Technologies
Tremor is a new FinTech trading platform facilitating the allocation of risk in the reinsurance industry. Tremor connects buyers and sellers in a re-insurance marketplace auction, a first of its kind technology solution for the industry. Outside of Tremor, the entire reinsurance industry relies on voice broker and lengthy negotiations to complete an agreement.
As a UX Designer for UXL, Inc. I redesigned Tremor’s preference (bid) submission system.
Preference Design
Since Tremor serves as a marketplace auction product, the first feature participants see when setting preferences (placing bids) on the platform is the supply and demand curve interface. Buyers and sellers alike use this tool to submit preferences during an auction period, and once that auction closes Tremor’s algorithm optimizes the best matches between buyers and sellers.
The challenge inherent in redesigning the Preference Page was to create an interaction model that included all the necessary information to submit a supply or demand curve with ease and confidence.
State Exploration
An important focus of this redesign was to visualize all the different states a user would encounter in our interaction model.
The wireframes below from left to right illustrates the entire state exploration (click image to expand), starting from a user landing on an empty table (screen 1), the process of submitting preferences on multiple layers (screens 2-8), a fully submitted curve with collapsed layers where an underwriter would request an edit for re-approval (screens 9 & 10) and a post auction view (screens 11 &12).
Interaction Design
The most effective way to provide the user maximum content across layers was to remove the “Change Layer” button from the previous model and include an expand / collapse pattern so all layers could be represented or accessible. The inclusion of the "Expand All | Collapse All” serves to provide the user a comprehensive view of all plotted points or a pathway back to a closed table state.
By viewing the wireframes below from left to right (click image to expand), you can observe that we envisioned the use case where a user was navigating through a table with points plotted in every layer. Our recommendation was to include an anchored scroll function to the layer headings so that user would never lose his orientation of what specific layer was being viewed.