
Hubbl Review Order Refresh
Project completed
In house, Foxtel Group.
Role
Define brief, UI Design, Quality Control.
Outcome
Activation rate grew 3% over 2 months (to date)
Next Steps
I have recommended (and hope to get the chance to) further refine the way we apply offers to existing subscriptions.
There is also work to be done around our calculation of subtotal and what values are surfaced to the customer as opposed to the values used in the back end to support financial reporting.
The Problem
When designing the old review order experience, scalability and consistency were priorities. Yet, less than a year after launch, frustration had grown with our implementation.
A challenging design QA process and incremental changes to the UI without resolving existing build issues added to concerns for scannability.
Although the initial design had been through user testing, CX were getting feedback that customers had confusion around their charges.
My Approach
We were nearing the end of the ‘pre work’ phase of a planned initiative. UX approval had stalled and team members were struggling to focus beyond the review order page to provide feedback on the user flows. As project management was eager to maintain the timeline, I volunteered to explore solutions that were:
Low cost;
Required minimal or no back-end changes;
Could be delivered within the initiative timeline.
I began by simplifying the problematic screen from the UX scenario. I stripped away all extraneous elements, leaving only the essential information needed to understand the transaction taking place.


At this point, I realised we had the fundamentals of a point of sale receipt. I decided to lean into that format and scheduled a feedback session to review an updated wireframe with a first pass at the UI.
The review with the Product Manager and Head of Product went extremely well, receiving overwhelmingly positive feedback. Following this success, I compiled a comprehensive pack for our e-commerce team and director, then expanded the template variants and arranged a meeting with Legal.
Legal approval came through in 15 minutes—an unprecedented turnaround—allowing me to immediately begin producing dev-ready boards with detailed notes. I then ran a technical consultation session and conducted a deep dive with the Business Analyst to help him craft thorough user stories for development.
