Ravelin client dashboard
I worked on the design and build of the first Ravelin client dashboard home page. We needed to build a launchpad that would be more useful in showing the state of fraud for clients' business analysts and summarizing all of Ravelin's growing number of useful features and data.
Additionally, I was creating systems and frameworks, to organize information and help users understand how a new feature on the Ravelin dashboard will work, and to maintain and extend Ravelin's style guide.
Here are samples of the work I shipped.
Actions button interaction
Ravelin actions are core to the product and fraud analysts who use the dashboard. It's the most common interaction performed by analysts, who are reviewing customers for fraud, need to make decisions on whether a customer is genuine, fraudulent or should be flagged to the watchlist.
Clients might allow and accept orders from likely genuine customers whose scores are below a threshold. Whereas high-risk customers with scores above a threshold, and fraudulent behaviour are prevented from processing their orders. Sometimes analysts require additional evidence if a customer is either fraudulent or not, adding them to a watchlist before making a decision for allowing or preventing orders from a customer.
Ravelin API docs
The API docs needed a version two for a few reasons:
▸ Marketing — We needed both developers and managers, for potential and current clients, to enjoy using and looking at our docs.
▸ Navigation — In version one, the navigation needed to be revised to consider the growing content of the docs and hierarchy.
▸ Complex tables — Reduce the number of nested tables inside multiple pop-up modules and redesign tables in docs.