try2.png

Reporting Administration - Sell Side Monitor

Tool for our internal reporting team. First part of a comprehensive overhaul to our reporting business.

Please view my figma presentation for an overview of this project.

LoanStreet’s Reporting Administration Hub

Responsibilities: UX + UI Design, User Research (Interviews, Testing, Prototyping), Product Management, QA

Product Overview:

  • LoanStreet’s Reporting Team is responsible for tracking the health of our clients’ loans on a monthly basis (More than one million loans! Every month!) The team’s expected output is to provide each client a monthly report detailing the health and activity of their assets.

Outcome:

  • As the sole designer on this project, I created a central hub for all things Reporting-related in the LoanStreet universe.

  • Reduced manual, error-prone processes through intelligent system design, improved efficiency and data accuracy, and monthly reporting time from 7 to 3 business days

  • The Reporting Dashboard encompassed functionality that resulted in the deprecation of multiple (5+!) brittle, convoluted legacy workflows


  • The top tile would serve as a utility for team members to filter by reporting month, team member and status - allowing all members of the team to easily and quickly construct a unique view.

  • The table itself was designed to allow for each row to accommodate necessary information per institutional client. Affordances provided key content on hover, while the cells and rows themselves could be edited and autosaved with ease.

The Launch

  • I worked with and PM / BA to validate the v1 vision and break it down into epics, user stories and tasks

  • I collaborated weekly with Engineering to actively QA in our staging environment, ensuring an effective solution for our production environment

  • We successfully hit our release date and introduced the new tool to the reporting team

  • I created a space for users to submit feedback and feature requests for the Reporting Administration tool, which is still fielding positive feedback and feature requests


The Problem

  • Team members relied on a haphazard Google Sheet to track the progress of a client’s report month over month, as well as multiple legacy-driven workflows to ingest, clean and ship data. 

  • My goal was to create a place in-system for the team to track the progress of their reports, ensure their monthly processes went smoothly and provide a way to highlight and problem solve any issues they encountered. 

Each month the Reporting team would use this clunky spreadsheet to track the status of each client’s monthly report across a set of statuses (not started -> finished). Since speed of report processing was a critical need, this posed a risk of clients being overlooked or ignored


User Research + Discovery

Once we understood the current tooling and user needs, we mapped out the user journey of the reporting process. This allowed us to determine what the opportunities for improvement were and where they could be implemented.

User Interviews

  • I audited every off-platform asset and legacy-driven workflow associated with their monthly reporting tasks

  • I conducted user interviews to identify pain-points in their current processes

  • Every month, I’d sit with the team to observe the ups and downs of their “reporting week” in person

User Testing

  • I created a prototype and conducted two separate rounds of testing

  • I synthesized the findings with my collaborators (a PM and BA) and detailed functionality needed for v1

User Flow

  • We arrived at a high fidelity flow that focused on the crucial actions the team needed to accomplish - assigning an institution, moving an institution through the reporting process manually and leaving a comment for other users to better understand the status of a client

  • After testing the prototype with all members of the reporting team, we broke our results into clear sections: improvements, not improvements and results


Design

The research and testing led to the following design tenants that would drive the functionality of our first release

  • The order of operations should be clearly outlined and available in appropriate and easily accessible means

  • Workflows should be safeguarded in a way that builds confidence in task completion

  • Actions should be provided in context of what needs to get accomplished respective to what stage of the reporting process the seller is in

Inspiration abounds regarding dashboards, so to get started we chose financial and workflow driven dashboards to draw inspiration from.

These iterations showed the different directions and styles I considered before landing on our ultimate vision.