Office Cloud is an application that allows Independent Advisors the ability to manage their clients' wealth portfolios. Components are charts and tables that live within Office Cloud, used for analysis on client data.
Several teams had worked on different components within the application. However, many teams built these components in silos, geared for their specific needs, which resulted in different UI/UX patterns that didn't scale properly across the application.
- There was an absence of user research, the components where designed on assumptions on how and why users would use components.
- There where no set rules or guidelines on how to design feature components making it difficult to contribute future designs to the inventory of components.
- Designers where reluctant to do user research.
Since we already had existing software I suggested we do some usability testing to properly understand what was working and not in the components.
After running some usability test we found some key issues:
- Component titles provided little value to the users only telling them what type of chart they where looking at.
- Component settings took up a lot of space for data to
- Component settings where not intuitive for users
- Most users would set their parameters once
- Users where confused between what settings to find in the component vs under the gear icon.
One centralized location for component settings.
Titles that gave users more context. Tittles where tested for each component to see what would be the most valuable information needed to know what data is being displayed
Designing isn't about knowing everything, its about knowing what you don't know and figuring out the best way to find out that information.
- One centralized location for component settings eased the learning curve. Eliminating any guess work for users.
- Titles allowed the user to know quickly what data they’re looking at with what parameters where set.
- A foundation for components was created. Allowing designers to easily contribute to new components being designed.
- Component settings didn’t need to be visible since the title displayed pertinent information in the title and most users wouldn’t change settings frequently. Placing all the settings under the “gear icon” free’d up space to display more content.
- There was a clear understanding on what was working within components.
With a strong foundation for components designers can continue adding to component settings as we find new needs as new components come.