FDSF
FDSF
FDSF
FDSF (Firm Data Submission Framework) was a application framework designed for stress testing UK banking networks designed and developed for Credit Suisse Risk / Finance Technology group. My role here was the lead UX designer in a team of 3 designers and we facilitated the design and delivery and helped define/refine the requirements.
FDSF (Firm Data Submission Framework) was a application framework designed for stress testing UK banking networks designed and developed for Credit Suisse Risk / Finance Technology group. My role here was the lead UX designer in a team of 3 designers and we facilitated the design and delivery and helped define/refine the requirements.
Service
Service
Application Design
Application Design
Application Design
Role
Role
Lead UX Design
Lead UX Design
Lead UX Design
Tools
Tools
Html / Axure / Illustrator
Html / Axure / Illustrator
Html / Axure / Illustrator
THE PROBLEM The Risk Reporting financial analysts needed the ability to add, edit, audit and view commentary on the dashboards and across all the dashboards. No such feature existed on the dashboards. The FDSF suite of applications contained several dashboards from Senior Management to Top Movers, Data quality management and Overrides etc. Users wanted this feature applied across all dashboards
THE PROBLEM The Risk Reporting financial analysts needed the ability to add, edit, audit and view commentary on the dashboards and across all the dashboards. No such feature existed on the dashboards. The FDSF suite of applications contained several dashboards from Senior Management to Top Movers, Data quality management and Overrides etc. Users wanted this feature applied across all dashboards
METHODOLOGY Finding time with Enterprise level end users is always crucial. Keeping that in mind the methodlogy and strategy we used was important - Group discovery and focus groups for effciency were considered for participatory design - Designs and rapid prototyped needs to be contstantly presented and iterated for testing - Unlike in consumer level apps design here is specific and complex - Reduction of stapes and friction was the goal based on user mental models - Users/roles/groups were defined - Given the multiple perspectives and geographies we used lo-fi prototypes nd documented pain points - Mapping out task flows was important
METHODOLOGY Finding time with Enterprise level end users is always crucial. Keeping that in mind the methodlogy and strategy we used was important - Group discovery and focus groups for effciency were considered for participatory design - Designs and rapid prototyped needs to be contstantly presented and iterated for testing - Unlike in consumer level apps design here is specific and complex - Reduction of stapes and friction was the goal based on user mental models - Users/roles/groups were defined - Given the multiple perspectives and geographies we used lo-fi prototypes nd documented pain points - Mapping out task flows was important
DISCOVERY Using contextual inquiries we identified the following features; - Designs needed to modular and extensible. - Cell level commentary was specific to a the PnL values on every dashboard - Dashboard level commentaries was across the application - Commentaries were made across multiple dashboards across FDSF - There were 2 specific groups of users MLRM and RFDAR - Each needed the ability to view the other groups comments but edit rights were provided only to comments withing their own group - Concurrent comments also needed to reflected - Users made an average of 80 - 100 comments a day and each comment could be over a 1000 characters or 3 + pages long. - Users required an audit and history trail as well as visual indications of any concurrent comments
DISCOVERY Using contextual inquiries we identified the following features; - Designs needed to modular and extensible. - Cell level commentary was specific to a the PnL values on every dashboard - Dashboard level commentaries was across the application - Commentaries were made across multiple dashboards across FDSF - There were 2 specific groups of users MLRM and RFDAR - Each needed the ability to view the other groups comments but edit rights were provided only to comments withing their own group - Concurrent comments also needed to reflected - Users made an average of 80 - 100 comments a day and each comment could be over a 1000 characters or 3 + pages long. - Users required an audit and history trail as well as visual indications of any concurrent comments
THE COMMENTARY MODAL With over 6 dashboards that the commentary had to span we settled on the idea of using a design pattern that would lay the commentary as a layer ABOVE the dashboard instead of integrating inside each application. Concepts we iterated based on a modified design pattern using a modal layer and a slide-in drawer over the dashboard. Users were provided with the ability to view commentary from individual cells on the dashboard and consolidated comments across all dashboards. - Comments could be filtered by users, groups and date ranges. - Edit rights were defined by role - Users were able to edit their own comments and append notes to others comments - Users would launch a commentary pane by clicking on a individual cell which would display comments to the specific Pnl. - The modal pane was provided the ability to be docked to the right side of the grid and function like a slide-in drawer.
THE COMMENTARY MODAL With over 6 dashboards that the commentary had to span we settled on the idea of using a design pattern that would lay the commentary as a layer ABOVE the dashboard instead of integrating inside each application. Concepts we iterated based on a modified design pattern using a modal layer and a slide-in drawer over the dashboard. Users were provided with the ability to view commentary from individual cells on the dashboard and consolidated comments across all dashboards. - Comments could be filtered by users, groups and date ranges. - Edit rights were defined by role - Users were able to edit their own comments and append notes to others comments - Users would launch a commentary pane by clicking on a individual cell which would display comments to the specific Pnl. - The modal pane was provided the ability to be docked to the right side of the grid and function like a slide-in drawer.
JOURNEY FLOWS - Journeys were mapped and problem spaces were identified. - Entry and exit points were identified as well as edit / read rights. - A key pain points we discovered were the need to visually represent concurrent comments being made in a cell - Other key issues was the ability to display over 3000 characters in one comment alone while keeping an audit trail for notes - Making it local and global across all dashboard(s) was yet another problem to solve for the design team
JOURNEY FLOWS - Journeys were mapped and problem spaces were identified. - Entry and exit points were identified as well as edit / read rights. - A key pain points we discovered were the need to visually represent concurrent comments being made in a cell - Other key issues was the ability to display over 3000 characters in one comment alone while keeping an audit trail for notes - Making it local and global across all dashboard(s) was yet another problem to solve for the design team
INTERACTION DESIGN - Color coded icons were provided to distinguish between user groups and to represent concurrent comments - Users would view the icon(s) and click to launch a modal with comments specific to the cell and PnL value. - The modal was provided with the ability to be docked and pinned to the dashboard - Concurrent comments prompted users to click and refresh by making a call to the server - Comments displayed were truncated and the "see more" showed the full comment - Comments were date and time stamped - The modal had a pinning/unpinning feature to make it a free floating modal if user required - The modal also had a built search feature
INTERACTION DESIGN - Color coded icons were provided to distinguish between user groups and to represent concurrent comments - Users would view the icon(s) and click to launch a modal with comments specific to the cell and PnL value. - The modal was provided with the ability to be docked and pinned to the dashboard - Concurrent comments prompted users to click and refresh by making a call to the server - Comments displayed were truncated and the "see more" showed the full comment - Comments were date and time stamped - The modal had a pinning/unpinning feature to make it a free floating modal if user required - The modal also had a built search feature
CONSOLIDATED COMMENTARY PANEL - One of the key requirements ask as well was the ability to view commentaries across multiple dashboards - We added an icon to the top right that would launch a commentary suite like modal. - Advanced filters were provided to left and the main content was displayed to the right.
CONSOLIDATED COMMENTARY PANEL - One of the key requirements ask as well was the ability to view commentaries across multiple dashboards - We added an icon to the top right that would launch a commentary suite like modal. - Advanced filters were provided to left and the main content was displayed to the right.
