Role
Senior UX Designer
Domain
Enterprise Systems · Financial Services · Platform UX
Skills
User Research · Information Architecture · Product Strategy · Dashboard UX · Design Systems · Cross-Functional Collaboration
Overview
From a basic application launcher to a more useful home for everyday work
J.P. Morgan's Party Central platform supported a growing collection of tools for searching, creating, resolving, and maintaining enterprise party records. But its landing page hadn't evolved alongside those capabilities.
What began as a convenient application launcher had become an increasingly crowded collection of tiles. Users relied on bookmarks, memorized locations, and familiarity with the platform to find what they needed.
I worked on reimagining the landing experience as a personalized, task-focused workspace that could bring search, pending work, recent activity, and frequently used tools into one place.
The challenge was to establish a more ambitious product vision while defining a realistic first step. Working with Product, Data, and Engineering, I explored capabilities that could make the landing page genuinely useful, while introducing J.P. Morgan's SALT design system as a foundation for incremental modernization.
The Problem
A growing platform without a clear starting point
Party Central's applications had evolved independently, reflecting the priorities and ownership of different teams rather than a unified user experience.
As the platform expanded, several problems became apparent:
Related applications were scattered across a flat collection of tiles.
Users depended on bookmarks and memorized navigation.
Pending requests, approvals, and unfinished work weren't readily visible.
Makers, checkers, and other operational users had different daily priorities.
The legacy Tuxedo interface offered limited flexibility for introducing new functionality.
The larger opportunity was being missed. Instead of helping users manage their daily work, the landing page primarily directed them elsewhere.
The challenge wasn't simply to reorganize the tiles. It was to rethink what the landing page could contribute to the platform while working within existing technical and delivery constraints.
My Role
As Senior UX Designer, I drove user research, information architecture, requirements synthesis, and design exploration for the proposed landing experience.
I interviewed operational users, reviewed existing application entry points, and collaborated with Product, Data, Engineering, and partner teams to understand workflows, technical dependencies, and opportunities for improvement.
My contributions included:
Translating a broad collection of feature requests into a coherent product direction.
Developing a revised information architecture around recognizable operational tasks.
Exploring personalized, task-focused capabilities informed by user needs and technical feasibility.
Balancing immediate MVP requirements with longer-term opportunities.
Advocating for the landing page to introduce reusable SALT components and interaction patterns.
The work required connecting user needs, business priorities, and technical realities rather than treating the landing page as an isolated interface redesign.
Research & Insights
Understanding why people came to Party Central
I developed a structured interview guide and conducted sessions with makers, checkers, and other operational users to understand how they navigated the platform, found information, resumed work, and handled problems.
Rather than beginning with proposed solutions, the interviews focused on users' everyday activities and the obstacles they encountered.
The research highlighted several needs:
Faster access to frequently used applications and records.
Less dependence on memorized navigation and personal bookmarks.
Better visibility into recent activity and work already in progress.
Easier access to requests, approvals, and relevant status information.
More useful context when returning to the platform.
These findings shifted the discussion away from adding more tiles or dashboard widgets.
The landing page needed to answer three practical questions:
Where am I? What needs my attention? What should I do next?
Grounding the Experience in Daily Work
The interview guide and sample notes illustrate the preparation and detail behind the research, from open-ended questions about daily work to specific observations about navigation habits, workarounds, and information needs.
Design
1. Turning requirements into a shared product vision
The initiative began with an extensive collection of proposed improvements, including search, portfolios, task summaries, request tracking, favorites, system announcements, and product metrics.
Rather than treating these as independent feature requests, I organized them into a coherent view of what the landing page could offer and why each capability mattered.
The resulting summary was particularly well received by Product and Technology stakeholders because it made a complicated initiative easier to understand, discuss, and prioritize.
From Feature Requests to Shared Product Direction
The visual summary connected proposed capabilities to their intended user and business benefits, giving stakeholders a common reference for discussing the scope and direction of the redesign.
2. Reorganizing applications around user workflows
The existing navigation reflected how Party Central's applications had been developed and maintained, rather than how users understood their work.
I developed a revised information architecture that grouped related applications into recognizable functional areas, including Party Management, Preferences, Bulk Upload, ID Resolution, Administration, and Reporting.
The exercise also accounted for proposed additions and applications being considered for decommissioning.
Instead of continually expanding the homepage as more tools were introduced, the new structure offered a foundation for persistent navigation that could grow with the platform.
From Disconnected Tiles to Coherent Navigation
The proposed structure organized independently owned applications into functional categories, distinguishing existing tools, planned additions, and candidates for retirement. It provided the foundation for the navigation explored in later concepts.
3. Exploring the larger opportunity
The existing landing page was significantly underused relative to its potential.
Through discussions with Product, Data, and Engineering, I explored how a more capable workspace could surface information and functionality users would otherwise need to find across separate applications.
The longer-term vision considered:
Personalized access to frequently used tools.
Outstanding tasks, approvals, and requests.
Request status and activity tracking.
Recent searches and work in progress.
Relevant operational updates and product communications.
Contextual information tailored to different user roles.
These weren't simply aspirational dashboard ideas. Discussions with the teams responsible for the underlying data and services helped identify realistic opportunities, dependencies, and delivery constraints.
Not every capability could be included in the initial release. But understanding the larger opportunity was essential to making good decisions about what to build first.
From Initial MVP to a More Capable Workspace
The explorations illustrate the contrast between an achievable initial experience and a richer workspace built around personalized tools, request status, and contextual information. They helped communicate the longer-term opportunity while informing what the first phase needed to support.
4. Using SALT to establish an extensible foundation
Party Central was still using J.P. Morgan's legacy Tuxedo design system while the broader organization was transitioning toward SALT.
I advocated for using the landing-page initiative as Party Central's first SALT-based experience.
SALT offered an opportunity to introduce shared navigation, reusable components, and consistent interaction patterns that could support both immediate usability improvements and future functionality.
The proposed MVP was intentionally more modest than the broader vision. It prioritized an achievable first phase without requiring every underlying application or data service to be redesigned at once.
Rather than treating the limited initial scope as the finished experience, I approached it as a foundation for gradual expansion.
5. From application catalog to task-focused workspace
Bringing the research, revised information architecture, and design-system exploration together, I developed a proposed landing experience organized around users' most common needs.
The concept introduced persistent navigation, prominent search, favorites, and modular areas for task and request information.
The key shift was from presenting a collection of available applications to helping users recognize, prioritize, and resume their work.
From Application Catalog to User Workspace
The existing landing page served primarily as an application launcher. The proposed MVP introduced clearer navigation and a modular layout designed to accommodate search, favorites, request tracking, and additional task-oriented capabilities as the platform evolved.
Outcomes
The project established a research-informed direction for evolving Party Central's landing page from an application catalog into a more useful enterprise workspace.
Key accomplishments included:
Conducted structured user interviews to identify navigation friction, workflow priorities, and opportunities for contextual information.
Consolidated a broad collection of feature requests into a visual product summary that was positively received by Product and Technology stakeholders.
Developed a revised information architecture organized around operational functions rather than application ownership.
Explored a richer, personalized workspace informed by discussions with Product, Data, and Engineering.
Established an incremental design direction that balanced an achievable MVP with longer-term functionality.
Proposed SALT-based navigation and reusable component patterns to support future platform modernization.
My involvement concluded during the concept and planning phase, so these outcomes reflect research, product direction, design exploration, and stakeholder alignment rather than post-launch performance.
The most important contribution was establishing a path forward: one that addressed immediate usability problems without limiting what Party Central's landing experience could eventually become.