Last CallLast Call Pool

Design Stage

Doświadczenie na minusie. Jak skutecznie redukować dług UX

September 18, 2025 12:35 PM

Power Talk

🇵🇱 Polish

Wisła

About

Dług UX to podstępny wróg. A jego sprzymierzeńcem jest pogoń za jak najszybszym wprowadzaniem nowych rozwiązań w Twoim produkcie, która prowadzi do pomijania drobnych niedoskonałości, a ich poprawę często przesuwa się na „wieczne potem”.

Zaczyna się od drobnych błędów, które początkowo nieznacznie wpływają na doświadczenie użytkownika. Nadal więc priorytetem są nowe funkcje, dające większą wartość biznesową. Jednak lista usterek rośnie, aż w końcu produkt przestaje dawać wartość użytkownikom, a każda interakcja z nim staje się irytująca.

Niezależnie od tego, czy Twój produkt już tonie w długu UX, czy na razie masz go pod kontrolą – ta prezentacja jest dla Ciebie. Wyjaśnię w niej, czym jest dług UX, jak powstaje i jakie niesie konsekwencje. Pokażę też sprawdzone zarządzania długiem UX i metody redukcji długu i przeciwdziałania mu na przykładach z mojej praktyki.

Talk by

Photo of Anna Jozanis, UX Design & Product Strategy Expert

UX Design & Product Strategy Expert at Independent

Watch the full talk

Watch this WaysConf session, then continue with related talks or explore the current programme.

Explore the 2026 agenda More WaysConf recordings

From the recording

Talk in brief

In her WaysConf 2025 presentation, UX Design & Product Strategy Expert Anna Jozanis outlines a structured, strategic approach to identifying, documenting, and systematically reducing UX debt. Drawing on her experience at Allegro and G2A, Jozanis defines UX debt as the accumulation of minor design flaws, usability issues, and UI inconsistencies that degrade user experience and increase operational costs over time. Rather than treating debt reduction as a one-off campaign, she advocates for a continuous, five-step operational cycle: identification, documentation, communication, reduction, and monitoring. By establishing a clear numerical metric (the sum of severity weights of all active bugs) and integrating tasks directly into existing product workflows using familiar tools like Jira, organizations can align design, product, and engineering teams. Ultimately, this systematic approach transforms the organizational mindset, fostering a highly customer-centric culture.

Key takeaways

01
Define UX Debt Numerically
To effectively manage and reduce UX debt, organizations must establish a clear, quantifiable metric, such as the sum of severity weights assigned to all identified usability issues. This numerical indicator provides a transparent benchmark that becomes more favorable as the score decreases toward zero.
Watch from 5:59
02
Leverage External Audits for Executive Buy-In
While internal reviews are valuable, commissioning external expert usability audits can be highly persuasive for C-level executives, helping to secure the necessary budget and strategic priority for debt reduction. These external evaluations carry authoritative weight that can accelerate organizational decision-making.
Watch from 9:46
03
Integrate Debt Tasks into Existing Tools
Rather than forcing teams to adopt new software, document UX debt in widely used project management tools like Jira to lower the barrier to entry for product and engineering teams. Assigning these tasks directly to product owners distributes responsibility and ensures usability fixes are treated as standard product backlog items.
Watch from 15:09
04
Secure High-Level Allies and Communicate Persistently
Successful UX debt reduction requires continuous communication and strong advocacy from executive leadership, such as a Chief Product Officer, to shift team priorities. Designers must act as persistent advocates, regularly reminding product teams of outstanding issues during quarterly planning and reviews.
Watch from 16:35
05
Verify Fixes Before Closing Tasks
The reduction process does not end when a developer deploys a fix; a dedicated UX verification step is essential to confirm the usability issue has been successfully resolved. Only after this design review is complete should the task be closed and its severity weight subtracted from the overall debt metric.
Watch from 21:21

Video chapters

1:03Understanding UX Debt and Its Causes
Anna Jozanis defines UX debt as the accumulation of minor usability flaws and explains how business pressure, rapid MVP releases, and ignored design systems cause it to grow.
4:11A Strategic Framework for Debt Reduction
The speaker introduces her three core strategic assumptions and the five-step process of identification, documentation, communication, reduction, and monitoring used at G2A.
7:47Methods for Identifying Usability Flaws
This chapter covers practical techniques for uncovering UX debt, including comprehensive usability testing, external expert audits, session recording analysis, and customer support insights.
12:31Documenting and Structuring the Backlog in Jira
Jozanis explains how to organize UX debt in Jira by creating dedicated tasks, categorizing them by platform, assigning severity weights, and sharing ownership with product managers.
15:45The Power of Persistent Communication
The speaker emphasizes the necessity of securing executive allies and maintaining constant, proactive communication across the organization to keep debt reduction on the roadmap.
20:31Integrating Debt Reduction into Product Sprints
This section details how to embed usability fixes into quarterly planning, apply prioritization frameworks like impact versus effort, and perform mandatory UX verifications.
24:15Monitoring Progress and Benchmarking Success
The final chapter highlights how to use Jira dashboards and external usability benchmarks to track progress, motivate teams, and demonstrate business value to C-level executives.

Read edited transcript highlights

These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.

The True Cost of UX Debt

While a single minor usability flaw or UI inconsistency might seem insignificant on its own, the cumulative effect of unresolved issues severely damages the overall user experience. Beyond user frustration and direct business losses, a high volume of UX debt introduces a heavy operational burden. It makes designing future product changes increasingly complex and significantly slows down the technical implementation of new features.

Watch from 1:31

Quantifying UX Debt with a Simple Metric

To effectively monitor and manage UX debt, organizations must be able to measure it. Borrowing a successful practice from Allegro, G2A established a single numerical metric calculated as the sum of the severity weights of all identified bugs. Each bug is rated on a scale of one to three based on its impact. A lower total score indicates a healthier product, providing a clear, transparent target for product teams to work toward.

Watch from 5:49

The Strategic Value of External Usability Audits

Conducting expert usability audits is a highly effective way to identify hidden design flaws. While internal reviews are useful, external audits from specialized agencies carry a unique strategic advantage. The formal stamp of approval from an outside authority often proves far more persuasive to C-level executives, helping to justify the initiative and accelerate critical decision-making regarding resource allocation.

Watch from 9:46

Fostering Shared Ownership in Jira

Documenting UX debt in a dedicated Jira project lowers the barrier to entry for product and engineering teams. By categorizing bugs with tags like desktop or mobile and assigning them directly to the product owners responsible for those specific areas, the UX team successfully distributes accountability. This ensures that resolving usability issues is no longer viewed solely as a design responsibility, but as a shared product goal.

Watch from 14:01

The Role of Executive Sponsorship and Constant Advocacy

Securing a high-level ally, such as the Chief Product Officer, is often the deciding factor in whether a UX debt initiative succeeds or fails. At G2A, the CPO's clear expectation that teams dedicate a portion of their capacity to debt reduction was crucial. However, designers must also maintain constant, persistent communication across all planning and review sessions to prevent the initiative from losing momentum.

Watch from 16:35

Prioritizing Usability Fixes and Verifying Results

Because teams cannot fix every usability bug at once, they must prioritize tasks using frameworks like impact versus effort, alignment with team goals, and piggybacking on existing feature developments. Crucially, a task should never be closed in the backlog immediately after deployment; it must undergo a formal UX verification to ensure the fix actually resolved the user problem.

Watch from 22:02

Explore WaysConf 2026

View the agenda

Get tickets