
Hubbl Review Order Refresh
Project completed
In house, Foxtel Group.
Role
Define brief, UI Design, Quality Control.
The Problem
The Hubbl sales flow began like many ambitious projects: a promising brief to revolutionise business models that ended up only slightly different from the old one.
The UX was crafted for a ‘pick and mix’ solution, offering access to Foxtel and third-party apps with scalable discounts, account credits, hardware purchases, and offer redemptions. It also supports subscription changes—upgrades, downgrades, cancellations, reactivations—and bundling, all within one template.
When designing the UI, scalability and consistency were priorities. Yet, less than a year after launch, frustration grew. A challenging design QA process and accumulated incremental changes without proper cleanup of the rush to launch left the team increasingly dissatisfied.
My Approach
We were nearing the end of the ‘pre work’ phase of an initiative. UX approval had stalled, with team members 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.
