Redefining Workday Success Plans:
From reactive support to strategic partnership
Overview
Workday Success Plans (WSP) were originally structured as support packages — reactive, transactional, and service-bound.
In my role as the Lead Product Designer, I reframed the initiative into a strategic experience platform that connected product insights, service delivery, and customer success into one measurable ecosystem.
Context & Challenge
| “We weren’t just fixing issues. We were fixing the relationship.”
When I joined the Workday Success Plan (WSP) initiative, it was positioned as a support-tier optimization project.
But beneath that, I saw a deeper challenge: Workday’s customers didn’t see “Success Plans” as strategic. They saw them as insurance policies.
Across teams, the symptoms were clear:
Disconnected customer touchpoints
Duplicated engagement tools
Siloed data on customer health
Teams measuring success differently
Our interfaces weren’t the real problem — our definition of “success” was.
I reframed the initiative: this wasn’t about better dashboards — it was about turning a service model into a partnership model.
Key challenge statements
Fragmented customer experience across touchpoints
Limited visibility into customer success health
Reactive engagement workflows
Misaligned KPIs across Services, Product, and CS teams
Strategic Vision
| “From solving tickets to designing outcomes.”
The new vision for WSP positioned design as the connective tissue between customer value and business growth.
The goal was simple — and radical: elevate customer success from reactive support to proactive partnership.
We introduced a new framing around three design principles:
Predictive: Anticipate customer needs before they escalate
Proactive: Guide through insights, not after-the-fact responses
Partnered: Measure success together, not in silos
To align leadership, I ran a cross-functional strategy sprint across Product, Services, and Marketing.
We used a CSD Matrix (Certainties, Suppositions, Doubts) to surface assumptions and mapped business goals through a Strategy Map linking customer outcomes to Workday KPIs.
This was not a design exercise — it was a business transformation conversation.
| “WSP wasn’t a service plan. It was a new language for partners.”
Foundations for Transformation
| “Before we could transform the experience, we had to understand the chaos.”
We started with a full service ecosystem audit — mapping every customer and internal touchpoint.
This revealed duplicated workflows, inconsistent success metrics, and reactive triggers scattered across teams.
From this, we defined three foundational pillars to guide the transformation:
Principles — clarity, transparency, and co-ownership
People — empowered customer-success managers as experience drivers
Patterns — standardized tools and signals to measure value consistently
Tooling alignment bridged design and delivery:
→ Figma for journey visualisation
→ Tableau + Workday Prism for insights
→ Internal design ops hub for documentation + governance.
Research & Insights
| “A design system without operations is just a library.”
A multi-layered research approach combined quantitative analytics and qualitative discovery:
Quantitative:
Support ticket clustering
Engagement + usage analytics
NPS trend analysis
Qualitative:
Customer advisory board interviews
Service-journey workshops
Success manager shadowing
Core insight:
| “We don’t want to be managed — we want to be guided.”
Customers valued clarity, predictability, and partnership over volume of service.
We reframed WSP as a proactive compass that helps customers plan, not react.
Designing the WSP Experience
| “We built WSP as an insight engine — not a support portal.”
We designed and tested the Success Command Center — a unified interface that centralized customer health signals, proactive engagement triggers, and ROI storytelling.
Delivery was structured into three coordinated tracks:
Foundations — visual frameworks, data architecture, service blueprints
Core Components — engagement modules, health summaries, ROI narratives
Experience Patterns — lifecycle moments (onboarding, renewal, expansion)
Each track paired a designer and service architect (“two-in-a-box”) to ensure both usability and operational feasibility.
Design prototypes evolved from static dashboards to an interactive decision layer embedded in Workday’s service workflow.
Testing with Customer Success Managers validated measurable improvements:
40% faster time-to-insight
25% reduction in redundant service actions
| “We went from managing customers to guiding outcomes.”
Cross-Functional Enablement
| “Great experiences don’t scale without great operations.”
The success of WSP depended on alignment across disciplines.
Once the product direction was clear, my focus shifted to making the work sustainable.
We needed a repeatable model to align design, engineering, and services around a single operating rhythm.
Key enablers:
Experience Guild: a cross-functional council for design + service governance
Outcome Framework: standardized definitions of “success moments”
Design Ops Toolkit: templates, documentation, and scorecards for ongoing iteration
Office Hours: weekly syncs with service leads to surface feedback and scale adoption
This transformed design from a contributor role to a strategic orchestrator — ensuring continuity across every customer journey.
Measurable Impact
| “Design became a growth lever — not a support function.”
We quantified success through a Design Scorecard, connecting UX performance and service metrics directly to business outcomes.
Key Metrics (Pilot Regions):
+8% customer retention
+25% proactive issue resolution (ticket deflection)
+2.3× perceived strategic value (surveyed customers)
Beyond metrics, the Scorecard created new behavior: every Success Manager began tracking design-enabled outcomes, not just support resolutions.
| “We didn’t just improve the experience. We improved how success was measured.”
Reflection and Evolution
| “Design’s greatest output is alignment.”
The WSP initiative reshaped how Workday’s design, product, and services teams work together.
It was less about creating new assets and more about creating shared understanding.
If I were to start again, I’d:
Integrate business metrics earlier in prototyping.
Build cross-functional storytelling rituals sooner.
Formalize DesignOps leadership roles from day one.
Today, WSP is used globally as the framework for measuring partnership value — a living system that continues to evolve with every customer insight.
Other Projects...
