Prioritize Decisions, Not Data
Surface the signals with the greatest customer and business impact instead of giving every available metric equal visual weight.
CASE STUDY
Designing a Unified Customer Success Workspace
Turning fragmented customer signals into a prioritized workflow for identifying risk, understanding relationships, and taking action.
I led the end-to-end product design of Staircase AI’s Customer Success workspace, working closely with product managers, founders, engineers, data and AI teams, and Customer Success. Together, we transformed fragmented customer data into a connected experience that helped teams identify risk, understand the relationships behind each account, and decide where to act.
The Challenge
Customer Success Managers were responsible for monitoring dozens of enterprise accounts at once. They needed to recognize churn risk, changes in stakeholder relationships, and potential growth opportunities early enough to respond.
The signals already existed across emails, meetings, support conversations, CRM records, product usage, and account history. But they were distributed across tools and screens, forcing CSMs to manually reconstruct the story behind each account before deciding what required attention.
As portfolios grew, this fragmented process became difficult to scale. Teams spent valuable time gathering context, relied heavily on intuition to prioritize accounts, and sometimes discovered important risks or opportunities too late.
The problem was not a lack of customer data. It was the absence of a clear path from signal to context to action.
Key challenges
- Customer signals were fragmented across systems and communication channels.
- Teams lacked a reliable way to prioritize risk and growth opportunities.
- Understanding an account required time-consuming manual investigation.
- Relationship changes were difficult to see within traditional account data.
Research & Understanding
To understand where the existing experience was breaking down, I worked closely with Customer Success, product, and the founders. We combined direct conversations with Customer Success teams, recurring feedback from customers, product usage patterns, and a review of the workflows used to investigate account health.
The issue was not that teams lacked information. They lacked a reliable way to interpret it. Tables and account records exposed individual metrics, but did not explain which accounts required attention, why a signal mattered, or what the CSM should investigate next.
What we learned
- CSMs needed to understand priorities before reviewing account-level detail.
- Metrics without relationship and communication context were difficult to trust.
- Important signals were buried inside dense tables and fragmented workflows.
- Teams needed both a portfolio-level summary and a direct path into the evidence behind each signal.
The interface needed to move beyond reporting what happened and help teams decide what to do next.
Design direction
The research shaped three connected design goals:
- Surface customer health and business priority at a glance.
- Connect every signal to the relationships and activity behind it.
- Support progressive investigation, from portfolio overview to detailed communication history.
Design Principles
The research gave us a clear standard for every design decision: the workspace should reveal what requires attention, explain why it matters, and provide a direct path to the supporting context.
Connect Every Signal to Context
Allow teams to move directly from an alert or opportunity to the relationships, activity, and communication that explain it.
Reveal Detail Progressively
Reduce cognitive load by showing a clear portfolio summary first, while keeping deeper evidence available when investigation is needed.
From Insights to Solution
These principles shaped a connected decision flow rather than a collection of isolated dashboards. A Customer Success Manager could begin with a prioritized portfolio signal, investigate the relationship and activity behind it, and reach the relevant context before deciding how to respond.
Signals
Prioritize
Investigate
Take Action
The flow organized the solution into three connected layers:
- Customer Health Overview to identify where attention was needed.
- Stakeholder Relationship Map to understand the people and relationship dynamics behind the account.
- Activity and Communication Intelligence to investigate what changed, when it changed, and why.
Each layer answered a different question while preserving one continuous path from overview to evidence and action.
SURFACE CUSTOMER HEALTH SIGNALS
Customer Health Overview
The Customer Health Overview gave CSMs a prioritized starting point for their day. Instead of scanning every account or reacting to the highest volume of activity, they could immediately see which customers required attention and the business context behind that priority.
Priority was determined by customer and business impact, not by activity volume alone.
The overview combined health, engagement, ARR, response time, and emerging trends into a single portfolio-level view. From each signal, CSMs could move directly into the relevant accounts and investigate the evidence behind it.
What the dashboard surfaced
- At-Risk Customers: accounts showing risk signals, including low engagement combined with meaningful business impact.
- Unanswered Items: customer communications that had remained without a response.
- Growth Opportunities: accounts showing positive changes in engagement or relationship activity.
- Business Context: ARR, engagement, and response indicators needed for prioritization.
- Direct Investigation: a clear path from each signal to the relevant customer accounts.
UNDERSTAND THE PEOPLE BEHIND THE ACCOUNT
Stakeholder Relationship Map
Portfolio-level metrics could show that an account had changed, but they could not explain what was happening inside the customer relationship. A healthy activity score could still conceal a disengaged Decision Maker, a frustrated Champion, or a critical stakeholder who had stopped responding.
The Stakeholder Relationship Map organized the customer’s key contacts by role and made the quality of each relationship visible. This helped CSMs understand not only how much communication was taking place, but whether the right people were engaged and how those interactions were changing.
We used a simple and consistent visual language so relationship patterns could be understood at a glance:
- Green: a positive interaction with an engaged or satisfied contact.
- Yellow: a neutral interaction that did not indicate a clear positive or negative shift.
- Red: a negative interaction showing frustration, disengagement, or dissatisfaction.
Account health depended not only on activity, but on the strength and direction of the relationships behind it.
INVESTIGATE THE CUSTOMER JOURNEY
Activity & Communication Intelligence
Activity Timeline
After identifying a risk or relationship change, CSMs needed to understand how the account had reached that point. The Activity Timeline brought engagement trends, sentiment changes, lifecycle milestones, and communication activity into one chronological view.
Rather than reconstructing the account across separate tools, teams could see when activity changed, which events occurred around that change, and where deeper investigation was required.
The timeline revealed
- Changes in customer activity and engagement over time.
- Positive and negative shifts in sentiment.
- Important milestones in the customer lifecycle.
- The sequence of events leading to the current account state.
Communication Summary
The timeline revealed where a change occurred. The Communication Summary provided the conversations needed to understand why.
Emails, meetings, and customer interactions were organized chronologically with the people and surrounding account context attached to each event.
CSMs could review the relevant communication without moving between disconnected tools, helping them understand what was discussed, who was involved, and how each interaction affected the broader relationship.
The goal was not to expose more history. It was to make the evidence behind every customer signal easier to understand.
TURNING INSIGHT INTO ACTION
Impact
The workspace was launched to customers and continued to evolve through direct feedback and observed product usage. Customers reported that the redesigned experience made complex account information clearer, reduced the effort required to understand what needed attention, and helped them navigate the product more efficiently.
We also observed a consistent increase in visits to the redesigned views and greater use of the features introduced through this work. Without relying on a single success metric, these behavioral patterns and recurring customer feedback indicated that the new structure was becoming part of the teams’ workflow.
Clearer Prioritization
Customers could understand which accounts and signals required attention without beginning with a manual review of every available metric.
Faster Access to Context
The connected views reduced the effort required to move from a high-level signal to the relationships, activity, and communication behind it.
Growing Product Engagement
Usage patterns showed increasing visits to the redesigned pages and stronger engagement with the new capabilities over time.
Continuous Improvement
Customer feedback did not end at launch. It informed additional product decisions and helped us refine features around real Customer Success workflows.
The strongest signal of success was that customers increasingly used the product to understand, prioritize, and investigate their accounts.
FROM FRAGMENTED WORK TO A CONNECTED SYSTEM
Before / After
The redesign shifted the workflow from manually assembling customer context to following a connected path from priority to evidence and action.
Before: Fragmented Investigation
- Signals were distributed across tools, tables, and communication channels.
- CSMs manually reconstructed the context behind each account.
- Prioritization depended heavily on individual experience and intuition.
- Relationship and communication changes were difficult to detect early.
After: Connected Decision Flow
- A prioritized overview showed where attention was needed.
- Health signals connected directly to stakeholder and activity context.
- Progressive detail supported both fast scanning and deeper investigation.
- CSMs could move through one clear flow from signal to evidence and action.
The redesign did not simply reorganize customer data. It changed how teams moved from information to understanding.
DESIGNING FOR CONFIDENT DECISIONS
Final Reflection
This project reinforced that designing for complex data is not primarily an exercise in displaying more information. The harder and more valuable challenge is creating a hierarchy that helps people recognize what matters, while preserving the evidence they need to trust and investigate each signal.
The solution became stronger when we stopped treating the dashboard, relationship map, and communication history as separate features and designed them as stages within one decision-making journey.
Prioritization Creates Clarity
Complex systems become more useful when the interface makes deliberate choices about what deserves attention first.
Evidence Builds Trust
AI-generated insights are easier to trust when users can trace them back to the people, activity, sentiment, and communication that produced them.
Connected Experiences Support Action
Individual views provide information. Their real value emerges when users can move between them without losing context or rebuilding the story themselves.
Staircase AI showed how thoughtful product design can turn fragmented customer signals into a coherent experience for understanding risk, relationships, and opportunity.