Web

Mobile

App

Introducing T-Mobile IDs

Introducing T-Mobile IDs

Introducing T-Mobile IDs

Introducing T-Mobile IDs

Introducing T-Mobile IDs

The F&BV Digital Profile project aimed to update the existing line permissions page and overall user experience. The focus was on transitioning from using MSISDNs (phone numbers) to T-Mobile IDs, paving the way for T-Mobile IDs to be used for all T-Mobile products and services.

There are 4 different roles every user can have which are primary account holder, authorized user, standard user, restricted user


The F&BV Digital Profile project aimed to update the existing line permissions page and overall user experience. The focus was on transitioning from using MSISDNs (phone numbers) to T-Mobile IDs, paving the way for T-Mobile IDs to be used for all T-Mobile products and services.

There are 4 different roles every user can have which are primary account holder, authorized user, standard user, restricted user


The F&BV Digital Profile project aimed to update the existing line permissions page and overall user experience. The focus was on transitioning from using MSISDNs (phone numbers) to T-Mobile IDs, paving the way for T-Mobile IDs to be used for all T-Mobile products and services.

There are 4 different roles every user can have which are primary account holder, authorized user, standard user, restricted user


The F&BV Digital Profile project aimed to update the existing line permissions page and overall user experience. The focus was on transitioning from using MSISDNs (phone numbers) to T-Mobile IDs, paving the way for T-Mobile IDs to be used for all T-Mobile products and services.

There are 4 different roles every user can have which are primary account holder, authorized user, standard user, restricted user


The F&BV Digital Profile project aimed to update the existing line permissions page and overall user experience. The focus was on transitioning from using MSISDNs (phone numbers) to T-Mobile IDs, paving the way for T-Mobile IDs to be used for all T-Mobile products and services.

There are 4 different roles every user can have which are primary account holder, authorized user, standard user, restricted user


2022

Timeline

UX Designer

My Role

Dev Manager, Product Owner, Project Manager, Copywriter

Dev Manager, Product Owner, Project Manager, Copywriter

Dev Manager, Product Owner, Project Manager, Copywriter

Dev Manager, Product Owner, Project Manager, Copywriter

The Team

Use nice finished designs
Use nice finished designs
Use nice finished designs
Use nice finished designs
Use nice finished designs

Mobile view of the different T-Mobile ID user role pages.

Streamline account management with T-Mobile IDs

Streamline account management with T-Mobile IDs

The primary objective was to enhance the line permissions page and overall experience by transitioning to T-Mobile IDs for all customers to create a unified sign-on experience.

This transition allowed customers, including those without traditional phone numbers—such as T-Mobile Home Internet users—to manage their accounts seamlessly.

The primary objective was to enhance the line permissions page and overall experience by transitioning to T-Mobile IDs for all customers to create a unified sign-on experience.

This transition allowed customers, including those without traditional phone numbers—such as T-Mobile Home Internet users—to manage their accounts seamlessly.

Tackling T-Mobile ID integration

Tackling T-Mobile ID integration

On the backend, user roles were still connected to MSISDNs, so we needed to create an experience that not only appeared but worked as though they were linked to T-Mobile IDs. The complexity increased for users with multiple lines attached to their T-Mobile ID, as we had to determine how to assign appropriate user roles to these users. For instance, when a user had two or more lines linked to their T-Mobile ID, we had to carefully design the experience to handle multiple MSISDNs and determine the suitable user role for them.

On the backend, user roles were still connected to MSISDNs, so we needed to create an experience that not only appeared but worked as though they were linked to T-Mobile IDs. The complexity increased for users with multiple lines attached to their T-Mobile ID, as we had to determine how to assign appropriate user roles to these users. For instance, when a user had two or more lines linked to their T-Mobile ID, we had to carefully design the experience to handle multiple MSISDNs and determine the suitable user role for them.

Use Wireframes
Use Wireframes
Use Wireframes
Use Wireframes
Use Wireframes

Web view of the different T-Mobile ID user role pages.

Our approach

Our approach

This project began with tight deadlines and a limited budget, initially intended for a UI update of one page. Upon joining the project, I realized their original plan wouldn't work. Drawing from research conducted the previous year, I had insights into which terms users preferred for different roles. Each role required its own experience based on its specific access. For instance, the main account holder had full privileges, whereas a restricted user couldn't see their role.

Due to technical constraints limiting our design options, close collaboration with the development team was crucial. I communicated daily with the dev manager through meetings, Slack, and email to ensure our design would meet user needs effectively. After careful consideration and exploring all of our options, we decided to move forward listing all the different phone numbers connected to each T-Mobile ID and updating them all to the highest user role whenever a change is made. Therefore, it acts like the T-Mobile ID is what decides the user role even though technically the user roles are still connected to the phone numbers. 

There was doubt this option was technically possible but we knew it was the best option we had so we ran with it after confirming it would work.

This project began with tight deadlines and a limited budget, initially intended for a UI update of one page. Upon joining the project, I realized their original plan wouldn't work. Drawing from research conducted the previous year, I had insights into which terms users preferred for different roles. Each role required its own experience based on its specific access. For instance, the main account holder had full privileges, whereas a restricted user couldn't see their role.

Due to technical constraints limiting our design options, close collaboration with the development team was crucial. I communicated daily with the dev manager through meetings, Slack, and email to ensure our design would meet user needs effectively. After careful consideration and exploring all of our options, we decided to move forward listing all the different phone numbers connected to each T-Mobile ID and updating them all to the highest user role whenever a change is made. Therefore, it acts like the T-Mobile ID is what decides the user role even though technically the user roles are still connected to the phone numbers. 

There was doubt this option was technically possible but we knew it was the best option we had so we ran with it after confirming it would work.

Use User Flows
Use User Flows
Use User Flows
Use User Flows
Use User Flows

Different pages from the web experience. Profile page, disable user's access, failed user role change, authorized user confirmation.

Legacy authorized users

Legacy authorized users

This section is only on some accounts that were created by a retail store in the past. It's an old system that's been replaced but hasn't been fully phased out yet. No user can edit someone's role in this section, they must call support or go to a T-Mobile store for help. Not a common occurrence but something we had to account for.

This section is only on some accounts that were created by a retail store in the past. It's an old system that's been replaced but hasn't been fully phased out yet. No user can edit someone's role in this section, they must call support or go to a T-Mobile store for help. Not a common occurrence but something we had to account for.

Disabling a user's access

Disabling a user's access

Another feature on this page is called "disable user's access to web and app" which is a feature created in case someone's phone is lost, stolen or compromised. The primary account holder can disable that person's access to their T-Mobile account on the web and app, stopping any unwanted person from getting into the account.

Of course, T-Mobile would do this for them as well, it's an added feature and in my opinion, something that creates peace of mind knowing you can quickly ensure your account is safe at a moment's notice.

Another feature on this page is called "disable user's access to web and app" which is a feature created in case someone's phone is lost, stolen or compromised. The primary account holder can disable that person's access to their T-Mobile account on the web and app, stopping any unwanted person from getting into the account.

Of course, T-Mobile would do this for them as well, it's an added feature and in my opinion, something that creates peace of mind knowing you can quickly ensure your account is safe at a moment's notice.

Use User Flows
Use User Flows
Use User Flows
Use User Flows
Use User Flows

Profile page on iOS and Android for the four different user roles.

Our success

My contract ended right at the completion of this project with T-Mobile, so I don’t have access to any results from the project. What I do know is that this project enabled T-Mobile to kickstart their push to use T-Mobile IDs across all of T-Mobile; previously, it was only for T-Mobile Digital.

T-Mobile comprises T-Mobile Digital, Retail, and Business.