Technology Product Catalog
Internal infrastructure inventory database
All assets have been remade and genericized due to NDA requirements
From
To
Project Overview:
Internal teams for JP Morgan Chase did not have a singular location to research what department owned an internal product, who the product manger was, and what infrastructure assets are associated with that product. This project was to consolidate multiple databases of internal infrastructure assets into a single, easily searchable "Technology Product Catalog"
Project Aspects:
Led a small UX team consisting of interaction designer and visual designer
Close collaboration with business units and Dev team
Completed in Figma
Agile work environment
Old Product Listing Landing Page
Old “Product Wheel”
Requirements:
Create robust search platform for multiple product databases
Create "New Product" pages as well as allowing for editing of existing products
Must be implemented in an "Agile" environment
Define a developable "Minimum Viable Product"
Allow for iterative updates to design and functionality
The Ask:
Update the existing Technology Product Catalog from being organized by “company verticals” to a single database organized by “product line.”
Make the Technology Product Catalog the sole “system of record” for all internal products and platforms within the company (by consolidating 3 existing product databases into one seamless experience).
The User:
Product consumer (developer)
Product owners
Product line owners
Executive directors
Issues:
At time of start, product lines were ill-defined
Limited dev-line resources
Poor back end data structures
Different for all 3 different databases
Databases were created for different purposes and functionality
Lack of agreement of MVP
The multiple database issue truly compounded the MVP determination. Certain databases had less functionality than others which limited the global functionality of the catalog.
Research Effort:
Expert analysis
"Best practice" analysis
User group feedback
There was no research to speak of. The desire to update the catalog was driven by a shift in the internal company operating model. Some user feedback from customer satisfaction surveys was used for decisions, but no direct UX Research for this project was conducted. The user forum was used aa an "User Acceptability Testing."
Design Advocacy:
Simple and clean
Strong visual information hierarchy
Easy is not always best
Design Results:
Redesigned Catalog Landing
Redesigned Product Details
Product Life Cycle Details
The Results:
Working catalog organized by product line
Compliant with internal design system
Stronger visual hierarchy
Easily scannable data
Positive user responses
Continued iterative updates
