FDSF

FDSF

FDSF

FDSF (Firm Data Submission Framework) was an application framework for stress testing UK banking networks, designed and developed for the Credit Suisse Risk / Finance Technology group. I led a team of three designers, facilitating design and delivery to the tech team while helping define the requirements. Tech stack: AngularJS

FDSF (Firm Data Submission Framework) was an application framework for stress testing UK banking networks, designed and developed for the Credit Suisse Risk / Finance Technology group. I led a team of three designers, facilitating design and delivery to the tech team while helping define the requirements. Tech stack: AngularJS

Service

Service

Application Design

Application Design

Role

Role

Lead UX Design

Lead UX Design

Tools

Tools

Html / Axure / Illustrator

Html / Axure / Illustrator

THE PROBLEM Risk Reporting financial analysts needed to add, edit, audit and view commentary on individual dashboards and across all of them. No such feature existed: comments were kept as notes in shared Word documents. The FDSF suite contained several dashboards, from Senior Management and Top Movers to Data Quality Management and Overrides. Users wanted commentary available across all of them.

THE PROBLEM Risk Reporting financial analysts needed to add, edit, audit and view commentary on individual dashboards and across all of them. No such feature existed: comments were kept as notes in shared Word documents. The FDSF suite contained several dashboards, from Senior Management and Top Movers to Data Quality Management and Overrides. Users wanted commentary available across all of them.

METHODOLOGY Time with enterprise-level end users is always scarce, so choosing the right methodology and strategy was crucial. • We ran group discovery sessions and focus groups to make participatory design more efficient • Designs and rapid prototypes were continually presented and iterated on for testing • Unlike consumer apps, the design needs here were specific and complex • Our goal was to reduce steps and friction, based on users’ mental models • Users, roles and groups were defined • Given the multiple perspectives and geographies, we used lo-fi prototypes and documented pain points • Mapping out task flows was essential

METHODOLOGY Time with enterprise-level end users is always scarce, so choosing the right methodology and strategy was crucial. • We ran group discovery sessions and focus groups to make participatory design more efficient • Designs and rapid prototypes were continually presented and iterated on for testing • Unlike consumer apps, the design needs here were specific and complex • Our goal was to reduce steps and friction, based on users’ mental models • Users, roles and groups were defined • Given the multiple perspectives and geographies, we used lo-fi prototypes and documented pain points • Mapping out task flows was essential

DISCOVERY Through contextual inquiries, we identified the following needs: • Designs needed to be modular and extensible • Cell-level commentary was specific to the PnL values on each dashboard • Dashboard-level commentary applied across the application • Comments were made across multiple dashboards within FDSF • There were two distinct user groups: MLRM and RFDAR • Each group needed to view the other’s comments, but could edit only comments within its own group • Concurrent comments needed to be reflected • Users made an average of 80–100 comments a day, and a single comment could exceed 3,000 characters (3+ pages) • Users required an audit and history trail, as well as visual indicators for concurrent comments

DISCOVERY Through contextual inquiries, we identified the following needs: • Designs needed to be modular and extensible • Cell-level commentary was specific to the PnL values on each dashboard • Dashboard-level commentary applied across the application • Comments were made across multiple dashboards within FDSF • There were two distinct user groups: MLRM and RFDAR • Each group needed to view the other’s comments, but could edit only comments within its own group • Concurrent comments needed to be reflected • Users made an average of 80–100 comments a day, and a single comment could exceed 3,000 characters (3+ pages) • Users required an audit and history trail, as well as visual indicators for concurrent comments

THE COMMENTARY MODAL With commentary spanning more than six dashboards, we chose a design pattern that placed commentary in a layer above the dashboard rather than integrating it into each application. We iterated on concepts using a modified pattern that combined a modal layer with a slide-in drawer over the dashboard. Users could view commentary for individual cells as well as consolidated comments across all dashboards. • Comments could be filtered by user, group and date range • Edit rights were defined by role • Users could edit their own comments and append notes to others’ comments • Clicking an individual cell opened a commentary pane showing comments for that specific PnL • The pane could be docked to the right side of the grid, working like a slide-in drawer

THE COMMENTARY MODAL With commentary spanning more than six dashboards, we chose a design pattern that placed commentary in a layer above the dashboard rather than integrating it into each application. We iterated on concepts using a modified pattern that combined a modal layer with a slide-in drawer over the dashboard. Users could view commentary for individual cells as well as consolidated comments across all dashboards. • Comments could be filtered by user, group and date range • Edit rights were defined by role • Users could edit their own comments and append notes to others’ comments • Clicking an individual cell opened a commentary pane showing comments for that specific PnL • The pane could be docked to the right side of the grid, working like a slide-in drawer

JOURNEY FLOWS • We mapped user journeys and identified problem spaces • We identified entry and exit points, along with edit and read rights • A key pain point was the need to visually represent concurrent comments being made on a cell • Another was displaying comments of over 3,000 characters while keeping an audit trail for notes • Making commentary work both locally and globally across all dashboards was a further challenge for the design team

JOURNEY FLOWS • We mapped user journeys and identified problem spaces • We identified entry and exit points, along with edit and read rights • A key pain point was the need to visually represent concurrent comments being made on a cell • Another was displaying comments of over 3,000 characters while keeping an audit trail for notes • Making commentary work both locally and globally across all dashboards was a further challenge for the design team

INTERACTION DESIGN • Color-coded icons distinguished between user groups and indicated concurrent comments • Clicking an icon opened a modal with comments specific to that cell and PnL value • The modal could be docked and pinned to the dashboard • When concurrent comments came in, users were prompted to refresh, which made a call to the server • Long comments were truncated, with a “See more” link to show the full text • Comments were date- and time-stamped • The modal could be unpinned to float freely when needed • The modal also included built-in search

INTERACTION DESIGN • Color-coded icons distinguished between user groups and indicated concurrent comments • Clicking an icon opened a modal with comments specific to that cell and PnL value • The modal could be docked and pinned to the dashboard • When concurrent comments came in, users were prompted to refresh, which made a call to the server • Long comments were truncated, with a “See more” link to show the full text • Comments were date- and time-stamped • The modal could be unpinned to float freely when needed • The modal also included built-in search

CONSOLIDATED COMMENTARY PANEL • A key requirement was the ability to view commentary across multiple dashboards • We added an icon at the top right that launched a commentary-suite-style modal • Advanced filters sat on the left, with the main content displayed on the right

CONSOLIDATED COMMENTARY PANEL • A key requirement was the ability to view commentary across multiple dashboards • We added an icon at the top right that launched a commentary-suite-style modal • Advanced filters sat on the left, with the main content displayed on the right

Designed in

© Copyright 2025

Designed in

© Copyright 2025

Designed in

© Copyright 2025