Created a database for internal use that will have all of the credit card offers for all channels and will also act as an API for developers. This database is a revised version from the current database.
Year
2024
Role
Led content and visual design. Met with all stakeholders to gather all needs and pain points.
Team
Credit Cards, Consumer Banking
Channel
Internal; web | English only
About
An internal database to manage all credit card offers, that will be used as an API for engineering to pull details for various credit card flows. This database allows for the growth of the credit card space through maintenance and automation. Growth in catering for specific segments and maintaining that individually. Growth to ensure content can be used effectively in different channels.
Current problems
1
Legal and footnotes have no consistency which causes legal implications when pulled in with other legal disclaimers.
2
Every offer is currently under a credit card and with hopes of growing the database to cover multiple campaigns, it is not scalable
3
Content is not mobile friendly. Content designers need to be able to structure content so it can be effective in the various channels
4
Offers can be updated and it is a manual process that requires dev support. If the tool can quickly update, product owners can own the process which will reduce human error
5
There are no filter options in current database. All offers (expired, current, campaign) are all batched together.
6
Different roles for database can help streamline process and help keep order with the hundreds of offers.
Allow for different roles to have different access to keep efficiency and order, but also to easily find the information needed or use it as it pertains to their role.
Filter by different categories
Different roles will use this database for different purposes. Business will review the content and offer lifespan, design will require access to the content and legal, while Product will manage the overall offer including how engineering will sync to the database for offer generation for various card flows.
Approval User
This tool will be owned by Product, so all updates will be approved by Product
View
In the current state, all users need a login to view the offers. Now anyone with the link can view the offers. So now legal, business partners, and other relevant stakeholders can view.
Edit
Decided on three roles Product, Designer and Business. Product will have edit and approve access, while Designer and Business will have edit access, only.
Pagination
In the current database, the list is never ending with every status of offer. Adding pagination will help with view
Roles for database
Unauthenticated
Any user with database link can access and view without logging in
Does not have any edit access
Can only view
Product
Can approve all activities
Can add new product offers
Can edit start and end date for offers. No other card offer information can be edited
Can duplicate an active offer. Duplicated offer will go into "pending" status
Can edit offer content including legal
Design
Can edit offer content including legal
Cannot add new product offer
Cannot edit card offer information
Can edit pending and active offers. If active offer is edited goes from active to pending until approval
Cannot duplicate offers
Product must approve all edits made by design
Business
Can add new product offers
Can edit start and end date for offers. No other card offer information can be updated
Can duplicate an active offer. Duplicated offer will go into "pending" status
Can edit offer content including legal for active/pending offers
Product must approve all activities made by business
Engineering
Cannot change any information
Will use database as an API to pull necessary information
