Designing a Customer Intelligence Platform That Helps Teams Turn Customer Data into Better Decisions.
Role
Senior Product Designer (Lead)
Team
Product Manager, Engineering, Marketing, Compliance, Customer Success, Business Stakeholders
Duration
4 weeks
CustomerHub is a customer intelligence platform designed to give marketing, customer success, and account management teams a complete understanding of their customers in one place. Rather than functioning as another sales-focused CRM, the platform helps teams understand customer health, engagement, communication history, and growth opportunities so they can make faster, more informed decisions.
As the Senior Product Designer, I led the end-to-end product design strategy, working across product discovery, UX research, information architecture, interface design, prototyping, and engineering collaboration. My role extended beyond designing dashboards—I partnered with stakeholders to define product direction, simplify complex customer data, and create scalable design foundations that could support future product growth.
One of the biggest challenges was balancing depth with clarity.
Customer-facing teams rely on enormous amounts of information to make daily decisions. Customer profiles, communication history, account health, engagement metrics, support interactions, marketing activities, and revenue insights all compete for attention.
The challenge wasn’t collecting more customer data.
It was helping teams understand what mattered most and act on it quickly.
To achieve this, we designed CustomerHub around three core principles:
The result was a modern customer intelligence platform that transformed fragmented customer records into a single, actionable workspace where every interaction helped teams understand customers better and make more confident decisions.
Senior Product Designer
Product Strategy • UX Research • Information Architecture • Interaction Design • UI Design • Dashboard Design • Design System • Prototyping • Cross-functional Collaboration • Design Leadership
Timeline
6 Weeks
Tools
Figma • FigJam • Adobe Illustrator • Prototyping
Traditional CRM systems are primarily designed to help sales teams manage opportunities and pipelines.
CustomerHub approached the problem differently.
Once a customer signs a contract, success depends on how well an organisation understands, supports, and retains that customer over time.
Unfortunately, customer information is often fragmented across multiple systems, making it difficult for teams to build a complete picture of customer health or identify opportunities before issues become problems.
Our challenge was to design a platform that consolidated customer intelligence into a single experience while making complex information easy to interpret, navigate, and act upon.
The dashboard was designed as the team’s starting point for understanding customer health and identifying where attention was needed.
Rather than presenting every available metric, I prioritised the information that could influence an immediate decision: customer health, engagement, recent activity, accounts requiring attention, and key actions.
The challenge was balancing information density with cognitive load. The interface needed to feel comprehensive for experienced users without overwhelming someone seeing the platform for the first time.
Design decision: Prioritise signals and actions over raw data.
Outcome: Users could understand the state of their customer base at a glance and move directly from insight to action.
One of the biggest challenges we uncovered during discovery wasn’t a lack of customer data, it was an overload of customer data.
Marketing teams, Customer Success Managers, and Account Managers already had access to dozens of tools that tracked customer interactions, campaign performance, support requests, product usage, and account activity.
The problem wasn’t collecting more information.
The problem was turning that information into meaningful action.
CustomerHub was designed around a simple but important question:
“What does someone need to know about this customer right now to make the right decision?”
That question became the foundation for every product decision that followed.
Rather than creating another reporting dashboard, we focused on building a decision-support platform that helped customer-facing teams quickly understand customer health, identify opportunities, and take immediate action.
Traditional dashboards often prioritise displaying as much information as possible.
CustomerHub took a different approach.
Every section of the interface was designed to answer a specific business question.
Instead of asking users to interpret large datasets themselves, the interface surfaced the insights most relevant to the task at hand.
For example:
Instead of simply displaying contact information, the profile became a comprehensive view of the customer relationship, bringing together account details, engagement history, communication records, product usage, and recent activity into a single workspace.
This eliminated the need to switch between multiple systems before engaging with a customer.
Rather than requiring Customer Success Managers to manually assess account health, visual indicators highlighted engagement trends, satisfaction signals, and potential risks.
The goal wasn’t merely to report customer behaviour.
It was to help teams recognise which accounts required immediate attention.
Marketing teams often struggle to identify the right audience quickly.
Instead of navigating complex filters across multiple pages, CustomerHub made segmentation an integrated part of the workflow.
Users could quickly organise customers based on behaviours, demographics, engagement levels, lifecycle stage, or custom attributes, enabling faster campaign creation and more targeted communication.
Every customer conversation contributes valuable context.
Instead of separating emails, support interactions, notes, and previous engagements across different tools, CustomerHub brought them together into a chronological timeline.
This allowed anyone interacting with a customer to understand the relationship immediately without searching through disconnected systems.
One of the most important design principles throughout the platform was ensuring that every insight naturally led to an action.
Rather than asking users to interpret information and then navigate elsewhere to respond, CustomerHub connected insights directly to workflows.
Teams could launch campaigns, contact customers, assign follow-up tasks, or update account information directly from the customer record, significantly reducing context switching.
The platform wasn’t designed simply to answer questions.
It was designed to help users act while the information was still relevant.
Another challenge was recognising that different departments looked at the same customer from different perspectives.
Marketing teams wanted to understand campaign engagement.
Customer Success focused on retention and adoption.
Account Managers cared about relationship history and growth opportunities.
Support teams needed immediate visibility into recent issues.
Rather than creating completely separate products for each department, CustomerHub provided a shared customer foundation while adapting the information hierarchy to different workflows.
This created a single source of truth without forcing every team to work in the same way.
One of the biggest design challenges wasn’t adding features.
It was deciding what to hide.
Customer dashboards naturally accumulate more data over time, making it easy for interfaces to become overwhelming.
Throughout the design process, I continually evaluated every piece of information against one question:
Does this help someone make a better decision?
If the answer was no, it was deprioritised, simplified, or removed.
This principle influenced everything from page layouts and navigation to typography, spacing, colour, and visual hierarchy.
The result was an interface that felt comprehensive without feeling cluttered, enabling users to process large amounts of information without becoming overwhelmed.
Throughout the project, one principle guided nearly every design decision:
The best dashboard is not the one that displays the most information.
It’s the one that helps people make better decisions with the least amount of effort.
That philosophy became the defining characteristic of CustomerHub and influenced every feature that followed.
Designing CustomerHub wasn’t simply an interface challenge.
It was an information architecture challenge.
The platform needed to bring together large volumes of customer data from multiple touchpoints while ensuring users could quickly identify what mattered most without becoming overwhelmed.
Rather than starting with layouts or visual design, I focused on defining the structure of the product itself.
The goal was to create a platform where information naturally supported decision-making instead of competing for attention.
One of the earliest discoveries during product definition was that every team viewed the same customer through a different lens.
Marketing wanted to understand campaign performance and audience behaviour.
Customer Success focused on adoption, engagement, and retention.
Account Managers looked for relationship history and expansion opportunities.
Leadership wanted high-level customer health and business performance.
Although everyone interacted with the same customer, they asked very different questions.
Instead of building separate experiences for each department, I designed a shared information architecture that established a single customer record while allowing each team to surface the information most relevant to their workflow.
This reduced duplication, improved collaboration, and ensured everyone worked from the same source of truth.
One of the biggest risks in dashboard design is treating every piece of information as equally important.
When everything is prioritised, nothing is prioritised.
To avoid this, I organised the experience into layers of importance.
The first screen answered the questions users needed within seconds.
This gave users enough context to make an informed decision without searching through multiple pages.
Once users understood the current situation, they could explore deeper information including:
This additional context remained available without overwhelming the primary experience.
More advanced information, including reports, segmentation tools, behavioural trends, and historical activity, was intentionally placed deeper within the product.
This approach allowed power users to access detailed analysis while keeping everyday workflows fast and intuitive.
One of the core principles behind CustomerHub was progressive disclosure.
Rather than exposing every available data point immediately, the interface revealed additional information only when users needed it.
This reduced cognitive load while maintaining the depth expected from an enterprise platform.
Users could move naturally from:
Customer Overview
↓
Customer Details
↓
Historical Context
↓
Recommended Action
without ever feeling overwhelmed by unnecessary information.
Progressive disclosure allowed the platform to remain approachable for new users while still supporting experienced teams managing large customer portfolios.
Traditional enterprise software often organises navigation around product modules.
CustomerHub was organised around user workflows instead.
Instead of asking users where information was stored, the navigation reflected how teams actually worked.
Common workflows such as:
could all be completed with minimal context switching.
This reduced navigation complexity and helped users remain focused on the task they were trying to accomplish.
Large enterprise dashboards succeed or fail based on how effectively they communicate information.
Visual hierarchy became one of the project’s most important design tools.
Rather than relying on colour alone, hierarchy was established through:
Critical information naturally attracted attention while secondary information remained accessible without competing for focus.
The result was an interface that felt information-rich without feeling visually heavy.
CustomerHub was never intended to remain a static product.
As customer data, integrations, and product capabilities expanded, the interface needed to evolve without becoming increasingly complex.
To support this, I designed the information architecture as a scalable framework rather than a fixed collection of screens.
Navigation patterns, page layouts, component behaviours, and content structures were all created with future expansion in mind.
This systems-first approach allowed new capabilities to be introduced while preserving consistency and reducing long-term design debt.
Every information architecture decision ultimately supported one objective:
Reduce the time between understanding a customer and taking meaningful action.
That principle influenced:
Rather than designing around pages, I designed around decisions.
That shift—from organising information to enabling action—became one of the defining characteristics of CustomerHub and one of the project’s most valuable strategic outcomes.
Instead of forcing users to interpret a customer signal and then navigate somewhere else to respond, relevant actions were placed directly alongside the information that triggered them.
This reduced context switching and preserved the user’s workflow.
Design decision: Put the next relevant action as close as possible to the insight.
Outcome: CustomerHub became more than a place to understand customers—it became a workspace for acting on that understanding.
With the product strategy and information architecture established, the focus shifted to designing an experience that helped customer-facing teams understand customers, identify opportunities, and take action without unnecessary friction.
Every interface was designed around a simple principle:
Information should lead naturally to action.
Rather than treating dashboards as collections of charts and widgets, each part of CustomerHub was designed to answer a business question and support a decision.
The dashboard became the operational starting point for every user.
Rather than overwhelming teams with dozens of metrics, the experience surfaced the information most likely to influence immediate decisions.
At a glance, users could understand:
Quick actions were positioned alongside key insights so users could immediately respond without navigating through multiple screens.
Instead of acting as a reporting interface, the dashboard became a decision-making workspace.
One of the biggest pain points uncovered during discovery was context switching.
Customer Success Managers often moved between CRM systems, support tools, marketing platforms, spreadsheets, and communication history before they could understand a single customer.
CustomerHub solved this by creating a unified customer profile.
Every profile brought together:
Instead of searching across disconnected systems, teams could understand the entire customer relationship from one screen.
This significantly reduced the effort required before every customer interaction.
Segmentation is one of the most powerful capabilities within customer platforms, but it’s often treated as an advanced reporting feature.
We approached it differently.
Segmentation became part of everyday workflows.
Users could quickly organise customers using combinations of:
Rather than requiring technical knowledge, segmentation was designed to feel visual, flexible, and approachable.
This enabled both marketing and customer success teams to identify meaningful customer groups without relying on complex query builders.
Understanding a customer requires understanding their history.
Instead of separating interactions across multiple systems, CustomerHub presented customer activity as a unified chronological timeline.
Users could quickly review:
This timeline reduced the time required to prepare for customer conversations while improving continuity across departments.
Every interaction added context to the overall customer story.
One principle guided every page within CustomerHub:
Every insight should create an opportunity to act.
Rather than displaying information passively, the interface encouraged immediate action.
From almost every screen, users could:
Reducing the distance between insight and action helped teams respond faster while maintaining workflow momentum.
Enterprise software often struggles to balance depth with clarity.
Throughout CustomerHub, visual hierarchy became a critical design tool.
Rather than relying on dense tables and reports, data was presented using:
The objective wasn’t simply to make dashboards attractive.
It was to help users recognise important patterns without analysing raw data manually.
As CustomerHub expanded, maintaining consistency became increasingly important.
Instead of designing each page independently, I established reusable interaction patterns and shared components that supported both designers and engineers.
The system included:
This reduced duplication while making future product expansion faster and more predictable.
The design system became more than a UI library.
It became the product’s operational foundation.
Although CustomerHub appears visually sophisticated, the project’s greatest challenge wasn’t aesthetics.
It was simplifying the complexity of customer relationships.
Every design decision balanced competing priorities.
Business teams wanted more information.
Users wanted less complexity.
Engineering needed scalable solutions.
Product teams wanted flexibility.
My role was bringing those perspectives together to create an experience that felt simple without sacrificing capability.
That balance became one of the defining strengths of the platform.
As CustomerHub expanded, designing each feature independently would have created inconsistency and increasing design debt.
I established a shared design system that brought the product’s visual language, interaction patterns, and reusable components into a single foundation.
The system covered typography, colour, spacing, grids, navigation, forms, tables, cards, status indicators, and common interaction patterns.
The goal wasn’t simply visual consistency. It was to create a shared language between Design and Engineering that made new product work easier to design, build, and maintain.
Design principle: Build reusable patterns around recurring product behaviours, not individual screens.
As CustomerHub expanded, maintaining consistency became increasingly important.
Instead of designing each page independently, I established reusable interaction patterns and shared components that supported both designers and engineers.
The system included:
This reduced duplication while making future product expansion faster and more predictable.
The design system became more than a UI library.
It became the product’s operational foundation.
Although CustomerHub appears visually sophisticated, the project’s greatest challenge wasn’t aesthetics.
It was simplifying the complexity of customer relationships.
Every design decision balanced competing priorities.
Business teams wanted more information.
Users wanted less complexity.
Engineering needed scalable solutions.
Product teams wanted flexibility.
My role was bringing those perspectives together to create an experience that felt simple without sacrificing capability.
That balance became one of the defining strengths of the platform.
CustomerHub needed to support different customer workflows and large amounts of data, but introducing one-off patterns for every use case would quickly fragment the experience.
I therefore designed components with clear behavioural rules and flexible variants, allowing the same patterns to adapt to different contexts without losing their underlying structure.
This approach made common interactions predictable for users while giving designers and engineers enough flexibility to support new features.
System principle: Standardise the behaviour, not every possible visual outcome.
The design system became a shared foundation for how CustomerHub was designed and built. It helped the team move from designing individual screens to designing reusable product patterns, making the experience more consistent for customers and the product easier for the team to evolve.
The success of CustomerHub wasn’t measured by the quality of its interface alone.
It was measured by how effectively the product helped teams understand customers, collaborate across departments, and make faster, more informed decisions.
Throughout the project, we evaluated success through improvements in usability, operational efficiency, collaboration, and the platform’s ability to scale as customer data and business needs evolved.
The objective wasn’t simply to build another dashboard.
It was to create a product that helped organisations build stronger customer relationships through better decision-making.
Customer-facing teams often lose valuable time switching between disconnected systems before taking action.
By consolidating customer intelligence into a unified workspace, CustomerHub reduced the effort required to gather context before engaging with a customer.
Instead of navigating multiple applications, teams could review customer health, communication history, engagement metrics, and recent activity from a single interface.
This streamlined daily workflows and allowed users to spend more time supporting customers rather than searching for information.
One of the platform’s primary goals was making customer information easier to understand.
Rather than overwhelming users with dashboards full of metrics, CustomerHub prioritised clarity through structured information hierarchy, progressive disclosure, and contextual insights.
By surfacing the most relevant information first, users could quickly identify:
This transformed the dashboard from a reporting tool into a decision-support platform.
CustomerHub was designed as a growing product rather than a fixed solution.
To support future expansion, I established reusable interaction patterns and a scalable design system that improved consistency across the platform while reducing duplication during future development.
As new modules and customer workflows were introduced, the product could evolve without requiring fundamental redesign.
This systems-first approach helped ensure that design remained an accelerator for product growth rather than a bottleneck.
Design decisions throughout the project were shaped through continuous collaboration with Product Managers, Engineers, Marketing teams, Customer Success leaders, and business stakeholders.
Rather than treating design as a downstream activity, I participated in discussions that influenced product priorities, feature definition, and implementation strategy.
Working closely with engineering throughout development helped identify technical constraints early, improve implementation quality, and ensure that the final product remained consistent with the original design intent.
This collaborative approach strengthened alignment across teams while reducing unnecessary iteration later in the development process.
As the Senior Product Designer, my contribution extended beyond interface design.
I helped facilitate conversations between business and technical teams, translated customer needs into actionable product decisions, and established design principles that guided future feature development.
I also mentored junior designers by encouraging systems thinking, structured design critiques, and a stronger focus on business outcomes rather than purely visual execution.
Creating shared understanding across disciplines became just as important as producing high-quality design work.
If I were evolving CustomerHub today, I would extend it beyond customer intelligence into an AI-native customer success platform.
Several opportunities stand out.
Rather than requiring teams to manually interpret dashboards, an AI assistant could generate concise customer summaries before every meeting.
Examples:
“This customer’s engagement has dropped by 28% over the last month. They have two unresolved support tickets and haven’t adopted the new reporting feature. Consider scheduling a success review.”
Instead of analysing multiple screens, teams begin every conversation with immediate context.
Instead of reporting historical activity, CustomerHub could proactively identify customers at risk of churn by analysing behavioural trends, product adoption, support activity, and communication history.
Rather than waiting for issues to appear in reports, Customer Success Managers could intervene before relationships deteriorate.
The platform could recommend actions based on customer behaviour.
Examples include:
Instead of simply presenting data, CustomerHub would actively help teams decide what to do next.
Rather than navigating reports manually, users could ask natural-language questions such as:
“Show me enterprise customers whose engagement declined this month.”
“Which accounts have the highest expansion potential?”
“Summarise support activity for our top twenty customers.”
This would dramatically reduce the time required to find insights while making advanced analytics accessible to non-technical users.
CustomerHub reinforced an important lesson that continues to shape how I approach product design.
Great enterprise software isn’t defined by the amount of information it displays.
It’s defined by how effectively it helps people make decisions.
The project strengthened my ability to simplify complex systems, collaborate across disciplines, design scalable product foundations, and balance user needs with business strategy.
More importantly, it reinforced a mindset that now guides every product I work on:
The role of design isn’t simply to make software easier to use.
It’s to help people make better decisions with greater confidence.