Oracle
Sr. Director, User Experience · 2012 – 2018 · Redwood Shores, CA
The Situation
Oracle Marketing Cloud was Oracle's answer to the enterprise marketing automation market, a suite of products capable of orchestrating campaigns across email, push, SMS, and more, with deep personalization and targeting. At its scale, the platform sent over 300 billion messages annually and generated over $200M in recurring revenue globally.
But the suite wasn't built; it was assembled. Five products, acquired at different times, from different companies, built on different front-end architectures, with five different design languages, navigation systems, and interaction models. For customers who used more than one product, the experience was jarring. For customers evaluating the platform, fragmented UX was one of the most frequently cited reasons for walking away.
I came in before the Oracle acquisition, joining Responsys in 2011 when the UX situation there was already broken: a product largely built by engineers and "dressed up" by designers after the fact, shipped when time allowed. Over three years I rebuilt that practice from the ground up. When Oracle acquired Responsys to anchor the Marketing Cloud suite, I was asked to do the same thing at a much larger scale.
You can't impose consistency; you have to build toward it from shared recognition.
My Role & What I Was Working With
I was appointed to lead the combined UX organization across all five Marketing Cloud properties: Responsys, Eloqua, Maximizer, Data Cloud, and Social Marketing. That meant 18 designers across four countries (the US, Canada, India, and the UK), including three UX leads who came from the acquired companies and were now reporting to me.
The reason I was asked to lead this effort was straightforward: Responsys had been acquired as the flagship of the suite, and by that point our design patterns were the most mature of any property in the group. Management wanted the suite built around those foundations. I was the only senior design leader who had both the design systems background and the organizational experience to run that kind of cross-team consolidation.
What that also meant, practically, was that I was walking into teams with their own design identities, their own product loyalties, and their own engineering relationships, asking them to give up their autonomy for the good of a suite they hadn't asked to be part of.
The Work
Before the acquisition, the work at Responsys was its own significant effort. UX had been an afterthought: features were engineered first, then styled, then shipped whenever there was bandwidth. I hired strong designers, built a research and feedback practice, and systematically worked toward consistency across the product over multiple release cycles. We also introduced a highly visual campaign-building experience that simply hadn't existed before, a capability that would later become a differentiator for the entire suite.
By the time Oracle came calling, UX at Responsys had moved from the most complained-about aspect of the product to a competitive strength. That track record was the credibility I brought into the larger challenge.
With five fragmented products now in scope, the temptation would have been to mandate the Responsys design system immediately. I took a different approach: I started by running cross-team design sessions to map what the products actually had in common. Most had some form of WYSIWYG editor for building emails and landing pages. All had CRM integration configuration. Navigation differed on the surface, but the underlying information architecture was often more similar than the teams realized.
That mapping exercise did two things: it identified the genuine common ground that could anchor a shared system, and it gave the other teams a reason to engage rather than resist.
The fragmented front-end architectures across the five products were a real constraint. Getting every team to rebuild components from scratch on a unified technical foundation wasn't realistic in the near term. So I made a deliberate sequencing decision: prioritize visual consistency first. Standardized color palette, icon set, typography, form layouts, navigation patterns, even if the underlying implementation varied slightly, users would experience a coherent suite. This approach let us move faster and show meaningful progress to product leadership without getting blocked by engineering complexity.
The hardest part of this effort wasn't the design work; it was getting the acquired engineering teams to adopt the new system at all. Management backing helped, but it wasn't sufficient. The real breakthrough was an organizational decision: I established a separate, dedicated UI team with no existing loyalty to any one product. Their sole mandate was to build out the new suite-level components and patterns.
This neutrality mattered. Teams that might have resisted adopting "Responsys patterns" were more willing to adopt components built by a team with no agenda. It removed the politics from the technical conversation.
I ran twice-weekly virtual design reviews where designers presented work in progress before anything went to engineering. The goal was consistency enforcement without micromanagement, a shared checkpoint that caught divergence early. I also held weekly meetings with the three UX leads to track progress and coordinate at the organizational level, leaving day-to-day execution to them. That structure, close enough to catch problems and distributed enough to scale, let us maintain momentum without everything flowing through me.
The Outcome
The transformation in how customers perceived the UX was stark. Before this work began, user experience was among the most commonly cited reasons for churn. By the time the suite reached maturity, UX had become one of the top reasons customers chose Oracle Marketing Cloud over competitors. That's not an incremental improvement; it's a complete reversal of a product's competitive positioning, driven by design.
The visual campaign-building experience introduced during the Responsys years became a hallmark feature of the suite. The shared design system, built through the neutral UI team and enforced through cross-team design reviews, gave 18 designers in four countries a common language and a common standard to work from.
That's not an incremental improvement; it's a complete reversal of a product's competitive positioning, driven by design.