LSQ Report Center
Duration: 2.5 months | Role: Product Designer |Team: Kacper Scheibe (PM) & Katie Hoang
Tools used: Sketch, Abstract, Invision, Miro | Methods: Customer journey mapping, Wire-framing, Rapid prototyping, Competitive analysis, Moderated user interviews, Remote cross-collaboration
Problem
At LSQ, their dedicated user base are buyers and sellers. Buyers receive a number of different reports emailed to them, but these reports are not viewable in a centralized location on the platform.
This leads to:
Inconvenient auditing experience
Limited data visibility
Lack of scalability
Security concerns
Unavailable personalization
Purpose
To add a Report Center experience to an existing product. Users can view, parse through, and export their report at a minimum and customize and schedule their report as forward-thinking add-ons.
Challenges
Aiming for the North star
The project pivoted from an MVP to forward-thinking approach. This gear shift opened the doors for more complexity as we wanted to validate each use case of the product.
B2B User Personas
This is my first time working at a fintech company aimed at enterprises. This came with its own challenges of getting familiar with the space to build empathy for users and acknowledging scalability and technical limitations.
Cross-collaboration
Up until this point I have done UX projects independently. Here I was partnering up with a PM intern, engineers, other designers, POs, and the accounting team for input. This was invaluable to the progression, but also a different scenario to adapt to.
Discover
To get more insight into reporting needs and empathize with the user, I did some research with the internal accounting department as they closely represent the buyers (intended users of the product).
The outlining challenge uncovered from this interview was that the accounting team are power users. To design an inclusive user experience, the Report Center must be intuitive enough for non-tech savvy users and robust power users alike.
Additional questions I asked myself were:
How can users streamline tasks in a Report Center
What features in the Report Center require an evaluation of user permissions?
How can users customize their report?
Competitive Research
I did some market research on similar enterprise platforms that deal with file sorting, updating, and organizing. This helped me ideate how to incorporate the strengths and make up for the weaknesses of these products in LSQ’s Report Center to remain competitive.
Ideation
I made wireframes on Miro to get approval on them from all stakeholders before transitioning to high-fidelity on Sketch. This tool was immensely useful for quick idea mockups and made remote collaboration enjoyable. The comment boxes allowed me to comb through each user flow with a fine-tooth comb to assure the navigation was intuitive.
Areas to improve based on feedback received from prototype
User Permissions
Users were nervous about sensitive reports being viewed by people it wasn’t intended for. All buyers of a company can have access to the Report Center, but it is important to distinguish who can view all the data.
Solution - I added a modal to customize who can view the detailed report. Similar to Google Docs, users can elect to have it be private to them, seen company-wide, or by invite only with a link.
Report Customization
In efforts to build an inclusive user experience, I had to design for a less tech savvy user persona, which I didn’t have direct access to.
Solution - I did additional competitive research and looked towards similar enterprise products, like Salesforce, in how they approach report building. To design for an intuitive experience in report customization, I designed a modal to allow users to begin creating their report starting with a pre-populated company report that currently exists.
Design
After editing my prototypes with solutions that garnered positive reactions or noticeable ease in navigating the product, I translated the wireframes into hi-fidelity screens.
Home screen
Week-to-date is the default to view reports. This component was recycled from the design system to ease workload on devs.
Customized Reports folder
The actions in the Customized Reports folder were icons to be quickly recognizable for enterprise users.
Report Settings
Toggles were used instead of a radio button because it is an on/off feature a user can quickly switch between. If a user switches to opt out of a report this defaults the email notifications off.
Conclusion
I leaned a lot on my collaborators for research, enterprise insights, and design tools for producing deliverables in this project as the sole designer. It was an invaluable learning to see the project pivot in different iterations because that is realistic to the UX process in the wild. I am excited to see the Report Center get developed at LSQ and get real feedback from the intended users.
Improvements to be made in the future for this design:
Changing name conventions on reports for more distinction because all weekly reports are named “Weekly Reports” and so on
Option to batch schedule reports via multi-select within a scrollable modal
Allowing users to customize their default view when logging into the Report Center to fit user’s needs