About:
Every month, HR teams across Czechia order meal vouchers, cards and credit for their employees through Pluxee. When I started in 2022, they were still doing it in a system from the Sodexo era. I have been redesigning how they order ever since, as the only designer on the product.
Category:
UX/UI design
Client:
Pluxee
Year:
2022 – present
Location:
Prague, Czech Republic
Design framework:
Design thinking
Tools:
Figma, Pluxee Design System, Maze, Condens, Google Analytics 4, Hotjar
Research
Define
Prototype
Test
The problem:
Ordering ran on mojesodexo.cz, later order.pluxee.cz, with the same structure. Login by contract number, a separate PDF manual for every order type (11 pages just for vouchers in envelopes), bulk orders as a hand-written CSV with numeric product codes, and internal acronyms like GPC, APC and FPC in the main menu. One door for every client, whatever their size or role.
Goal:
Let HR order credit, cards and vouchers on their own, quickly and without errors, in one client portal built on the Pluxee design system, and measure whether it actually works.
My role:
Sole product designer since 2022, working with product manager Petra Tothová, business analyst Vilém Suchý and the Pluxee design system team in Paris. Discovery, personas, research, delivery in Figma, coded prototypes, sprint testing and analytics reporting.
Methods:
•
Archive research
•
Personas
•
Moderated usability testing
•
Unmoderated testing (Maze)
•
Coded prototyping
•
Analytics review (GA4, Hotjar)
•
Measurement plan
Empathize
Before changing anything, I wanted to see the system the way HR saw it every month.
/01
A system that outlived its brand
Ordering ran on mojesodexo.cz, archived since 2010, and later on order.pluxee.cz with the same structure. In 2025 it still ran as version 5.4.8. Drag the line to compare it with the new portal.
/02
Ordering needed a manual
Five PDF guides, 51 pages in total. A bulk order meant writing a semicolon-separated file by hand, with numeric product codes and one row per envelope.
Define
The old system had one door for everyone. The new one needed to know who is coming in, and why.
/01
Five personas
I split users by role and company size. Each persona got its own route: onboarding for new clients, an invitation and upgrade for migrating ones, ordering at scale for HR teams and an internal login for Pluxee staff.
/02
Start from the employee, not the product
HR doesn't think in product codes. They think “these three people need a card”. So ordering now starts from the employee list, with card status and credit in every row.
Prototype
I design in Figma on the Pluxee design system and deliver there. Bigger interactions I also build as coded prototypes and run locally, so I can test them before handoff. Like this one.
/01
The ordering system, clickable
Try it: set credit, order a card for an employee without one, review delivery and send the order. Built from the Figma ordering system with the real states and steps.
/02
One design system for every module
Everything is built from the Pluxee Figma library maintained by the design team in Paris: the same tokens, buttons, status chips, inputs, tabs, steppers and tables across ordering, employees and orders. Click the components.
/03
A homepage that starts with action
Quick actions, blocked orders, card parcels to collect and unpaid orders with a direct Pay button, all on the first screen.
Test
Every bigger step goes in front of real users before it ships.
/01
Two studies, 22 respondents
A moderated test of onboarding and first login, and an unmoderated Maze test of the import centre, which HR used to leave to Pluxee's internal digital team. The goal: HR finishes the import alone, fast and without errors.
Measure
Once the client portal was live, I turned Google Analytics 4 into a UX report for product management.
/01
What the data says
A work tool with a monthly rhythm. Users keep coming back to check orders and spend the most effort on employees, while success itself was not measured at all.
/02
From data to concepts
Each signal became a hypothesis, a test plan and a metric. Alongside the concepts I wrote the event specification for IT, page titles for WCAG 2.4.2 and a monthly UX scorecard.
Outcome
An ongoing project: live, measured and tuned sprint by sprint.
/01
Then and now
The ordering process is up to 20% faster, the new client portal has 2,590 active users a month, and clients are still being migrated from the Sodexo-era system. Next come the quick wins, then order status and bulk employee management, each tested with HR users and measured before and after release.
/02
How I work
Ongoing discovery instead of a one-off phase. Testing every sprint, success metrics from GA4 and Hotjar reported back to product management, and bugs removed release by release.
© More works
(WDX®)
digital design
© help centre
(WDX)
clarification
Let’s talk