Getting started
Challenge
Business needs
My Role & Team
User Research
User Persona
Existing Experience
User Pain Points
Opportunity
Workflows
Concept Exploration
Cross Functional Review
Components
Style guides
Typography
Solutions
Learnings
What if your unused data didn't have to
go to waste?
What if your unused data didn't have to go to waste?
Designing a clearer Data Rollover experience that helps Lyca Mobile Australia customers understand, track and use their unused data.
Designing a clearer Data Rollover experience that helps Lyca Mobile Australia customers understand, track and use their unused data.
Disclaimer
A quick note before we begin: To respect confidentiality, some information in this case study has been simplified or removed.
This case study focuses on my work for Lyca Mobile Australia and shares the key problem, design process and solution without revealing sensitive business, customer or technical information.
A quick note before we begin: To respect confidentiality, some information in this case study has been simplified or removed.
This case study focuses on my work for Lyca Mobile Australia and shares the key problem, design process and solution without revealing sensitive business, customer or technical information.
Getting Started
Unused data shouldn't feel like wasted value.
Unused data shouldn't feel like wasted value.
Customers don't always use all the data included in their mobile plan. When that unused allowance disappears at the end of a cycle, customers can feel like they're losing something they've already paid for.
The opportunity was to give that unused data a place to go - and make it easy for customers to understand what they had accumulated.
Customers don't always use all the data included in their mobile plan. When that unused allowance disappears at the end of a cycle, customers can feel like they're losing something they've already paid for.
The opportunity was to give that unused data a place to go - and make it easy for customers to understand what they had accumulated.
Challenge
The problem wasn't just unused data. It was making the value visible.
The problem wasn't just unused data. It was making the value visible.
Data Rollover introduced a new concept into an experience customers already understood: their regular plan allowance.
The challenge was to clearly distinguish current plan data from rolled-over data, while keeping the experience simple enough to understand at a glance.
Data Rollover introduced a new concept into an experience customers already understood: their regular plan allowance.
The challenge was to clearly distinguish current plan data from rolled-over data, while keeping the experience simple enough to understand at a glance.
1
Invisible unused data
Customers had limited visibility into what happened to their unused allowance.
2
Two types of data
Plan data and rollover data needed to be clearly differentiated.
3
Expiry complexity
Rollover data could have different validity rules from the customer's regular plan.
4
Discoverability
Customers needed to understand that rollover existed and how it worked.
5
Multiple states
The experience needed to account for different balances and customer situations.
Business Needs
The experience needed to account for different balances and customer situations.
The experience needed to account for different balances and customer situations.
The goal wasn't simply to add a new Data Rollover card.
The experience needed to make rollover understandable, encourage customers to continue using Lyca Mobile, and provide enough visibility for customers to make better decisions around their data usage.
The goal wasn't simply to add a new Data Rollover card.
The experience needed to make rollover understandable, encourage customers to continue using Lyca Mobile, and provide enough visibility for customers to make better decisions around their data usage.
Goal
Make unused data useful
Turns unused data into something customers can see, understand and use.
Customer
More control over data
Gives customers clarity on what they have, when it expires and how it works.
Business
Increase plan value
Strengthen customer satisfaction, trust and loyalty by making every GB count
Experience
One clear Data Rollover Journey
A consistent and simple experience across discovery, usage, history and support
My Role & Team
Good product design is rarely a solo effort.
Good product design is rarely a
solo effort.
The Lyca Mobile Data Rollover experience was shaped through close collaboration across design, research, business, engineering, delivery, and QA.
I worked with Sandeep Das, My Manager, alongside Visakan Kanagarajan on UX research, Kunal Chettri as Business Analyst, Jithender Reddy as Project Manager and Amit Bharadhwaj as Delivery Manager.
On the engineering side, I collaborated with Narendra Prasad on Android Development and Mihir Oza on iOS Development, with Nagaraj Hittalamani leading QA.
Together, we worked through the user, business, regulatory, and technical constraints to create a registration experience that could scale across different markets.
The Lyca Mobile Data Rollover experience was shaped through close collaboration across design, research, business, engineering, delivery, and QA.
I worked with Sandeep Das, My Manager, alongside Visakan Kanagarajan on UX research, Kunal Chettri as Business Analyst, Jithender Reddy as Project Manager and Amit Bharadhwaj as Delivery Manager.
On the engineering side, I collaborated with Narendra Prasad on Android Development and Mihir Oza on iOS Development, with Nagaraj Hittalamani leading QA.
Together, we worked through the user, business, regulatory, and technical constraints to create a registration experience that could scale across different markets.
What I owned
What I owned
From understanding the problem to shaping the final experience, I owned the design across the journey.
From understanding the problem to shaping the final experience, I owned the design across the journey.
User Experience
Data Rollover Journey
User Flows
Edge Cases
Product
Business Requirement
Feature Behaviour
Rollover Scenarios
User Interface
UI Design
Components
Visual Design
User Research
Before designing the solution, I needed to understand how people actually manage their data.
Before designing the solution, I needed to understand how people actually manage their data.
I explored how customers monitor their data,
what happens when they have unused data,
what they do when they run out, and
what they would expect from a rollover experience.
The research focused on:
Current data management behaviour
Expectations around unused data
Situations where customers run out of data
Clarity around current balances
Pain points in managing multiple data states
I explored how customers monitor their data,
what happens when they have unused data,
what they do when they run out, and
what they would expect from a rollover experience.
The research focused on:
Current data management behaviour
Expectations around unused data
Situations where customers run out of data
Clarity around current balances
Pain points in managing multiple data states
User interview questions
User interview questions
Understanding current behaviour
How do you usually monitor your mobile data usage?
What do you do with unused data at the end of your billing cycle?
Have you ever run out of data before the end of a cycle? If so, how did you handle it?
Understanding user expectation
Would a Data Rollover feature be valuable to you? Why or why not?
What would you expect from a Data Rollover feature?
Understanding pain points
What frustrates you most about managing mobile data currently?
Have you ever felt unclear about your data balance or usage?
User Persona
I created the research around three different customer perspectives instead of showing only one type of user.
I created the research around three different customer perspectives instead of showing only one type of user.
Existing Experience
The existing experience answered how much data I had. Not what happened to the rest.
The existing experience answered how much data I had. Not what happened to the rest.
Customers could already track their regular plan usage, but unused data wasn't presented as a clear, actionable balance. The experience made it difficult to understand whether unused data could be carried forward, how much was available, and when it would expire.
Customers could already track their regular plan usage, but unused data wasn't presented as a clear, actionable balance. The experience made it difficult to understand whether unused data could be carried forward, how much was available, and when it would expire.
User Pain Points
The frustration wasn't simply running out of data. It was not knowing what was happening to it.
The frustration wasn't simply running out of data. It was not knowing what was happening to it.
I would not show all the individual suggestions from the interviews here. Instead, consolidate them into the common problems across the three personas.
I would not show all the individual suggestions from the interviews here. Instead, consolidate them into the common problems across the three personas.
Opportunity
What if unused data became a balance customers could actually see?
What if unused data became a balance customers could actually see?
Instead of treating unused data as something that disappears in the background, I explored how it could become a visible part of the customer's everyday usage experience.
Instead of treating unused data as something that disappears in the background, I explored how it could become a visible part of the customer's everyday usage experience.
Workflows
Rollover data isn't just saved. It has a lifecycle.
Rollover data isn't just saved. It has a lifecycle.
The experience needed to cover more than just showing a balance. Customers needed visibility into how data was rolled over, accumulated over time, used from their Data Bank, and eventually expired. I mapped these scenarios to create a clearer experience across the entire rollover lifecycle.
The experience needed to cover more than just showing a balance. Customers needed visibility into how data was rolled over, accumulated over time, used from their Data Bank, and eventually expired. I mapped these scenarios to create a clearer experience across the entire rollover lifecycle.
Concept Exploration
The hardest question was simple: how do we show two types of data without confusing people?
The hardest question was simple: how do we show two types of data without confusing people?
I explored multiple ways to represent Regular Plan Data and Data Bank balance. Each concept approached the relationship between the two balances differently - from combining them into a single visualisation to separating them into distinct states.
The challenge was to find the right balance between information density and immediate comprehension.
I explored multiple ways to represent Regular Plan Data and Data Bank balance. Each concept approached the relationship between the two balances differently - from combining them into a single visualisation to separating them into distinct states.
The challenge was to find the right balance between information density and immediate comprehension.
Cross Functional Concept Review
I didn't want the final direction to be based on design preference alone.
I didn't want the final direction to be based on design preference alone.
To evaluate which concept was easiest to understand, I shared the three directions with a cross-functional group across Product, UX, Engineering, QA, Business Analysis and Delivery.
Participants reviewed the concepts and selected the direction they believed provided the clearest understanding of Plan Data and Data Bank.
To evaluate which concept was easiest to understand, I shared the three directions with a cross-functional group across Product, UX, Engineering, QA, Business Analysis and Delivery.
Participants reviewed the concepts and selected the direction they believed provided the clearest understanding of Plan Data and Data Bank.
Conclusion
Conclusion
16 of 23 participants preferred Option 03 - 69.6% preference
16 of 23 participants preferred Option 03 - 69.6% preference
Components
A new feature needed more than a new card.
A new feature needed more than a new card.
I translated the experience into reusable components so the rollover experience could remain consistent across different customer states and screen sizes.
I translated the experience into reusable components so the rollover experience could remain consistent across different customer states and screen sizes.
Style Guides
The visual language needed to make data feel simple.
The visual language needed to make data feel simple.
I used Lyca Mobile's existing visual language as a foundation while refining hierarchy, spacing, typography, colour, and component behaviour to create a clearer and more consistent registration experience across screen sizes.
I used Lyca Mobile's existing visual language as a foundation while refining hierarchy, spacing, typography, colour, and component behaviour to create a clearer and more consistent registration experience across screen sizes.
Foundational Colours
Primary colours
P1
P2
Core colours
C1
C2
Secondary colours
S1
S2
S3
S4
Text Colours
Text colours
T1
T2
T3
T4
Core colours
B1
B2
B3
B4
B5
B6
Semantic Colours
SE1
SE2
SE3
SE4
SE5
Typography
Typography that keeps the experience clear and consistent.
Typography that keeps the experience clear and consistent.
I used GT Eesti LC Display, Lyca Mobile’s brand typeface, throughout the data rollover experience to maintain brand consistency and create a clear, cohesive visual language.
I used GT Eesti LC Display, Lyca Mobile’s brand typeface, throughout the data rollover experience to maintain brand consistency and create a clear, cohesive visual language.
GT Eesti LC Display
Ag
abcdefghijklmnopqrstuvwxyz
abcdefghijklmnopqrstuvwxyz
1234567890!@#$%^&*()
Solution
I turned unused data into something customers could see, understand and use.
I turned unused data into something customers could see, understand and use.
The redesigned Data Rollover experience gives customers a clearer view of their available data, separates rollover from their regular allowance, and provides contextual information around usage, history and expiry.
The redesigned Data Rollover experience gives customers a clearer view of their available data, separates rollover from their regular allowance, and provides contextual information around usage, history and expiry.
Learnings
Good product design isn't about showing more. It's about showing what matters at the right moment.
Good product design isn't about showing more. It's about showing what matters at the right moment.
Designing the Data Rollover experience taught me that a feature with multiple balances, expiry rules and usage conditions could easily become overwhelming. The challenge was not simply to display all the available information, but to organise it in a way that felt clear, relevant and easy to understand throughout the customer's journey.
Designing the Data Rollover experience taught me that a feature with multiple balances, expiry rules and usage conditions could easily become overwhelming. The challenge was not simply to display all the available information, but to organise it in a way that felt clear, relevant and easy to understand throughout the customer's journey.
Clarity is more important than showing everything
Clarity is more important than showing everything
Early concepts showed both Plan Data and Data Bank at the same time. While this provided more information, it also created unnecessary confusion. Simplifying what users saw helped make the experience easier to understand.
Early concepts showed both Plan Data and Data Bank at the same time. While this provided more information, it also created unnecessary confusion. Simplifying what users saw helped make the experience easier to understand.
Context should guide the experience
Context should guide the experience
The customer's needs change depending on their current data balance. Prioritising the active balance helped ensure that the most relevant information was always visible at the right time.
The customer's needs change depending on their current data balance. Prioritising the active balance helped ensure that the most relevant information was always visible at the right time.
Complex rules need simple communication
Complex rules need simple communication
Data rollover involved multiple conditions, including accumulation, usage order and expiry. Breaking these into clear states, messages and interactions made the rules easier for customers to understand.
Data rollover involved multiple conditions, including accumulation, usage order and expiry. Breaking these into clear states, messages and interactions made the rules easier for customers to understand.
Better solutions come from collaboration
Better solutions come from collaboration
Reviewing concepts with Product, Development, QA and other internal teams helped identify potential issues early and contributed to selecting a clearer direction.
Reviewing concepts with Product, Development, QA and other internal teams helped identify potential issues early and contributed to selecting a clearer direction.
“The biggest learning was simple: when a product has complex rules behind it, the customer shouldn't have to feel that complexity.”
“The biggest learning was simple: when a product has complex rules behind it, the customer shouldn't have to feel that complexity.”
Looking for the right team and
the right challenge.
I’m currently open to Senior Product Designer,
AI Product Designer, and Design Lead opportunities.
Looking for the right team and
the right challenge.
I’m currently open to Senior Product Designer,
AI Product Designer, and Design Lead opportunities.
+91 83174 84558