How might we reimagine the
GT EX user experience by
creating an intuitive Content
Management System?

How might we reimagine the
GT EX user experience by
creating an intuitive Content
Management System?

How might we reimagine the
GT EX user experience by
creating an intuitive Content
Management System?


Admin Console


2023

Role: UX Design Analyst

Overview

I was a part of the GT EX (Global Technology Employee Experience) Website Team. My goal was to aid in reimagining the user experience of the Admin Console. To do this, I designed and built the GT EX Content Dashboard main page.


Note: Due to NDA, I cannot show all work.

Tools

Project Timeline:

Weeks 1-2: Discovery


Weeks 2-3: Defined user stories


Weeks 3-5: Gather peer feedback & ideate wireframes


Week 5-6: Lo-fi Design/ prototype


Week 7: Lo-fi test


Week 8: Lo-fi synthesis & bucketing


Week 9: Redesign test & Hi-fi design/ prototype


Week 10: Test/ Presentation

Weeks 1-2: Ideation & research


Weeks 2-3: Wireframing (lo-fi, mid-fi, hi-fi)


Weeks 3-5: Gather peer feedback


Week 5-6: Complete high-fidelity mockups


Week 7: Presentation

Why is this work important to JPMorgan Chase?

Why is this work important to JPMorgan Chase?

Saves Time

Saves Time

Streamlines processes for Writers, Collaborators, and individuals engaging with the content division of the go/GTEX website

Streamlines processes for Writers, Collaborators, and individuals engaging with the content division of the go/GTEX website

Less Maintenance

Less Upkeep

Lowered site upkeep

Lowered site upkeep

Consistency

Consistency

Ensures same look and feel in appearance / look and feel of the website

Ensures same look and feel in appearance / look and feel of the website

Personalization

Personalization

Customized website to meet JPMC specific needs

Customized website to meet JPMC specific needs

Design Process


Throughout the research and design phases, my team and I used the Double-Diamond Process Model. This design process model demonstrates how each aspect is iterative and that in order to discover the problem, we needed to first facilitate primary research. Through lo-fi pencil sketches and wireframing, we went through several iterations and rounds of user-testing that led us to our hi-fidelity prototype that was delivered to the Website Team.

Double Diamond Process Model



Double Diamond Process Model



01 Empathize

Objective: Design and build an internal Employee Experience Content Management system.

Who am I solving for? What is my process?

I am creating a Content Dashboard (CMS) known as the 'Admin Console' targeted toward content writers, contributors, developers and other internal JPMC GT EX website employees to use when managing article content on the GT EX Website. The interface aims to be easy-to-use and appealing when adding News content.


A core goal was to eliminate bias when defining the problem, so I surveyed JPMC employees internal to the Jersey City office who weren't all on the GT EX website team, to conduct discovery research holistically.


I facilitated about 5 interviews (15min/ person) to get a better understanding of the target audience with the following research goals:


  • Understand user behavior around using an internal employee website

  • To understand the challenges users face when trying to create/ manage content and articles

  • Discover pain points with existing apps/websites both internal and external to JPMC


I began the user interviews by asking questions around why this CMS Dashboard was important to the GT EX team so that I could get an understanding of the purpose and intent behind this new tool as well as my target audience’s pain points. Following this, my strategy was to follow up with questions such as:


  • How do you manage content currently?

  • What tools do you use/ lack that are pivotal to your day-to-day duties?

  • What challenges do you face?

  • When do you seek additional help for managing/ creating content?

  • What do you do when you can’t find the information you are looking for?


Research Summary

Bucketed categories of what participants seek in a content management system.

Editor Capability

  • Participants want Intuitive interactions when using the CMS interface

  • They want meaningful section titles/examples inside fields

  • Writers need to have appropriately sized fields when creating content

  • Formatting capabilities (bullets, bold, italicize, 

       number, indentation)

  • Content Writers and Admin Users can benefit from spelling/grammar checks

Content/Page list capability

  • Admins and non-content creators want the ability to easily sort & filter through content rather than spending time searching

  • Writers want the ability to publish/delete content 

  • All users need to view content status

  • Ability to view owners/stakeholders

  • Ability to view where content lives (status)

View in Admin Console

  • Users are keen to check the status of content: "Save/Submit for review".

  • It would be advantageous for users if there was an automated transfer of text and visuals from the testing phase to the final stage, preventing the need to submit numerous articles or content pieces individually.

Existing GT EX Website/ System solutions:

Before: Over 50% of admin console users lacked standard capabilities needed to perform their tasks

Before

  • Time consuming

  • Not intuitive

  • Outdated

  • Generic

  • Confusing

After

  • Intuitive

  • Concise

  • Minimalistic

  • Clean/ Modern

  • Customized

  • Intentional


02 Define

How can I ensure that what we create will suit the needs of our target demographic?


Who are our users?

Our main users include internal employees of the JPMC Global Technology Experience team who use the Admin Console as a means to share, track and create content on the GT EX Website.

Content Writers

Content Writers

Designers

Less Upkeep

Developers

Agility Leads

Agility Leads

User Persona

03 Ideate

What does the solution look and feel like and what are the next steps that need to unfold in order for a user like Lily to achieve her goal to use a customized dashboard with standard CMS core features in order to do her job effectively?


How can we make the most of Lily's needs to meet the project's primary objectives?


Who are our users?

Our main users include internal employees of the JPMC Global Technology Experience team who use the Admin Console as a means to share, track and create content on the GT EX Website.


In the user flow, my main focus was on making the process of managing intake of content and editing abilities of content as seamless as possible. It was crucial to be aware of cognitive load by separating the editing capability steps into individual screens that also include error pop-ups with content confirmation before proceeding to publishing content live on the website.

Design Process

Competitive Analysis


Competitor Platforms

An investigation was carried out to gain better insight into our competitors' landscapes. Our goal was to evaluate these competitors to ascertain if our redesign would be up to the same standard as theirs.


Some Questions that we asked included:

What message are we looking to deliver via our website?

  • How can we enhance the productivity of the website or admin console?

  • How could this online impression tie in with other current experiences on the platform?

  • In what ways can the web-based CMS align with different aspects of the site?



S.W.O.T Analysis

We conducted a comprehensive SWOT Analysis on three prominent website platforms, Squarespace, Wordpress and Shopify. This analysis gave us the chance to explore the strengths and weaknesses of every competitor while distinguishing opportunities for our own Admin Console.


Through this SWOT Analysis, I discovered opportunities that can aid in making our Admin Console stand apart from our competitors, like including stakeholder input and identification for giving different user permissions.



S.W.O.T Analysis

We conducted a comprehensive SWOT Analysis on three prominent website platforms, Squarespace, Wordpress and Shopify. This analysis gave us the chance to explore the strengths and weaknesses of every competitor while distinguishing opportunities for our own Admin Console.


Through this SWOT Analysis, I discovered opportunities that can aid in making our Admin Console stand apart from our competitors, like including stakeholder input and identification for giving different user permissions.


Strengths

  • ​Relevant and unique content

  • User friendly interface

  • Quick navigation

Opportunities

  • Works on all devices

  • Innovative marketing/ UI

  • New technology

  • Trendy designs

Weaknesses

  • Poor images

  • Long load time

  • Poort mobile optimization


Threats

  • Competitive disadvantage among competitors

  • Doubts about reliability


Strengths

  • ​Relevant and unique content

  • User friendly interface

  • Quick navigation

Opportunities

  • Works on all devices

  • Innovative marketing/ UI

  • New technology

  • Trendy designs

Weaknesses

  • Poor images

  • Long load time

  • Poort mobile optimization


Threats

  • Competitive disadvantage among competitors

  • Doubts about reliability


04 Prototype

Wireframes and Prototype / Rapid Prototyping The Solution


One article is selected by the user to either 'publish', 'delete' or 'hide'.

One article is selected by the user to either 'publish', 'delete' or 'hide'.

Existing states and scenarios with populated article content

on the Dashboard from Content Writers that are in 'drafts'.

Existing states and scenarios with populated article content

on the Dashboard from Content Writers that are in 'drafts'.

Upon selecting the 'publish' icon, there is a confirmation pop-up message to ensure this is the correct

action being taken to 'publish' the article.

Upon selecting the 'publish' icon, there is a confirmation pop-up message to ensure this is the correct

action being taken to 'publish' the article.

Confirmation toaster pop-up shows that the article was successfully published and live on the website.

Confirmation toaster pop-up shows that the article was successfully published and live on the website.


Fundamentally, this greatly enhances key features of a CMS within the JPMC Admin Console that were missing previously.

Now, users have the ability to control, modify, and assign diverse user privileges for content, among other capabilities,

all from the comfort of this CMS table.


Fundamentally, this greatly enhances key features of a CMS within the JPMC Admin Console that were missing previously.

Now, users have the ability to control, modify, and assign diverse user privileges for content, among other capabilities,

all from the comfort of this CMS table.

Onboarding Experience

The primary goal of onboarding is to introduce and set user expectations for a new experience. I began by creating wireframes and concepts that prove how a user benefits from using the platform only once they create an account however I chose to begin by creating the experience for how a user interacts with the platform based on their first interaction.
This would be via the home screen which would entail seeing the NON-POPULATED content dashboard Admin Console before any content has been added to it. Upon conducting further research on common onboarding practices, I shifted my approach to designing a solution to this problem and honed in on the progressive experience a user has through the home dashboard screen with the table and it's empty state.
Then, I chose to showcase how the user goes from an empty state to a populated table in which they then have the option to publish, delete, or hide their content on the website.


Onboarding Experience

The primary goal of onboarding is to introduce and set user expectations for a new experience. I began by creating wireframes and concepts that prove how a user benefits from using the platform only once they create an account however I chose to begin by creating the experience for how a user interacts with the platform based on their first interaction.
This would be via the home screen which would entail seeing the NON-POPULATED content dashboard Admin Console before any content has been added to it. Upon conducting further research on common onboarding practices, I shifted my approach to designing a solution to this problem and honed in on the progressive experience a user has through the home dashboard screen with the table and it's empty state.
Then, I chose to showcase how the user goes from an empty state to a populated table in which they then have the option to publish, delete, or hide their content on the website.

User Testing

Upon completion of the first working prototype, we conducted user tests in order to validate my designs. Feedback was necessary for usability, information architecture, user interactions, visual design and personalization aspects.


We reached out to many of the original participants from our interviews in which the participants shared their screens and provided commentary as we asked them to perform six tasks through main scenarios. Below are 2/6 scenarios that we facilitated.


When testing with users, the goals were to:

  1. Gather quick user feedback to design more intuitive experiences.

  2. Value the prototype feedback with the technical architecture in mind (for development purposes)


Sample Pool/ Interview Participants

2 groups: Users and Development


  1. General Users: When testing with general users, this included designers, agility leads, contributors and researchers. We aimed to gather quick user feedback to design more intuitive experiences for those who would be general users of the Admin Console.


  1. Development: When testing with development, we aimed to value the prototype with the technical architecture in mind. Our goal was to conduct primary research involving actual JPMC employees to develop a clearer understanding of our early stage design of the Content Dashboard.


Why this participant group? 

We confined our audience to those within my team's 'vicinity' since they were familiar with the structure of go/GTEX.







Task Flow

1. User lands on Admin View (Preview Mode)
2. User clicks "Add a News article"
3. Modal pops up with form fields
a. User fills out the title
b. User fills out the abstract
c. User uploads the thumbnail (drag & drop or clicks add files)
i. IDEAL - Opens asset manager and selects file
ii. Currently on prototype - Opens files from computer and selects file
d. User clicks "Save"
4. Confirmation modal that let's users know their changes were saved and they can continue to make edits.
5. User selects "Continue"
6. User is brought to the News article template page
a. Title, abstract, and thumbnail are repopulated
b. Slug and helmet are generated from the Title
User fills out all required fields
8. User selects save draft
9. Confirmation modal appears letting user know their changes were saved and if they want to preview changes.
10. User selects "Preview"
11. Preview of live content of the News article appears
12. If user is satisfied with draft, at the Preview mode screen, user selects

"Submit for Review"
13. News article status changes from "Draft" to "Ready for Review" on Content Dashboard


What is the impact of my work and contributions to the GT EX Team at JPMC?

Simplicity

Use basic yet impactful layouts

Time

Users strive to find data and information with little time expenditure

Control

Allow users the choice to leave their current interaction and pursue their experience, while enabling contributors to modify content and perceive the alteration instantly

UI Consistency

Visitors desire an interface that upholds the uniformity seen throughout the site

Navigation

Contributors desire a user-friendly interface that can be used by everyone

Accessibility

I ensured that the design complied with as many WCAG standards as the timeframe allowed and that the system would be accessible to users

© Ariana's Portfolio