TelstraPlus Multi-CAC Dashboard
A CAC is a customer account number usually created when a user signs up for a Telstra ID. Multi-CAC users have multiple Telstra+ memberships. An example of this would be a full account holder with the authority to manage accounts for other family members.
How did we do it
Hypothesis
The hypothesis suggested that a well-designed dashboard offers a clear and organised representation of key metrics and information, allowing users to make informed decisions quickly by presenting data visually.
UX design
I wanted to explore how I can improve the experience for our customers with multiple Telstra+ memberships.
I considered ways to implement the most user-friendly patterns and adapt them to mobile behaviours. I ran an ideation workshop that included the design team, product owner and others involved in the project. After consolidating workshop outcomes, I conducted a competitor and best practices analysis and created the first concepts of user journeys and proposed UI patterns.
Design critique
I introduced the concepts to the wider UX / UI team, where everyone could provide feedback, identify friction points or raise specific concerns. I then synthesised the feedback and adjusted the UX accordingly.
User testing
I created a fully functional prototype and ran a 5-person usability testing session. After synthesising the feedback, it was confirmed that we were on the right track. Most participants have indicated that these patterns were familiar to them as they have seen them in other apps. All participants were able to navigate the feature with confidence.
Visual design
Using MyTelstra’s Design System, UI concepts were created, and I ran another design critique session to ensure this work was aligned with all other features using similar UI patterns. Also, stress testing for multiple devices was conducted to address any alternative layouts required when accessibility features are activated.
Developer handoff documentation
Providing the development team with as much information as possible is one of the most critical steps in successfully delivering any feature. Once the visual design was finalised, we created the developer handoff documentation identifying the design system patterns we’ve used, spacing, fonts and accessibility information such as screen reader behaviour.