Productisation Roll-out
UX
·
Strategy
Led UX stream in major logic shift, delivering meaningful KPIs lifts · 2025-2026 · Allegro
Remove a major user pain — lengthy offer lists that were hard to browse — by rolling out the productisation project aggregating offers into products. Keeping the user-centered idea at the core while ensuring monetisation goals were met throughout the transition.
I contributed to the project in its design, prototype, testing, and delivery phases.
• Led the UX stream of this major architectural change, collaborating closely with backend, frontend, and monetisation teams.
• Co-facilitated workshops aligning product and advertising perspectives, and designed and tested solutions on the product list to improve both experience and business metrics.
• Design decisions were iterated based on quantitative metrics and qualitative insights, with multiple rounds of prototyping and validation before and after launch.
Project delivered as part of my full-time role at Allegro (internal product work).
Overall results: productization project successfully launched, improving key engagement and business metrics. Key metric uplifts (YoY):
• Product list conversion: over +2 pp
• C-index (internal customer satisfaction rate): over +2.5%
My favourite contributions:
• Co-prepared strategic product–monetisation workshops attended by senior managers.
• Proposed a concept and co-created mockups to visualise complex backend changes in the new monetisation model.
• Redesigned the add-to-cart button on the product cell, resulting in measurable metric improvements from this single focused change.
• Strategic workshops established shared design and ways-of-working principles and enabled joint prioritisation across teams.
• Workshop outcomes also contributed to a new high-level monetisation business model.
• Introduced a repeatable practice of visualising backend changes to support collaboration during large architectural transitions.
• Obsessively goal-focused and data-heavy workshops are a good way to build alignment among senior stakeholders with strong, often opposing perspectives.
• Small iterations can truly lead to big, lasting impact over time.
• Even if teams’ goals seem to conflict at first, they don’t have to stay that way.
• Backend changes can (and should) be visualised as well. Visualisation is a great tool for achieving a shared understanding of complex changes. Always. Will not accept “can’t be visualised” anymore.
• Adoption takes time, and the bigger the change, the older the product, the stronger this factor becomes in a project’s success. This project truly made me adoption-issues master 101. I always have at least three ideas at hand on how to facilitate a big change since then.
• The lag between behaviour and satisfaction is key to reading metrics right.
• Treating the product list as a workflow with multiple decision points, dependencies, and failure states rather than a single UI surface.
