I redesigned the portfolio model flow on Fartherās wealth management platform, used by their financial advisors and clients. As the lead designer, I collaborated with four engineers in a three-week iterative process.
I redesigned the portfolio model flow on Fartherās wealth management platform, used by their financial advisors and clients. As the lead designer, I collaborated with four engineers in a three-week iterative process.
At the time, the portfolio model flow was clunky and difficult to navigate, despite being one of the heavily utilized flows for Advisors.
If we simplify the steps, make data interactive, and provide detailed information, this would lead to users making data-informed decisions and increasing Fartherās AUM (Assets Under Management).
I simplified the portfolio model flow to help Advisors and Clients make informed investment decisions through a comprehensive selection process.
We reached a crucial point in Fatherās journey. Our Advisor team tripled, signaling an expansion in our operations. With this growth came the realization that our MVP flows within the Farther platform were due for an upgrade,particularly the process of selecting portfolio models by Advisors or clients.
It was essential to define our target user early on. We commonly referred to our user personas, representing our target audience and their investment approach:
When I engaged in the user discussions with stakeholders, we leaned on these personas as our guiding lights. Ultimately, we reached a consensus: Advisors would serve as the primary users, however we acknowledged the need to accommodate secondary users.
This is where I delve into our current product, identifying problem areas, scoping out technical details as needed, and understanding the intricacies of our system.
During the visual audit, I worked with the designer of the MVP flow, probing into the rationale behind past decisions. Drawing from these insights, I propose design enhancement for clarity around new and existing data.
In addition to conducting a visual audit, I mapped the user journey. This enabled me to identify and eliminate redundant screens, as well as rethink the sequence of steps.
Now that Iāve grasped the problems, at high level:
If we simplify the steps, make data interactive, and provide comprehensive details, users can make data-informed decisions, thereby contributing to the growth of Fartherās AUM (Assets Under Management).
With a focus on user experience, we aim for users to effortlessly navigate through the flow, anticipating that it will yield the following outcomes:
I analyzed competitors to pinpoint opportunities for aligning the Fartherās portfolio model flow with user expectations while also setting us apart in the market.
Drawing from these insights, I made informed assumptions about user behaviors:
After drawing inspiration from competitor research and honing my vision, I quickly sketch wireframes to ensure the new flow is coherent and contains all necessary data. Once finalized, I present the wireframes to my design team for feedback and refinement.
During implementation, new considerations prompt scope adjustments and questioning of certain elements as the team interacts with the actual product. This necessitated collaboration between me and the engineers to refine micro-interactions. Some changes included:
During the project, I collaborated with the engineers to accurately implement the designs. As a startup in continuous production, we focus on user experience by self-testing, gathering user feedback, and making iterative enhancements to ensure our platform meets our target audience's needs.
This solution was launched in 2022 alongside other projects, with these estimated outcomes:
Engage with users ā In retrospect, I could have showcased my early designs to our main users, the Advisors. Eventually, juggling multiple projects and time constraints taught me to find ways to interact with the users, ensuring this step is not missed during heavy production.
Testing amid constraints ā While testing and validating ideas for each project would be ideal, it wasnāt feasible during our production-heavy phase. However, overtime, I form hypothesis to guide my design decisions when testing isnāt possible.
Revisiting color ā My past excessive use of color in UI design is a lesson learned. After discovering the book āRefactoring UIā by Adam Wathan & Steve Schoger, Iāve adopted a monochromatic scheme for color-intensive UIs. This book now guides my future projects.