Transforming a big data platform.

The Challenge

I redesigned a version of one of the central features within Vividly’s portal. By focusing on creating a more streamlined process, I created a workflow that allows our users to work faster than before.

*Due to an NDA, there is limited visibility on this project.

guiding question

What challenges do Vividly users face when managing repayments, and how might the platform address them?

guiding question

What challenges do Vividly users face when managing repayments, and how might the platform address them?

guiding question

What challenges do Vividly users face when managing repayments, and how might the platform address them?

User Research

To understand the current state of the repayments' workflow, I talked to a handful of different users who have had differing experiences with repayments. In these interviews, I found these grounding insights:

Repayments are distinct from regular transactions - they vary across companies and suppliers. As a result, there is inconsistency in how repayments are managed.
Clarity and detail matter for tracking - users need context within transactions to understand what the money was for, who it was to/from, and how it fits into the financial picture.
The current repayment flow is full of friction - the process is time-consuming, confusing, and not streamlined, leading to frustration and errors.

Repayments are distinct from regular transactions - they vary across companies and suppliers. As a result, there is inconsistency in how repayments are managed.
Clarity and detail matter for tracking - users need context within transactions to understand what the money was for, who it was to/from, and how it fits into the financial picture.
The current repayment flow is full of friction - the process is time-consuming, confusing, and not streamlined, leading to frustration and errors.

Repayments are distinct from regular transactions - they vary across companies and suppliers. As a result, there is inconsistency in how repayments are managed.
Clarity and detail matter for tracking - users need context within transactions to understand what the money was for, who it was to/from, and how it fits into the financial picture.
The current repayment flow is full of friction - the process is time-consuming, confusing, and not streamlined, leading to frustration and errors.

Ideating & Design Principles

After conducting the interviews, I executed a Crazy 8’s exercise that was rooted in How Might We’s and User Need Statements to brainstorm.

This exercise yielded an abundance of ideas to choose from, and I narrowed down the design principles that would shape the future of the repayments process:

📍Familiar - repayments should feel intuitive and consistent, even when repayment scenarios differ.

📍Supported - the process should integrate smoothly into existing workflows and minimize friction for users.

📍Informed - each repayment should provide enough context to help users track and understand their financial picture.

Low, Mid & High Fidelity Prototyping

Once the user needs were finalized, I began sketching low-fidelity user flows to test out different ideas.    

I wanted to pinpoint the following:

where the repayments process could become faster
how information could be best displayed for users.

I am unable to show the medium and high fidelity prototypes, but I am happy to answer any questions relating to the process of building the prototypes.

Outcomes

Presentation & Impact

I was presented this redesign to Vividly’s then Head of Product, and gained some useful feedback to inform quick changes before handing it off to the Product Manager.    As of September 2022, I was told that the redesigned feature will be featured in the next built version of the platform.

Explore Website

additional work

Accessibility Audit

During my internship at Vividly, I also conducted an accessibility assessment on Vividly’s portal and cross-checked it against WCAG2 guidelines to ensure that the platform could reach the most amount of users.

I communicated with our engineering team for these improvements and, as of September 2022, the changes were on the roadmap for future development.