Kien Pham

Role: Product Designer (DC5 Project, FPT Software)

Timeline: March 2025 - Present

Scope: End-to-end UX architecture, interaction design, and system UI across 150+ core screens.

Key Output: Designed an integrated Portal Hub merging Customer 360°, Health, and Studio modules into a single, role-based ecosystem.

1. The Executive Summary

The CExP (Customer Experience Platform) under the Digital Conglomerate 5.0 (DC5) initiative was conceived to solve a critical enterprise problem: fragmented customer data. Large-scale B2B clients were managing customer interactions, support tickets, and marketing campaigns across disconnected legacy systems.

As the Product Designer, my objective was to unify these isolated touchpoints into a cohesive Customer Data Platform (CDP). By rethinking the fundamental information architecture and introducing a centralized Portal Hub, the design successfully reduced cognitive load for administrators while optimizing complex data workflows.

Headline Business Impact:

40% Reduction in Setup Time: Streamlined complex segment and campaign creation flows, accelerating enterprise admin velocity by up to 40%.
Unified 3 Ecosystems: Successfully merged disparate data streams (CExP Health, Customer 360, and Studio) into a seamless, role-based dashboard.
Scalable Architecture: Delivered a comprehensive component library powering over 150+ screens, establishing the foundational design system for all future DC5 enterprise products.

2. The Problem: Operational Friction in Legacy Systems

Enterprise users-ranging from Marketing Managers to Support Agents-faced severe workflow bottlenecks:

The "Swivel Chair" Dilemma: Users had to constantly switch contexts between different tools to view customer health, analyze 360° profiles, and launch campaigns.
High Cognitive Overload: Data was presented in dense, unstructured tables without clear visual hierarchies, making it difficult to extract actionable insights.
Complex Rule Creation: Setting up targeted customer segments required deep technical knowledge and manual logic inputs, leading to frequent errors and slow campaign execution.

The Core Challenge: How do we design an interface dense enough to satisfy power users (data analysts) while remaining intuitive enough for operational staff (marketing and support) to execute rapid campaigns?

3. Strategic Discovery & Research Insights

Instead of immediately jumping into visual mockups, I initiated a deep-dive analysis of existing administrator workflows. The discovery phase highlighted a critical discrepancy between how the system was structured and how users actually worked.

Key Research Insights

4. System Architecture & The "Portal Hub" Solution

The defining strategic decision of the CExP project was moving away from a traditional dashboard toward a Portal Hub Architecture. This served as the master routing system for the entire DC5 ecosystem.

1. The Centralized Portal Hub

I designed a unified gateway that intelligently managed user navigation:

Authentication Routing: Public guests were served landing page capabilities, while authenticated enterprise users were seamlessly transitioned into their personalized workspaces.
Role-Based Workspaces: Depending on the user's organizational tier, the Hub dynamically surfaced relevant modules (Customer 360° for Sales, Health for Support, Studio for Marketing).
Context Preservation: Users could navigate laterally between sub-modules without losing their session context or applied global filters.

2. Streamlining Complex Interactions: The Segment Builder

The most technically complex interaction was the Customer Segmentation engine. To solve the legacy issue of slow campaign setup, I introduced a modular logic interface:

[ If Customer Profile Contains: "High LTV" ] AND [ Engagement Score is: "> 80" ] THEN [ Assign Tag: "VIP Cohort" ] -> [ Launch Campaign ]

This visual "building block" approach translated complex backend database queries into a frictionless, drag-and-drop experience, directly contributing to the 40% reduction in campaign setup time.

3. High-Density B2B Component System

To support the massive scale of the project (150+ screens), I established a rigid, scalable design system focused purely on utility and data legibility:

Tabular Data Mastery: Implemented sticky headers, inline editing, and resizable columns to handle heavy enterprise data sets without breaking the UI.
Status Hierarchy: Designed a consistent taxonomy of color-coded tags (e.g., Active, Churned, At-Risk) to ensure instant visual recognition across all modules.
Progressive Disclosure: Kept primary tables clean by moving secondary metadata into slide-out panels (drawers), reducing initial cognitive load.

5. Measurable Impact & Key Outcomes

6. Strategic Takeaways for Enterprise Design

Structure dictates behavior: In complex B2B systems, solving navigation and permission architecture early is infinitely more valuable than perfecting visual aesthetics.
Consistency creates velocity: A strict component system not only speeds up engineering but drastically reduces the learning curve for enterprise users.
Empowerment through clarity: By translating complex database logic into visual, human-readable blocks, we empowered non-technical staff to execute high-level data tasks independently.