Back
App Unification & Information Architecture Overhaul
February 2025
To deliver a seamless platform experience, I led the unification and information architecture overhaul to merge two applications into one streamlined platformed. Includes conducting Card Sorting workshops with traders and desk heads and internal workshops to understand users' mental models.
To deliver a seamless platform experience, I led the unification and information architecture overhaul to merge two applications into one streamlined platformed. Includes conducting Card Sorting workshops with traders and desk heads and internal workshops to understand users' mental models.
Basics
Stakeholders | Business sponsors of markets risk organization |
|---|---|
Collaborate with | FE/BE developers, architectures, product owners, project managers, business analysts, and QA |
User Base | App 1 1,500+ daily global users 10 different user groups App 2 Subset of the users of App 1, ~ 200 users |
Project Sizes | A large app with multiple layers of information architecture A smaller app with 5 modules |
Project Type | App 1 Enterprise, web app, mobile app, migration/overhaul from legacy to next gen application App 2 Enterprise, web app, data-heavy/visualization app |
My Role | Lead UX designer/researcher |
Context
This project is related to Markets Risk Platform project.
Migrating a legacy version of the application to a new application with complete UX/Product overhaul
Legacy version entailed 16 individual pages + 9 sub-pages
Old information architecture was convoluted and provided unnecessary redirection to different pages to users for tasks that overlap one another, and UX writing for the menu items were also very technical and outdated thus adding more to the confusion
Goal is to merge two applications due to the overlap of the user groups and to deliver a consolidated and seamless platform for them
Highlights
Conducted card sorting workshops and interviews with different user groups
New menu is now with four main categories of pages with fly-out menu so users can expect what they will see before entering the page
Launching in September 2025, feedback unavailable at this date
Details
Using wireframes instead due to confidentiality reasons
Legacy version
Previous menu of the application had items ordered in the chronological order of when the pages were developed, and not to do with the actual usage and interest of the users. This resulted in users taking longer to navigate to their destination as they're given too many options with technical-jargons (e.g. including words like "workflow" and multiple acronyms).
For some of the menu items, once clicked users were given sub-pages, which then they had to make another decision and click again to get to their destination. This structure is inefficient as it gives users unexpected options after they have already made a choice from the first layer of the menu.
New version
After the research, I consolidated the menu items into four different categories. First tab is a single-page, a merge of five different items from the legacy menu item because they were all part of same user journey where user disposes alerts/tasks day to day and search for those items.
The remaining menu items are fly-out menus for transparency of where user can navigate to. Each menu item is categorized into relevant buckets. These buckets are named so that they are task oriented instead of an abstract description of what the page entailed (which is what the legacy version had), for example "Reports & Dashboards" and "Hierarchy & Permission". The new menu is also dynamic to the user's permission so that they are only seeing items that are relevant to them. App 2 mentioned above is also merged into this new menu thus delivering a more consolidated experience to our users instead of having them switch between two different apps back and forth.
Basics
Stakeholders | Business sponsors of markets risk organization |
|---|---|
Collaborate with | FE/BE developers, architectures, product owners, project managers, business analysts, and QA |
User Base | App 1 1,500+ daily global users 10 different user groups App 2 Subset of the users of App 1, ~ 200 users |
Project Sizes | A large app with multiple layers of information architecture A smaller app with 5 modules |
Project Type | App 1 Enterprise, web app, mobile app, migration/overhaul from legacy to next gen application App 2 Enterprise, web app, data-heavy/visualization app |
My Role | Lead UX designer/researcher |
Context
This project is related to Markets Risk Platform project.
Migrating a legacy version of the application to a new application with complete UX/Product overhaul
Legacy version entailed 16 individual pages + 9 sub-pages
Old information architecture was convoluted and provided unnecessary redirection to different pages to users for tasks that overlap one another, and UX writing for the menu items were also very technical and outdated thus adding more to the confusion
Goal is to merge two applications due to the overlap of the user groups and to deliver a consolidated and seamless platform for them
Highlights
Conducted card sorting workshops and interviews with different user groups
New menu is now with four main categories of pages with fly-out menu so users can expect what they will see before entering the page
Launching in September 2025, feedback unavailable at this date
Details
Using wireframes instead due to confidentiality reasons
Legacy version
Previous menu of the application had items ordered in the chronological order of when the pages were developed, and not to do with the actual usage and interest of the users. This resulted in users taking longer to navigate to their destination as they're given too many options with technical-jargons (e.g. including words like "workflow" and multiple acronyms).
For some of the menu items, once clicked users were given sub-pages, which then they had to make another decision and click again to get to their destination. This structure is inefficient as it gives users unexpected options after they have already made a choice from the first layer of the menu.
New version
After the research, I consolidated the menu items into four different categories. First tab is a single-page, a merge of five different items from the legacy menu item because they were all part of same user journey where user disposes alerts/tasks day to day and search for those items.
The remaining menu items are fly-out menus for transparency of where user can navigate to. Each menu item is categorized into relevant buckets. These buckets are named so that they are task oriented instead of an abstract description of what the page entailed (which is what the legacy version had), for example "Reports & Dashboards" and "Hierarchy & Permission". The new menu is also dynamic to the user's permission so that they are only seeing items that are relevant to them. App 2 mentioned above is also merged into this new menu thus delivering a more consolidated experience to our users instead of having them switch between two different apps back and forth.