Renaming Documents Feature on Pathways

Pathways are a key part of the Ansarada platform. They guide the progression of activity from pre due diligence in scorecards, through to execution of the deal itself in a data room.

The absence of functionality for renaming documents in Pathways is a frequently reported pain point for advisors. Advisors report that their customers frequently upload documents to pathways with inappropriate names. This is particularly an issue for use cases where advisors are using pathways to prepare their clients for a deal that will later be transacted in the data room. They report that it is important for documents to be labelled correctly before they can be surfaced in the data room environment.

I led this project with the Product Manager and the Lead Engineer. I was the sole individual responsible for User Experience and I personally created the deliverables that you will see in this case study. I saw the project through from the kickoff meeting, to the launch, and through multiple rounds of iteration afterwards.

I conducted a set of interviews with customers and used it as the basis for customer-specific dynamic content.

I began by digging into our historical data, surfacing user pain points and barriers to conversion. Using anonymous session recordings, I was able to put myself on our user’s shoes and identify the pain points when organising documents.

This project drastically affected multiple different areas of the organization, which at times had conflicting interests. I conducted interviews with representatives from Leadership (CEO), Product, Sales, Customer Services, and Engineering to understand each part of the company’s unique requirements and concerns for the design.

Once we had a solid direction for the design, I began to produce multiple different variations of wireframes. I then put the designs in front of users and stakeholders for testing and feedback. This helped me to narrow the design down to three major variations, which I used to establish a single design framework, and thus move into the final design

After the first interaction of design got approved I began to create the high fidelity designs. During this phase, I worked even closer to the development time.
On this case study, I’ve used 100% of the Ansarada component library, and by that reducing the delivery time and scope of this project

Pathways are a key part of the Ansarada platform. They guide the progression of activity from pre due diligence in scorecards, through to execution of the deal itself in a data room. In Pathways, only had document organisation, which provides a method for creating subfolders but we know this isn’t working well for our customers.