Rise of a Phoenix

Rise of a Phoenix

Rise of a Phoenix

ROLE

Lead UX/UI Designer

COMPANY

Vodafone Hungary

TIMELINE

Q4 2017 – Q2 2018

Vodafone Hungary's failed webshop rollout in 2017 cratered checkout from 10% to 2% and pushed digital T-NPS below -20. Instead of a rollback or a rescue, we redesigned the stable legacy platform into a mobile-first webshop in 8 months. One month after launch checkout recovered fully and T-NPS hit an all-time high above 40.

ROLE

Lead UX/UI Designer

COMPANY

Vodafone Hungary

TIMELINE

Q4 2017 – Q2 2018

Vodafone Hungary's failed webshop rollout in 2017 cratered checkout from 10% to 2% and pushed digital T-NPS below -20. Instead of a rollback or a rescue, we redesigned the stable legacy platform into a mobile-first webshop in 8 months. One month after launch checkout recovered fully and T-NPS hit an all-time high above 40.

ROLE

Lead UX/UI Designer

COMPANY

Vodafone Hungary

TIMELINE

Q4 2017 – Q2 2018

Vodafone Hungary's failed webshop rollout in 2017 cratered checkout from 10% to 2% and pushed digital T-NPS below -20. Instead of a rollback or a rescue, we redesigned the stable legacy platform into a mobile-first webshop in 8 months. One month after launch checkout recovered fully and T-NPS hit an all-time high above 40.

THE SITUATION

Vodafone Hungary rolled out a new, Hybris-based webshop in spring 2017 under the Red Sky strategic transformation project. It launched as a quasi-MVP for new customers only, leaving the legacy system – outdated UI and UX included – to temporarily serve existing users as webshop and self-care platform. The externally designed and developed system underperformed from day one.

THE SITUATION

Vodafone Hungary rolled out a new, Hybris-based webshop in spring 2017 under the Red Sky strategic transformation project. It launched as a quasi-MVP for new customers only, leaving the legacy system – outdated UI and UX included – to temporarily serve existing users as webshop and self-care platform. The externally designed and developed system underperformed from day one.

THE SITUATION

Vodafone Hungary rolled out a new, Hybris-based webshop in spring 2017 under the Red Sky strategic transformation project. It launched as a quasi-MVP for new customers only, leaving the legacy system – outdated UI and UX included – to temporarily serve existing users as webshop and self-care platform. The externally designed and developed system underperformed from day one.

MANDATE AND TEAM GROWTH

I joined the Vodafone Hungary Digital Team as a Lead UI/UX Designer (the company’s first internal UX designer) early 2017, about the same time as the rollout. My three mandates were to:

  • establish and build an internal design team,

  • introduce modern UX & product design and bring it to maturity within the company by demonstrating its benefits and added value,

  • and get the digital product portfolio in order, from a UX and UI perspective.

By Q4 2017, and the start of project Red Phoenix, I was managing a team of five internal designers working across the two webshops, the website, and the mobile app.

MANDATE AND TEAM GROWTH

I joined the Vodafone Hungary Digital Team as a Lead UI/UX Designer (the company’s first internal UX designer) early 2017, about the same time as the rollout. My three mandates were to:

  • establish and build an internal design team,

  • introduce modern UX & product design and bring it to maturity within the company by demonstrating its benefits and added value,

  • and get the digital product portfolio in order, from a UX and UI perspective.

By Q4 2017, and the start of project Red Phoenix, I was managing a team of five internal designers working across the two webshops, the website, and the mobile app.

MANDATE AND TEAM GROWTH

I joined the Vodafone Hungary Digital Team as a Lead UI/UX Designer (the company’s first internal UX designer) early 2017, about the same time as the rollout. My three mandates were to:

  • establish and build an internal design team,

  • introduce modern UX & product design and bring it to maturity within the company by demonstrating its benefits and added value,

  • and get the digital product portfolio in order, from a UX and UI perspective.

By Q4 2017, and the start of project Red Phoenix, I was managing a team of five internal designers working across the two webshops, the website, and the mobile app.

PROBLEM AREAS

01/

Business

Checkout collapsed. Completion fell to 2% from 10% after rollout, and stayed there even through marketing campaigns.

01/

Business

Checkout collapsed. Completion fell to 2% from 10% after rollout, and stayed there even through marketing campaigns.

01/

Business

Checkout collapsed. Completion fell to 2% from 10% after rollout, and stayed there even through marketing campaigns.

02/

Usability

Journeys broke mid-flow. Feedback and heuristic reviews revealed breakdown points throughout, with error recovery seldom possible.

02/

Usability

Journeys broke mid-flow. Feedback and heuristic reviews revealed breakdown points throughout, with error recovery seldom possible.

02/

Usability

Journeys broke mid-flow. Feedback and heuristic reviews revealed breakdown points throughout, with error recovery seldom possible.

03/

Performance

Pages crawled and crashed. 40+ second load times were common, and heavy client-side processing brought frequent request errors and browser tab crashes.

03/

Performance

Pages crawled and crashed. 40+ second load times were common, and heavy client-side processing brought frequent request errors and browser tab crashes.

03/

Performance

Pages crawled and crashed. 40+ second load times were common, and heavy client-side processing brought frequent request errors and browser tab crashes.

04/

UI Design

WS2.0 was applied poorly. Hasty adaptation left interfaces inconsistent and accessibility minimal, despite the system's own principles.

04/

UI Design

WS2.0 was applied poorly. Hasty adaptation left interfaces inconsistent and accessibility minimal, despite the system's own principles.

04/

UI Design

WS2.0 was applied poorly. Hasty adaptation left interfaces inconsistent and accessibility minimal, despite the system's own principles.

05/

User Journey

Users landed in the wrong shop. Makeshift routing between the two stacks often pulled existing customers into the new messy webshop, and new ones into the legacy one they couldn't access.

05/

User Journey

Users landed in the wrong shop. Makeshift routing between the two stacks often pulled existing customers into the new messy webshop, and new ones into the legacy one they couldn't access.

05/

User Journey

Users landed in the wrong shop. Makeshift routing between the two stacks often pulled existing customers into the new messy webshop, and new ones into the legacy one they couldn't access.

06/

User Satisfaction

The problems pushed customers to other channels. Retail and the call center strained to absorb the load, as digital T-NPS sank below -20, a record low.

06/

User Satisfaction

The problems pushed customers to other channels. Retail and the call center strained to absorb the load, as digital T-NPS sank below -20, a record low.

06/

User Satisfaction

The problems pushed customers to other channels. Retail and the call center strained to absorb the load, as digital T-NPS sank below -20, a record low.

A THIRD PATH

By Q3 2017, the new webshop could not handle even the acquisition flow it was built for, and maintaining it had become a liability despite the investment behind it.

An effort, codenamed Red Phoenix, launched in late 2017 with a mission to stabilize performance, restore trust, and make the digital experience compelling enough that customers chose it over visiting a store. Stakeholder leadership was weighing two, obvious paths:

  • lose face and play it safe: roll back to the old platform and build a completely new one from scratch;

  • risk and force it: keep fixing the new webshop with larger, significant deployments.

Both meant months of impacted sales, continued damage to brand trust, and loss of existing customers – with no guarantee of results.

With the Head of Digital, after some brainstorming and a feasibility meeting, we proposed and championed a third path: redesigning the stable legacy webshop into a modern, responsive, mobile-first platform. And not just redoing the UI, but revamping journeys, improving UX, and upgrading the front-end and database management in parallel. This path

  • required fewer infrastructure changes,

  • carried less risk by working within the existing back-end,

  • promised faster deployment through already-running QA environments,

  • and altogether meant user satisfaction and sales could recover much sooner.

This is a strong example why stepping back for a fresh perspective is crucial in good product design – and also on how to avoid sunk-cost fallacy and false dilemmas.

A THIRD PATH

By Q3 2017, the new webshop could not handle even the acquisition flow it was built for, and maintaining it had become a liability despite the investment behind it.

An effort, codenamed Red Phoenix, launched in late 2017 with a mission to stabilize performance, restore trust, and make the digital experience compelling enough that customers chose it over visiting a store. Stakeholder leadership was weighing two, obvious paths:

  • lose face and play it safe: roll back to the old platform and build a completely new one from scratch;

  • risk and force it: keep fixing the new webshop with larger, significant deployments.

Both meant months of impacted sales, continued damage to brand trust, and loss of existing customers – with no guarantee of results.

With the Head of Digital, after some brainstorming and a feasibility meeting, we proposed and championed a third path: redesigning the stable legacy webshop into a modern, responsive, mobile-first platform. And not just redoing the UI, but revamping journeys, improving UX, and upgrading the front-end and database management in parallel. This path

  • required fewer infrastructure changes,

  • carried less risk by working within the existing back-end,

  • promised faster deployment through already-running QA environments,

  • and altogether meant user satisfaction and sales could recover much sooner.

This is a strong example why stepping back for a fresh perspective is crucial in good product design – and also on how to avoid sunk-cost fallacy and false dilemmas.

A THIRD PATH

By Q3 2017, the new webshop could not handle even the acquisition flow it was built for, and maintaining it had become a liability despite the investment behind it.

An effort, codenamed Red Phoenix, launched in late 2017 with a mission to stabilize performance, restore trust, and make the digital experience compelling enough that customers chose it over visiting a store. Stakeholder leadership was weighing two, obvious paths:

  • lose face and play it safe: roll back to the old platform and build a completely new one from scratch;

  • risk and force it: keep fixing the new webshop with larger, significant deployments.

Both meant months of impacted sales, continued damage to brand trust, and loss of existing customers – with no guarantee of results.

With the Head of Digital, after some brainstorming and a feasibility meeting, we proposed and championed a third path: redesigning the stable legacy webshop into a modern, responsive, mobile-first platform. And not just redoing the UI, but revamping journeys, improving UX, and upgrading the front-end and database management in parallel. This path

  • required fewer infrastructure changes,

  • carried less risk by working within the existing back-end,

  • promised faster deployment through already-running QA environments,

  • and altogether meant user satisfaction and sales could recover much sooner.

This is a strong example why stepping back for a fresh perspective is crucial in good product design – and also on how to avoid sunk-cost fallacy and false dilemmas.

CORE DESIGN OBJECTIVES

As Lead Designer, my role was to orchestrate the end‑to‑end redesign while coordinating five designers and collaborating with internal and external developers, and the Vodafone Group (UK) design team. I set two objectives to frame the work:

  • An inviting digital experience. Building clear, reassuring purchase and subscription journeys, first to win back the digitally mature users who had been pushed away, then to draw in everyone else through ease of use.

  • Mobile first. Rebuilding these desktop-first platforms with responsive, mobile-first layouts that hold up on any device, for a true omni-channel experience.

CORE DESIGN OBJECTIVES

As Lead Designer, my role was to orchestrate the end‑to‑end redesign while coordinating five designers and collaborating with internal and external developers, and the Vodafone Group (UK) design team. I set two objectives to frame the work:

  • An inviting digital experience. Building clear, reassuring purchase and subscription journeys, first to win back the digitally mature users who had been pushed away, then to draw in everyone else through ease of use.

  • Mobile first. Rebuilding these desktop-first platforms with responsive, mobile-first layouts that hold up on any device, for a true omni-channel experience.

CORE DESIGN OBJECTIVES

As Lead Designer, my role was to orchestrate the end‑to‑end redesign while coordinating five designers and collaborating with internal and external developers, and the Vodafone Group (UK) design team. I set two objectives to frame the work:

  • An inviting digital experience. Building clear, reassuring purchase and subscription journeys, first to win back the digitally mature users who had been pushed away, then to draw in everyone else through ease of use.

  • Mobile first. Rebuilding these desktop-first platforms with responsive, mobile-first layouts that hold up on any device, for a true omni-channel experience.

FUZZY RESEARCH

This project involved what I like to call 'fuzzy research': sketch a fuzzy plan with generic goals, start with a few proven methods to get the first puzzle pieces, and define next steps as findings emerge. I defined three main axes:

01/

Learning from the Mistakes

Finding where and why the Hybris webshop underperformed, mapping the legacy system's own bottlenecks, and grounding the design phase in competitor and best-practice research.

01/

Learning from the Mistakes

Finding where and why the Hybris webshop underperformed, mapping the legacy system's own bottlenecks, and grounding the design phase in competitor and best-practice research.

01/

Learning from the Mistakes

Finding where and why the Hybris webshop underperformed, mapping the legacy system's own bottlenecks, and grounding the design phase in competitor and best-practice research.

02/

A Clear Path

Revalidating the core journeys from the ground up and weaving them into a template mesh, and also collecting a nice-to-have list along the way.

02/

A Clear Path

Revalidating the core journeys from the ground up and weaving them into a template mesh, and also collecting a nice-to-have list along the way.

02/

A Clear Path

Revalidating the core journeys from the ground up and weaving them into a template mesh, and also collecting a nice-to-have list along the way.

03/

Requirements & Limitations

Mapping technical, logistical, and sales limitations against product and marketing requirements to define the space design could maneuver within, keeping in mind the swift delivery requirements.

03/

Requirements & Limitations

Mapping technical, logistical, and sales limitations against product and marketing requirements to define the space design could maneuver within, keeping in mind the swift delivery requirements.

03/

Requirements & Limitations

Mapping technical, logistical, and sales limitations against product and marketing requirements to define the space design could maneuver within, keeping in mind the swift delivery requirements.

Research in 7 weeks and on a limited budget

Workshops

4
4
4

with Product, Marketing, Development

with Product, Marketing, Development

2
2
2

Digital Team journey workshops

Digital Team journey workshops

Interviews

5
5
5

stakeholder interviews

stakeholder interviews

10
10
10

with internal & external users

with internal &
external users

Testing

72
72
72

short usability tests of our own systems

short usability tests of our own systems

Desk Research

30h
30h
30h

heuristic, competitor, and best-practice research

heuristic, competitor, and best-practice research

INSIGHTS

Research pinpointed two areas in severe need of a usability overhaul: the bundle configuration, and the checkout flow. Two core issues were behind most problem areas:

01/

Improper Information Hierarchy

Important information was technically available but buried in long forms and by unclear sequencing, leading to cognitive overload. Information hierarchy was also deeply inconsistent (minor details were prominent while essential ones, like phone plan details or device deposit options, were hidden or vague)

01/

Improper Information Hierarchy

Important information was technically available but buried in long forms and by unclear sequencing, leading to cognitive overload. Information hierarchy was also deeply inconsistent (minor details were prominent while essential ones, like phone plan details or device deposit options, were hidden or vague)

01/

Improper Information Hierarchy

Important information was technically available but buried in long forms and by unclear sequencing, leading to cognitive overload. Information hierarchy was also deeply inconsistent (minor details were prominent while essential ones, like phone plan details or device deposit options, were hidden or vague)

02/

Fragmented Interaction Patterns

Interaction types were mixed up, non-standardized, and violated Jakob’s law. An inconsistent UI also added to the problems: absence of correct visual hierarchy and structure, confounding color usage, lack of proper affordances and interaction cues, etc.

02/

Fragmented Interaction Patterns

Interaction types were mixed up, non-standardized, and violated Jakob’s law. An inconsistent UI also added to the problems: absence of correct visual hierarchy and structure, confounding color usage, lack of proper affordances and interaction cues, etc.

02/

Fragmented Interaction Patterns

Interaction types were mixed up, non-standardized, and violated Jakob’s law. An inconsistent UI also added to the problems: absence of correct visual hierarchy and structure, confounding color usage, lack of proper affordances and interaction cues, etc.

Design Direction

These findings led to two clear conclusions: we need to start with a clean slate, discarding almost all previous patterns; and we need to focus on creating

  • a simplified bundle configuration paired with

  • an adaptive checkout.

Adaptivity was critical given roughly two dozen distinct checkout variants depending on bundle details, product type, delivery method, and payment configuration. Our bottom-up journey map served as a blueprint: we defined the shortest simple journey, and represented the additional steps required by the more complex cases as side-loops.

Some edge cases such as fleet renewal purchases were set aside for later implementation, and were to be hidden temporarily from the front-end at (re)launch.

The Extra Mile

One nice-to-have finding also made it into scope through my push: existing customers renewing plans often felt lost and uncertain. Using testimonials and internal metrics, I convinced the stakeholders that a dedicated supporting feature here would deliver significant added value, not just a better user experience.

DESIGN WORK

Rebuilt Flows

The team reshaped bundle configuration and checkout into shorter, subtask-oriented, step‑by‑step flows with an accordion structure that also made modularity possible. User validation tests confirmed it: clearer hierarchy, continuous feedback, and a visible sense of progress. The new structure also allowed the market team to change available options on the fly, adapting them to currently available logistical capabilities.

One Surface

The new webshop and the digital self-care received a uniform UI based on consolidated UX and interaction patterns, and were seamlessly meshed based on the user’s progress in their journeys. Two more connections closed the loop:

  • the mobile app reached the webshop through webviews for basic purchases

  • flows directed users towards physical stores where genuinely necessary, keeping processes fluent and truly omni-channel

Single Source of Truth

Across the board, all visual and interaction patterns were aligned with Vodafone’s WS2.0 design system and documented in a shared design reference synced in Confluence, Sketch, and Zeplin. This enabled designers, and internal and contractor developers to work consistently from an up-to-date single source of truth.

Team Growth

Personal development within my team was also important. Work was not automatically allocated to the designer most experienced in specific areas: tasks were also assigned with individual growth goals in mind, supported by extra mentoring, joint working sessions, and tight handovers to keep quality high under very ambitious timelines.

BUSINESS WINS & USABILITY GAINS

Performance

Technological success was clear right after the launch in spring 2018. Thanks to streamlined data transfer processes, error rates and page load times dropped, the latter still to above ideal but well within the acceptable range for a portal this complex. Clear UX and information hierarchy meant that even when errors presented themselves, it was much easier for users to recover from them.

Before

After

Page load time

40s+
40s+
40s+
7s ±2
7s ±2
7s ±2

Browser-side errors

Consistent
Consistent
Consistent
Negligible
Negligible
Negligible

Business

These changes turned the webshop from a painful, desktop‑bound funnel into a mobile‑first experience that many customers were finally comfortable using. Customer care started steering existing users towards the new digital self-care for regular tasks, its usage numbers increased steadily. Digital customer satisfaction reached an all-time high and continued growing, landing Hungary in the top 3 among all Vodafone markets.

Before

After

Checkout completion rate

around 2%
around 2%
around 2%
10% in 4 weeks
10% in 4 weeks
10% in 4 weeks

Digital T-NPS

Digital T-NPS

Digital T-NPS

below -20
below -20
below -20
40+ in 6 weeks
40+ in 6 weeks
40+ in 6 weeks

The Longer Arc

Beyond the numbers, Red Phoenix was a significant organizational shift forward, one of my main long-term mandates at Vodafone. It repositioned digital product design from a UI team that 'puts buttons and forms on pages' into a partner shaping the entire digital journey. The shift showed up perceivably:

  • it led to our earlier involvement in new initiatives, and stronger collaboration with IT and business;

  • it opened the door to expand UX research, service design, design-system work, and the team itself over the following years;

  • the Digital Team's way of working served as a de facto pilot for the company's comprehensive Agile transformation.

Let's untangle
Let's untangle
Let's untangle

something.

Copy component

Copied

HELLO@DENESHETENYI.COM

Made in Budapest