Party Central Landing Page & Platform Improvements

Enterprise Systems
Written By B K

Role
Senior UX Designer

Domain
Enterprise Systems · Platform UX · Information Architecture

Skills
Information Architecture · Workflow Design · Dashboard UX · Cross-Squad Collaboration · Design Systems · Incremental Improvement

Overview

As Party Central grew to support more workflows — search, bulk upload, ID resolution, maintenance tasks — the landing experience struggled to keep up. Users were entering the platform through different paths and with different intents, but the landing page didn’t clearly support orientation, prioritization, or next steps.

This initiative focused on incremental but meaningful platform improvements, anchored by a redesigned landing experience that helped Ops users quickly understand where they were, what needed attention, and how to move forward efficiently.

The Problem

The existing landing experience created friction for daily users:

  • No clear hierarchy of tasks or entry points

  • Important updates and actions were easy to miss

  • Navigation felt scattered as new features were added

  • Users often relied on bookmarks or tribal knowledge

  • The landing page didn’t reflect how Party Central was actually used day to day

As the platform matured, the landing page needed to evolve from a passive entry screen into an active orientation and decision-support surface.

My Role

I contributed UX design across several platform-level improvements, including the landing experience. My responsibilities included:

  • Auditing existing navigation and entry patterns

  • Identifying common user intents across squads

  • Collaborating with Product and Engineering on feasibility and sequencing

  • Designing IA updates that aligned with ongoing feature work

  • Applying design system standards to ensure consistency

  • Supporting iterative rollout rather than a disruptive overhaul

This work required balancing immediate usability gains with long-term platform direction.

Research & Insights

Through stakeholder conversations and usage analysis, several patterns emerged:

  • Most users came to Party Central with a specific task in mind, not to browse

  • Users needed reassurance they were in the right place before taking action

  • Frequently used actions were buried too deeply

  • Announcements and status information lacked visibility

  • As new features shipped, discoverability became a growing concern

The landing page needed to support orientation, prioritization, and momentum — without overwhelming users.

Design Approach

1. Clarifying Primary User Intents

The redesigned landing experience prioritized the most common intents:

  • Search for a party or record

  • Continue in-progress work

  • Address data quality or review tasks

  • Access bulk or maintenance workflows

This reduced cognitive load and helped users act quickly.

2. Improving Information Architecture

I worked to simplify and rationalize navigation by:

  • Grouping related workflows more intuitively

  • Reducing redundancy across entry points

  • Aligning labels with how Ops teams actually talk about their work

  • Ensuring new features fit cleanly into the existing structure

These changes made the platform feel more cohesive as it expanded.

3. Landing Page as an Orientation Surface

Rather than treating the landing page as static, the redesign emphasized:

  • Clear visual hierarchy

  • Actionable entry points

  • Contextual awareness (what’s new, what’s pending, what matters now)

  • A balance between flexibility and focus

The goal was to help users quickly answer:
“Where am I, and what should I do next?”

4. Incremental, Low-Risk Improvements

Given the scale and criticality of Party Central, changes were intentionally incremental:

  • No sudden workflow disruptions

  • Familiar patterns reinforced rather than replaced

  • Design system components reused wherever possible

  • Improvements designed to layer on over time

This approach built trust and reduced adoption risk.

Key Design Decisions

  • Focused on clarity and discoverability over visual novelty

  • Avoided overloading the landing page with metrics or dashboards

  • Prioritized common actions without hiding advanced workflows

  • Designed IA updates to support future growth

  • Ensured alignment with concurrent initiatives (Search, Bulk Upload, ID Resolution)

Solution

Updated Landing Experience

  • Clear primary actions

  • Improved visual hierarchy

  • Better alignment with user intent

  • Reduced reliance on bookmarks and workarounds

Platform-Level Improvements

  • More intuitive navigation structure

  • Cleaner entry points into major workflows

  • Better discoverability of new capabilities

  • Consistent application of design system standards

Together, these changes made Party Central feel more intentional, navigable, and coherent as a platform.

Impact & Results

  • Reduced friction for daily Ops users

  • Improved clarity around where to start work

  • Increased discoverability of key workflows

  • Supported smoother onboarding for new users

  • Provided a foundation for continued platform evolution

While incremental, these improvements had an outsized effect on usability and confidence.

What I Learned

  • Small IA improvements can have large usability impact

  • Landing pages should support intent, not decoration

  • Platform UX requires restraint as much as creativity

  • Incremental change is often the safest path in enterprise systems

  • Consistency builds trust over time

Artifacts (Optional)

  • IA audits and navigation maps

  • Landing page explorations

  • Before/after comparisons

  • Component reuse documentation

B K
Previous

Spencer Stuart – Quest Mobile (Always-On Executive Search)
Next

JPMC Bulk Upload (Maker–Checker Workflow Redesign)