All case studies
Case Study · Operative
Unifying a Fragmented Five-Product Experience
Five enterprise products had drifted onto different stacks and different looks. Instead of waiting on a full retrofit, I sequenced a shared, more accessible design language customers could feel — and it launched by year end.
Role
Vice President, Product Design
Initiative
Portfolio Design Language & Accessibility Modernization
Scope
5 enterprise product lines
Organization
~20 across Design, Product + Front-End Engineering
Geography
North America + EMEA
The 15-second version
The story at a glance
5
Fragmented products brought under one shared design language
23%
Lower platform development costs across the broader modernization this release began
Record
Client retention after launch, with increased RFP activity
01 The situation
Five core solutions were fragmented across different technology stacks, with inconsistent experiences, low engagement, high abandonment, low CSAT, weak accessibility compliance, and limited commercial enthusiasm.
02 My move
I evaluated the portfolio, established baseline measures, spoke with end users, and reframed a full retrofit into a phased modernization strategy that could deliver visible value sooner.
03 The outcome
The first portfolio-wide refresh launched at year end, followed by higher engagement, lower abandonment, higher CSAT, improved accessibility compliance, record client retention, and increased RFP activity. The broader modernization it began contributed to 23% lower platform development costs, 18% higher release velocity, and 20–30% faster design/engineering cycles.
The pivotal decision
Instead of waiting for a complete end-to-end retrofit, I proposed a deliberate first phase: establish a shared visual language across all five solutions, use color and hierarchy more intentionally, improve accessibility where the first release could, and pair that work with a roadmap for deeper workflow, code, design-system, and compliance improvements.
The full story
For those who want the detail
Chapter 01
The challenge
Operative’s five core solutions had evolved on different technology stacks and with different interface patterns. The result was a fragmented product ecosystem: users moved between inconsistent visual languages and workflows, engagement was low, abandonment was high, CSAT was low, accessibility compliance needed improvement, and the portfolio was not generating the level of enthusiasm we wanted from Sales and Marketing.
The long-term answer was clear: consistent workflows, accessible code and design, a shared design language, and a scalable design system. The harder question was sequencing. Attempting to retrofit every product at once would take significant time and would delay visible customer value.
Chapter 02
My mandate
I led the initiative to define a credible first move, align stakeholders around the tradeoff, improve the experience without pretending the first phase solved everything, and create a roadmap that could continue raising consistency and accessibility over time.
The team model
A close cross-functional team of UX designers, front-end engineers, Product, and end users created a shared design language and a roadmap for deeper workflow, design-system, and accessibility improvements.
Chapter 03
How I approached it
01
Use end users to identify friction and opportunity
I spoke with end users to understand where the fragmented experience created confusion, extra effort, or inconsistency as they moved through the product ecosystem. Their input helped us identify which changes could create immediate clarity and which issues required deeper workflow or technical modernization.
02
Make the sequencing tradeoff explicit
A complete retrofit would require a new design language, workflow standardization, accessible code changes, accessible design changes, and a full design system. I brought that scope to stakeholders and leadership and recommended a phased approach: deliver a coherent first visual and accessibility layer now, then continue the deeper modernization incrementally.
03
Build the language with Product and Engineering
I formed a close working team across UX design, front-end engineering, Product, and end users. Together, we scoped and built a new design language for the solution ecosystem so the first phase was both design-led and grounded in what could be implemented across different technical foundations.
04
Focus phase one on visible consistency and accessibility
The initial release concentrated on the shared fundamentals that could improve the portfolio quickly: fonts, color, spacing, typography, hierarchy, and accessibility-oriented use of visual cues. We were explicit that this was a foundation, not the finish line. The roadmap carried forward the deeper work on workflows, code, accessibility, and design-system maturity.
05
Release, measure, and use the response to build momentum
The refreshed experience launched at the end of the year. We sampled the same measures we had baselined at the start and used the results to assess both user impact and the broader commercial signal from clients and prospects.
Chapter 04
Results
We re-sampled the same categories used in the baseline. Client-level engagement and CSAT figures are confidential, so they are shown directionally; the platform metrics come from Operative’s broader modernization, which this release started.
Engagement
Low
Higher engagement
Abandonment
High
Lower abandonment
CSAT
Low
Higher customer satisfaction
Accessibility
Low compliance
Higher accessibility compliance, with continued work on the roadmap
Commercial response
Limited Sales/Marketing engagement
Record client retention and increased RFP activity
Platform development cost
Fragmented across five stacks
23% lower (broader modernization)
Release velocity
Baseline
18% higher
Design/engineering cycle time
Baseline
20–30% faster
Chapter 05
Why it worked
Progress with a clear destination
The first release was intentionally bounded, but it was tied to a roadmap that made the broader modernization path visible.
Consistency across the ecosystem
A shared design language reduced the sense that customers were moving among unrelated products and signaled sustained investment in experience quality.
End users inside the work
User involvement from discovery through validation kept the modernization grounded in real friction rather than internal aesthetic preference.
Design and Engineering shaping the foundation together
Working with front-end engineers early helped us create a language that could move across products with different technical foundations.
Chapter 06
What I learned
End users need to stay involved from beginning to end so the team can validate whether the modernization is solving real problems.
Progress can be more valuable than waiting for perfection. A first iteration focused on typography, color, spacing, hierarchy, and accessibility can create momentum when it is part of a credible longer-term plan.
A seamless design language can do more than improve aesthetics. It can signal product investment, strengthen customer confidence, and create the expectation of continued experience improvement.
Chapter 07
The system, visualized
Leadership takeaway
The key was not treating the reskin as the strategy. The strategy was sequencing: deliver a coherent and more accessible foundation that customers could feel, measure the response, and use that momentum to support deeper workflow, code, and design-system modernization.