Change plans.
With confidence.
A focused redesign connecting everyday account management with clearer plan comparison, explicit billing consequences and deliberate confirmation.
Interface audit / Information architecture / UX writing / UI design
01 / The challenge
Information.
Without a clear path.
The supplied Ooredoo screens contain useful account information, commercial offers and detailed plan benefits. The challenge is how those elements work together.
On Home, overlapping usage cards compete with promotional modules. Plan management appears near the bottom of a long page, separated from the account information that might prompt a change.
Within Change Plan, customers inspect detailed cards one at a time. Comparing options requires remembering prices and allowances. The visible “Change Plan” action does not establish whether the next step reviews the choice or commits to it.
How can customers understand their current situation, evaluate another plan and recognize the consequences before committing?
02 / Evidence & priorities
Prioritize decision risk.
I audited hierarchy, discoverability, comparison, action language and feedback in the supplied screens. These observations informed hypotheses; they do not establish abandonment, accidental changes or support demand.
A provisional customer scenario
A postpaid customer checks usage and considers a plan for changing household needs. This scenario guides the journey; it is not a persona validated through interviews.
Three priority decisions
Make plan management discoverable beside the current plan. Reduce recall during comparison. Separate review from authorization. Account hierarchy and benefit scanning support those decisions.
Preserve the product context
Retain Ooredoo red, existing navigation, service categories and commercial offers. Refine the existing experience rather than introduce a new brand or navigation model.
- Understand account
- Explore plans
- Inspect details
- Review consequences
- Confirm
- Receive feedback
03 / Account clarity
Status before discovery.
Usage categories appear in parallel cards with remaining amounts and total allowances. An update label gives context to the displayed information. Bill and plan cards provide distinct actions.
“Manage plan” sits beside the current plan. Offers, rewards, recharge and shopping remain available after the account tasks, preserving commercial discovery.
The tradeoff
Parallel cards expose several balances together but limit room for labels. Small screens and large text settings need validation. Ring proportions must match the displayed balances.
04 / Plan discovery
Compare with less recall.
A vertical list exposes multiple alternatives together. Each summary emphasizes monthly price, included lines and essential allowances, with access to detailed benefits. The current plan remains a reference point.
Details separate main-line allowances, shared benefits, secondary-line options and entertainment choices. In the illustrated scenario, the current and proposed price sit together.
A list is a starting point
This reduces switching between carousel cards, but does not offer complete side-by-side comparison. Test a comparison view if people still struggle to distinguish similar plans.
Source-design limitations: the list repeats “Individual Plans” on both tabs and uses an unexplained “Recommended” badge. These are identified for correction; recommendation logic is not established.
05 / Review & confirm
Make the cost explicit.
The review screen brings the current and proposed plans, monthly fees, price difference, proposed effective date and eligibility into one decision summary.
In this scenario, QR 140 becomes QR 500: an additional QR 360 per month. Displaying the difference removes the need to calculate it mentally.
“Your current plan remains unchanged until you confirm” explains the boundary between evaluation and commitment. Only the final action says “Confirm plan change.”
Rules need verification
Prices are supplied scenario content, not current offers. Eligibility and next-billing-cycle activation are proposed assumptions requiring verified product and billing rules.
06 / Recovery
Close the loop.
Explain the state.
The success concept confirms the change and explains the proposed activation timing and confirmation message. The failure concept states that the current plan remains unchanged and provides access to support.
That reassurance addresses the key uncertainty after a failed request: did my account change? It must reflect a verified transaction state. An uncertain server response needs reconciliation rather than a false claim that nothing changed.
Success and failure are demonstrated. Loading, ineligible plans, interrupted requests and ambiguous responses remain additional states to specify.
07 / Product tradeoffs
Design beyond the happy path.
Selection and recommendation
Plan selection needs an explicit selected state. Family-line configuration and entertainment choices need rules, limits and completion feedback. A recommendation needs an explainable basis, such as stated household needs.
Consistency across the journey
The supplied Home uses “Shahry Voice,” while the change flow uses “Shahry+ Go.” The selected line and current plan must be reconciled. Copy such as “2 MORE Benefits” and “please Choose 2” needs consistent language.
Accessibility and localization
Verify contrast, text scaling, touch targets, focus order and screen-reader descriptions. Test English and Arabic layouts with real content and right-to-left behavior. Visual polish alone is not evidence of accessibility.
Engineering boundaries
Confirm billing dates, additional charges, restrictions and eligibility with product and engineering. Success and failure overlays should retain the relevant underlying screen context.
08 / Validation
Test understanding.
Then measure impact.
The next step would be a usability study with 5–7 current postpaid customers. Ask participants to find plan management, compare options, identify the monthly increase, explain activation timing and recover from a simulated failure.
Observe completion, incorrect interpretations, hesitation and requests for help. Check whether participants distinguish browsing, reviewing and confirming.
If implemented, instrument entry into plan management, selection and review progression, confirmed changes and related support requests. Establish a baseline before claiming improvement.
09 / Outcome
A clearer decision.
An honest outcome.
The result is a proposed journey connecting account awareness, plan evaluation, consequence review and transaction feedback. Its strongest contribution is an explicit review boundary: understand what changes before authorizing it.
The work demonstrates interface analysis, prioritization, flow design and UI execution. Production implementation, user testing and business outcomes are not established by the supplied material.
AI supported synthesis, critique and production exploration. Final prioritization and responsibility for design decisions remained mine.
Independent redesign concept based on supplied Ooredoo app screens. Presented for design analysis; no affiliation, endorsement or production launch is claimed. Original product and brand assets belong to their respective owners.
The first gesture
Have a good challenge?Let’s talk.