ENTERPRISE SaaS · DATA VISUALIZATION · PRODUCT DESIGN · DESIGN LEADERSHIP
Sprinklr Display Platform
Evolving a customization-heavy social-display tool into a scalable enterprise platform for large-format data storytelling.
From 2017 to 2026, I contributed to Sprinklr Display as a hands-on product designer and later managed its distributed design team. My work combined product design, customer delivery, data visualization, technical prototyping and team leadership.
Display builder
Builder
Published Display
Finished CCaaS Display
Sprinklr Display paired a browser-based builder with branded, large-format data experiences for command centers, executive environments and events.
Product Overview
From hands-on to design leadership
Sprinklr Display is a large-format data visualization platform used as a principal source of information that tells a story to its audience.
Display evolved from Postano’s social-display foundation into an enterprise visualization platform supporting richer data, more complex customer needs and information-dense CCaaS environments.
CHALLENGE
Customization did not scale with customer needs.
Display’s flexibility often depended on customer-specific design and CSS or JavaScript. Larger data feeds and denser CCaaS layouts exposed new platform, interaction and delivery constraints.
MY CONTRIBUTION
Product design and global team leadership.
I contributed selected widget controls, designed customer Displays, translated recurring implementation needs into product recommendations and later managed the three-person global design team responsible for Display delivery.
APPROACH
Customer evidence informed product improvements.
I worked across customer discovery, information design, technical prototyping and beta validation. As manager, I also guided designers through product constraints and represented the team’s delivery needs in roadmap discussions.
OUTCOMES
Reusable capabilities and delivery practices.
Recurring needs informed native semantic sorting and responsive widget behavior. The team also established reusable CCaaS patterns, a five-day minimum design window and customer guides later added to Sprinklr’s knowledge base.
SELECTED IMPACT
Native capabilities informed by recurring customer needs.
Responsive widgets supporting denser CCaaS layouts.
More scalable delivery and customer-enablement practices.
My Display Journey
2017
Joined during platform redesign
2018
Semantic sorting became native
2021
Became Product Design Manager
2022
First CCaaS implementation
2023–2024
Product development resumed with drill-down exploration.
2026
Five-day requirement added to SOW
Product role and context
As display evolved, my role evolved with it
Sprinklr acquired Postano in 2016 and began integrating its social-display model into the broader Sprinklr platform. I joined in 2017 while that transition was underway.
1. A presentation layer for enterprise data
Sprinklr Display turned data from the broader Sprinklr platform into branded visual stories for command centers, executive spaces and events. Unlike a traditional dashboard, it ran continuously on large screens and communicated selected information without requiring interaction.
The product in one sentence
A presentation layer that organized selected metrics, visualizations and social content into slides people could understand quickly or view from across a room.
Both experiences could use the same underlying data but were configured independently.
2. The platform evolution
Postano interface during the early platform transition, 2017
Sprinklr Display builder after the platform redesign, 2022.
- Social content foundation.
- Limited enterprise-data controls.
- Heavy limitations on customization.
- Controls reorganized by purpose.
- Data and visual settings separated.
- Widget-specific controls.
- Broader enterprise-data support.
3. Large screens changed the design priorities
Display was not simply a dashboard enlarged. Viewers might see a slide for only a few seconds or from several feet away, so every screen needed a clear message, readable data and controlled visual emphasis.
Glanceability
Make the primary message understandable within seconds.
Distance Legibility
Keep type, contrast and spacing clear across a room.
Information Hierarchy
Decide what deserves attention instead of treating every metric equally.
Data Density
Balance available information with viewing time and context.
Motion
Use animation to guide attention without distracting from the data.
Brand Integration
Create a recognizable experience without letting decoration overpower meaning.
The audience might look for only a few seconds or from several feet away. Each setting called for a different balance of information, motion and visual emphasis.
Command centers
Information-dense views for teams monitoring activity, performance and emerging issues.
Executive environments
Curated highlights with strong hierarchy, controlled content and limited visual noise.
Events
Branded, motion-led experiences combining live social content with supporting metrics.
A finished Display designed for quick comprehension, distance legibility and continuous large-screen viewing.
5. Two stages of contribution
My involvement covered two distinct stages: direct product and customer work, followed by management of the distributed team responsible for Display delivery.
Senior product designer
2017–2021
I worked directly on the platform and designed customer Displays for large-format environments. My role combined interface design, data visualization, discovery and technical prototyping.
Responsibility List:
- Contributed selected widget controls during the platform redesign.
- Designed branded Displays around customer data, audiences and environments.
- Used CSS and JavaScript to test ideas and address platform limitations.
- Participated in discovery, validation, implementation and training.
Primary Focus
Designing the product and using it directly with customers.
Product Design Manager
2021–2026
I managed 3 designers across New York, London and Dubai while remaining involved in complex customer work and product-development initiatives.
Responsibility List:
- Allocated work across overlapping global projects.
- Reviewed hierarchy, visual direction and implementation trade-offs.
- Helped designers navigate product constraints and Engineering dependencies.
- Represented the team’s delivery needs in product and roadmap discussions.
Primary Focus
Improving design quality, team capacity and the connection between customer work and product development.
How ownership worked
Designers retained ownership of their assigned customer solutions. My role was to provide direction, review important trade-offs, help remove delivery obstacles and connect recurring problems with the appropriate Product or Engineering partners.
I did not own Display’s entire product strategy. I contributed through direct product work, customer evidence, technical understanding and the priorities I represented on behalf of the design team.
Product influence
Finding the product opportunities through customer needs
Customer projects often required CSS or JavaScript to achieve behavior the platform did not yet support. When the same limitation appeared across projects, I documented the need, tested possible behavior and shared the evidence with Product and Engineering.
I contributed customer evidence, working prototypes and implementation feedback. Product and Engineering determined the final scope and built the native capabilities.
1. Making data order meaningful
I. Platform Default
Default data order
II. Custom Prototype
Behavior tested with Javascript
III. Native Capability
Semantic order supported by the platform
The Limitation
Some widgets followed a default data or alphabetical order even when the categories had a more meaningful sequence. This made the information harder to interpret at a glance.
My contribution
I used JavaScript to test a semantic order based on the meaning of the categories rather than their labels. The working implementation demonstrated the expected behavior in a real customer Display.
Product response
The recurring need helped inform native semantic sorting, allowing ordered categories to be configured without recreating the same custom script for each project.
A customer-specific workaround became a reusable platform capability.
2. Adapting widgets to denser layouts
The Limitation
Display widgets were originally designed for layouts containing a limited number of large visualizations. CCaaS projects introduced slides with more than 20 widgets, exposing problems with fixed spacing, labels and chart proportions at smaller sizes.
My contribution
Through customer implementations, I documented where widgets became difficult to read and used CSS and JavaScript to test more flexible behavior. I shared those patterns with Product and Engineering and evaluated later iterations against real CCaaS layouts.
Product response
Responsive behavior was introduced for selected widgets, allowing typography, spacing and supporting information to adapt as their containers changed size.
Denser operational layouts required less project-specific correction.
3. Customization as a testing ground
Not every custom solution became a product feature. CSS and JavaScript also allowed me to address needs tied to a particular customer, dataset or viewing environment.
Color overrides
Adjusted chart colors to support brand requirements, categorical meaning or stronger contrast.
Legibility treatments
Contrast layers on widgets to improve readability of text over imagery.
Widget-specific behavior
Modified spacing, labels or transitions when the available controls did not support the intended hierarchy.
4. From evidence to product decision
Native Capabilities
Native
Semantic sorting.
Native
Responsive behavior for selected widgets.
Native
Verified controls that became part of the product.
Customer-Specific Solutions
CUstom
Brand-specific color overrides.
CUstom
Specialized legibility treatments.
CUstom
Unique layout or animation requirements.
Takeaways
Custom implementation was valuable because it made product limitations tangible. It allowed us to test behavior in real environments, identify recurring needs and give Product and Engineering concrete evidence for future improvements.
Those same customer engagements also revealed how dramatically the design priorities changed between branded event Displays and information-dense operational environments.