Mockup of final Multilingual Templates feature

Asurion Service Sites Refresh

Overview

Long story short
From May to July 2019, I worked as a UX Design Intern at Asurion. I was a part of the Service Sites Refresh team, where we redesigned the insurance sites for several of our mobile carrier clients, specifically Sprint and AT&T. Here's some of the work that I got to be a part of!

ROLE: UX Design Intern
TEAM:
Product manager, lead designer (+me), lead developer (+2 developers)
TOOLS USED:
Figma, UserTesting.com
WHEN:
May-July 2019

Project Description

What were we tasked with?
Design a refreshed web experience, user experience and development platform for SprintComplete.com (and later also Protectioncenter.ATT.com) service sites that encourages and facilitates continued personalized engagement among our customers.

I worked on four parts of this project:

User Research

Customer Discovery Interviews

Let's talk to some people!
We conducted initial customer discovery interviews through Usertesting.com to gain insights on what users expect to see on their mobile insurance site. We had them walk through receiving the brochure in store, navigating to the website, and then log onto the website.

From this, we collected some key findings:

Card Sorting

Not quite "52 Pickup"
We also recruited some coworkers to do a card sorting exercise to figure out what features we expect on a mobile insurance site. From there, we thought about which features needed to be prioritized, which ones are essential for the website experience, and what message do we want to convey to the customer when they reach the site.

User flow diagram for adding translations

Results of card sorting: 18 main features expected on a mobile insurance site

Participatory Design

Group activity!
We conducted some participatory design activities to gain an even better perspective of what users expect to see in their logged-in dashboard on their mobile insurance site. We recruited a group of participants online and gave them some exercises to draw out what they currently think is their mobile insurance site, an example of a “hub” that they commonly use, and what they want to see on their mobile insurance site.

One of main findings was that users want a very personalized hub with the ability to view plan usage and alerts, especially for their children. Many users also were not aware of all the features that came with the protection plans that they had purchased.
User flow diagram for adding translations

Participants doing an exercise where they create their own "ideal hub" while munching on snacks!

User Flow

A big web!
Based on our research, we were able to create a user flow diagram to map out the user experience going through the website. This helped us illustrate where users expect different features and better understand where to place key business features.
User flow diagram for adding translations

Large user flow diagram!

Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

A little messy, bear with me.

Iterating the Designs

Second drafts, second drafts!
I moved forward with two main designs to be higher fidelity: a horizontal dropdown and a vertical sidebar. According to feedback I received, we wanted to make sure that the navigation was very adaptable, so I explored different ways to do so, including removing icons/graphics and adding accordions. I also looked at how the designs would translate between desktop and mobile views.

Final Design Choices

What'd I end with?
In the end, we decided to go with a purely text navigation to optimize space, accessibility, and adaptability. All text allows for sections to easily be switched out and moved around with minimal strain. The new navigation will be accessible on every web page and includes sections that connect each part of the website.
Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

Desktop and mobile versions of the navigation

The "Recommender"

The “recommender” is a navigational tool that we created to encourage user engagement and personalization. Like the navigation bar, it also connects different parts of the website but it is driven by the user’s needs and interests. It will recommend different experiences and content based on what pages the user has viewed.

User Flow Diagram

Can you tell it's my favorite diagram?
We started by creating a diagram to map out how the recommender could redirect the user to different experiences within the website. This will help us in thinking about how the tool will look like and how it can fit on each page to shape the user experience.

User flow diagram for adding translations

The "Recommender" user flows from different pages on the site

Initial Sketches

Square 1!
In creating the design for the recommender, we considered how the user flow would look like when using it. We looked at where it could live on the website so that it would be consistent and accessible, as well as engaging. Early on, we decided that using cards would be an easily-adaptable, yet engaging design pattern to use in the recommender.
Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

Lots of different ways to go about this...

Adding Features

Iterating and iterating ...
I continued to explore how the cards could look and how they would be laid out within the recommender. I played with how to display the information on the card, as well as how to create an engaging call-to-action. I also looked at how to better the user experience to make it feel more personalized, such as “Save for later” and “Give me new recommendations” buttons. Each iteration considered scalability between desktop and mobile versions.
User flow diagram for adding translations

Iterating card designs for desktop and mobile versions.

User flow diagram for adding translations

An iteration that allowed for a more personalized experience in the site header/hero.

Increasing Engagement and Personalization

We can make it better
We decided to switch from icons to photos to make the cards more engaging. We also transitioned from a “Save for later” CTA to a simpler heart “favorite” feature to make better use of space. The labels above the cards would change based the card’s content and help make the recommender more personalized.
Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

More iterations to increase user engagement

User flow diagram for adding translations

Mockup of the current iterations of the Recommender on an example page

Final Designs

What'd we finally land on?
The recommender cards then went through several iterations before being finalized. We created different cards to differentiate primary versus secondary recommendations for the user. The primary cards use a dark gradient to draw more attention, whereas the secondary cards are more minimal to fit more on a page without it being too cluttered. They are also skinned differently depending on the service provider.
Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

Final versions of the Recommender card designs

Landing Pages

For each of the experiences on the service sites, we created a landing page that gives an overview of the experience and also directs to relevant content. The landing pages create an intermediate place for the user to land on to better understand where they’re being directed to and where to view similar, relevant information.

The Problem

What's wrong with the pages now?
The original service site CTAs directed the user automatically to different websites, so the sites lacked cohesion and created a lot of confusion for the user. There is no “hub” for all services and experiences that fall under a specific category, so the user can’t easily find relevant interests, making for a poor user experience.

First Drafts

The process begins anew ...
Originally, the user dashboard/home page acted as the landing page to reach the different experiences on the service site. Following our hypothesis, we planned to have a “preferences selection” for the users to better personalize the content that they see. We later decided to simply use cookies to pull up relevant content to streamline the user experience.

Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

Final versions of the Recommender card designs

Our Solution

The process begins anew ...
Our landing pages would have universal headers and footers to maintain consistency throughout the site. The information on the page would be customized based on the experiences (phone optimization, photography, security, etc).

Request for a feature to translate and allow multiple languages for templates with 357 votes on it

Initial site page template

Iterations

You get the gist by now
I created several designs for possible landing page layouts for both AT&T and Sprint, as well as in desktop and mobile views. We wanted to make the landing pages appear dynamic and engaging for the user to scroll through. We decided to use block-based formats because one of our main considerations was making sure that there was a seamless transition from desktop to mobile views — blocks allow for an easier yet consistent arrangement between different resolutions. (P.S. the recommender makes an appearance on the landing pages, too!)

As this was toward the end of my internship, these intermediate designs will (hopefully) be used to influence future iterations of the landing pages!

Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

Final iterations of the site designs

Conclusion

As my first real internship doing UX Design, this was an incredibly eye-opening experience. Thank goodness I came out of it loving UX Design even more rather than the opposite. Here’s just a few of the many things I learned during my short time at Asurion:
Request for a feature to translate and allow multiple languages for templates with 357 votes on it

Morgan (my manager) and me 🥰

I absolutely loved my 10-week stay at Asurion. It taught me so much about the field of UX Design in industry and gave me a newfound appreciation for all the work they put into developing new products. It was also because of my amazing supervisor Morgan that I got to work on such a dynamic and fun project!

***This is my work as of the end of my internship at the end of July 2019. Many of these designs are works-in-progress as the final sites will not be launched until Fall 2019. The final product may vary!