Complexity and Scalable Design: Fin-tech Enterprise Software

UX Design and Research reinventing a 20 year-old software that Private Wealth Management relies on daily.

Project Summary

Web App

Client

Large Investment Firm

My Role

UX Designer and Researcher

Project Duration

Agile Sprints of 2 weeks
First year of an ongoing project

Team

3 UX Designers
1 UX Products Manager
Each UX Designer has a pod, with a representative from Dev, Ops, Business

Deliverables

  • Responsive Templates based on Bootstrap and 8 pixel grid from 1600 screens to 760 tablets (React, responsive web app)
  • Workflow Tasks within application component functionality
  • On-boarding Flows for new and existing layered account structures (Both easy to learn and oriented toward veteran Wealth Managers)
  • User interviews and Usability testing within sprints on components and larger flows

Process

  1. Research, Synthesis,
  2. Design wireframes with team,
  3. Usability testing, Iterate Design (repeat),
  4. Groom User Stories, Hand off to Dev,
  5. More Feedback Discoveries, Iterate with enhancements and updates, (repeat).

User Needs

  • Ability to open many task-flows simultaneously, and exist in different states of completion.
  • Clear validation and rules at each step of completing forms and submitting actions to the larger database.
  • Ability to easily discover and create structures and hierarchies of account details.
  • Specific Vocabulary to at every instance of the product.
  • Effortless navigation and swift execution within the system.

How might we ease the process for new and veteran Wealth Managers to both create and view complex financial structures, and clarify pertinent rules to each step of contractual systems?

Challenges

  • Staying consistent with existing toolkit logic and across the app, so that the product is unified.
  • Finding time for iterations and for user testing within a face-paced schedule.
  • Meeting expectations of veteran users and assisting with their specific needs.
  • Understanding the limitations of the back end old databases and designing to make implementation with minimal changes to existing engineering.

Outcomes

Through iterative releases and enhancements we created a product that offered more explanation and more intelligent conditional flows.

Users have more:
• access to the multitude of information,
• clarifying feedback from the interface,
• control and agency.

Overall the new experience is more efficient for veterans of the old software and clearer for the new professionals.

Learning

We designed to ease cognitive load by addressing the exact tasks and needs. Discovering the vocabulary and inquiring about the specific uses enabled us to create clear paths through the software and prioritize navigation and information accordingly.

Updating an older software iteratively, in phases, required that the designs take into account the movement between the two systems; the production backend requirements and schedule influenced the design differently over the course of releases.