Teamfight Tactics

PeerStreet • 2020 • Product Strategy, Design, Usability Testing, QA

As PeerStreet strives towards building a more streamlined and efficient process, ability to automate is vital to our success. Capturing data in our platform was the first step in this direction. In this project, I led the creation of a number of pages within our platform to capture data previously missing or disjointed across many other softwares.

Problem

How might we create data collection mechanisms within our Lender Platform (LP) that are intuitive for both entry and analysis?

Discovery

To understand the current process, we identified our target audience. We conducted interviews on different internal teams and members, focusing in on what worked and what didn’t.

We found the pain points to be:

• Inadequate reporting

• Free text entry (unstructured data) causing inconsistency of data across loans

• No support for multi-collateral loans

• Difficulty understanding borrower and guarantor structure

This boiled down to moving the data collection performed by the underwriting team from Asana (their tool at the time) to Lender Platform.

The project had 3 pieces:

1. Support multi-collateral loans

   Lender Platform was originally built around the idea of a single loan pertaining to a single property. Our newer offerings included loans containing a portfolio of properties, and LP had no way to support this.

2. Visualize borrower/guarantor structure

   The borrower/guarantor structure of a loan can often be complex. It can involve entities such as LLC’s and trusts, and it was not uncommon to see entities nested within each other. A visual representation could save lots of time in data entry and cognitive load.

3. Enable capture of property and borrower review data (Missing objects & fields in LP)

   Important data, such as a borrower’s background review, was recorded in Asana in an unstructured way. By pulling this data into LP, we could eventually build third-party integrations to automate processes such credit pulls.

Ideation & Iteration

Teaming with the Product Manager and Tech Lead, we:

• Discussed possible page structures

• Identified all the fields necessary and how to best organize, including understanding how quickly users need to move between fields, the level of detail, deciding on structured data

• Designed data model

Accounting for the different permutations that the borrower & guarantor structure may have, and playing out scenarios

Development & Launch