First Data DecisionQuest
Decisioning Campaign Creator

First Data – Internal Promotions & Campaign Management Redesign

Challenge
First Data previously relied on extensive training to help internal teams navigate a complex, unintuitive system for creating and managing promotional campaigns on behalf of clients. To reduce training costs and improve efficiency, the UX team was tasked with redesigning the internal application to make campaign setup, rule creation, and tracking more intuitive.

Guiding Principles

  • Wayfinding & Navigation: Internal users worked collaboratively across multiple teams, so a clear and consistent left-side navigation system was critical for locating campaigns quickly.

  • Language & Terminology: The existing system used esoteric jargon that confused users. I developed a more intuitive information architecture and labeling system to improve clarity and discoverability.

  • Consistency & Transparency: The new design emphasized showing which rules had already been applied to campaigns and enabled users to reuse rules from past campaigns to save time and ensure consistency.

Key User Behaviors Identified
Through research and workflow analysis, we observed that internal users frequently:

  • Needed to find and resume campaigns created days or weeks earlier.

  • Required the ability to name, categorize, and track campaigns across teams.

  • Relied on setting decisioning rules (e.g., credit approval) to streamline campaign targeting.

  • Preferred to duplicate existing rules instead of creating new ones from scratch.

Impact
The redesigned application reduced reliance on training by offering a more intuitive, structured, and user-friendly interface. By simplifying navigation, clarifying terminology, and enabling reusable rules, the UX solution streamlined internal workflows, improved data entry efficiency, and supported First Data’s efforts to optimize promotional campaign management at scale.

I am designing for Data Entry Clerks that have specific roles, some of them use multiple apps while others specialize in specific apps.  The design team and I interviewed the internal Data Entry team that handled the Old Decision Question Application

I am designing for Data Entry Clerks that have specific roles, some of them use multiple apps while others specialize in specific apps. The design team and I interviewed the internal Data Entry team that handled the Old Decision Question Application

Capturing The  ProcessAs we spoke to the internal Data Entry team, they walked through the UI as we asked questions about pain points and the overall team process.I captured the main phases in a journey map From a UX standpoint, key principles of Placemaking and Resilience of information were an issue.As users created Campaigns that contains elements inside of elements users would get lost, and the information did not bubble upthis disoriented users on what campaigns to work on, finding out what is inside the campaigns just to get started was a task in itself.Many of the same rules get applied to multiple campaigns so much of the work was redundant.

Capturing The Process

As we spoke to the internal Data Entry team, they walked through the UI as we asked questions about pain points and the overall team process.

I captured the main phases in a journey map
From a UX standpoint, key principles of Placemaking and Resilience of information were an issue.

As users created Campaigns that contains elements inside of elements users would get lost, and the information did not bubble up

this disoriented users on what campaigns to work on, finding out what is inside the campaigns just to get started was a task in itself.

Many of the same rules get applied to multiple campaigns so much of the work was redundant.

How the Puzzle FitsThe language itself was unintuitive, (Credit spreak) but dictated by FirstData business rules and industry standards which put some nomenclature changes out of scope.I did need to grasp how all the information with a campaign is related and created.I crafted a concept map to see how the information impacts each other. Somethings internally bubble up to information above it. Rules impact criteria and segments impact the available rules.

How the Puzzle Fits

The language itself was unintuitive, (Credit spreak) but dictated by FirstData business rules and industry standards which put some nomenclature changes out of scope.

I did need to grasp how all the information with a campaign is related and created.

I crafted a concept map to see how the information impacts each other.
Somethings internally bubble up to information above it. Rules impact criteria and segments impact the available rules.

I mapped out the current user flow of campaigns are created right down to the offer.

Understanding all the components that make up the process enabled me to StoryMap the steps from the user perspective.

Mapping all the steps out allows me to look at the entire process while adding ideas to solve usability issues under each step. Some of these design ideas will be essential some of them are nice to have depending on the technical feasibility of the design ideas. I worked with a JavaScript Guru that could help estimate how long some of these ideas would take.

IMG_5703.jpg
  • Intandem with story mapping I sketch out the and patterns and ideas, this helps to get the team on the same page.

  • Allow users to open a drawer showing what is inside of past campaigns. as well as a table giving a brief summary of what’s inside.

  • Also in creating a campaign invite users to put elements

    within elements while showing the progress of the overall campaign. keeping the user-oriented.

CampaignCretionflow.jpg

  • I wire-flowed a pattern to communicate the prime interactions

  • that include searching for elements on the left and applying them to the right, and all editing takes place on the created area.

  • Keeping this pattern consistant is important because the overall process demands putting elements within elements.

Previous
Previous

ListManagement & Segments

Next
Next

UCLA Care Access