This is an excerpt from the Eliminate UX Debt ebook, written by Jack Moffett, and originally published on UXPin.com.
Read Part 1.
Strategies for Spotting UX Debt
Knowing the source of UX debt is an important first step — and you don’t need to schedule a special meeting or phase of the project to begin identifying issues. It’s something you can accomplish in parallel with your normal activities.
To vigilantly detect, isolate, and track UX debt from so many sources, here are a few practices and tips that I highly encourage.
Create and Validate a UX Debt Inventory
Whether you’re at the receiving end of an incoming product acquisition or coming into the team as a new hire, corralling UX debt starts with discovering what you’re up against. And that means conducting an inventory.
Let me walk you through the process.
First, sit down and use the product. You want to do this yourself to highlight anything you find unintuitive or confusing. Keep notes as you go, or ask someone to write down your comments as you use the product — then switch places.
Another collaboration option entails using a spreadsheet (like this one) in your team’s cloud folder while evaluating the heuristics together. As the creators, Susan Rector and Kim Dunwoody suggest, review the system based on criteria in the following categories:
- Findability
- Accessibility
- Clarity of Communication
- Usefulness
- Credibility
- Learnability
- Overall Aesthetics
- Persuasive Design
You can create a solid snapshot of UX gaps by involving the whole team. Be sure to block out a manageable timespan (e.g., 1–2 months); completing the evaluation will definitely take more than a week.
Remember that while this exercise is highly informative, at the end of the day, you are not the intended user.
Now that you’ve conducted a UX debt inventory, it’s time to validate your findings by observing and talking with actual users and subject matter experts (read more on that in Rian van der Merwe’s free guide Practical Enterprise User Research).
This will help you better prioritize the work with product managers for the payback sprints or the backlog.
Practice Peripheral Awareness
Anytime you interact with the product, continually scan for issues that may have escaped notice. Do this in your peripheral awareness, meaning focus on the task at hand, but keep your sensors on in the background, just in case something catches your attention.
Also, be ready to jot down notes whenever you observe someone interacting with the product. Then, enter them into your issue tracker as soon as possible (before you forget the details left out of your notes).
You should also note any bugs — both functional ones and any little details that seem out of whack. Be sure to enter them in your tracking system (like JIRA or Desk) and classify them as UX issues. Classification is important, as it enables you to find them again later, prioritize them, and get them into the schedule to be fixed.
Be Aware of Your Blind Spots
Outside of the product, think about what design practices could create debt.
My team faces a situation that could easily create UX debt. We’re distributed, so we facilitate our critiques online.
In this format, we’re generally only looking at one screen at a time. I happened to look at two screens side-by-side and noticed slightly different formatting being used to represent the same type of information. It was easily noticed when comparing the two, but quite invisible when viewing them in sequence.
If we were colocated, we would all sit in the same room for critiques, and we would have screens printed and stuck on the walls. We would regularly make cross-comparisons. Being aware of this, I can now address the situation and hopefully avoid some unintentional UX debt.
Schedule Regular Time With Users
In his article Fast Path to a Great UX — Increased Exposure Hours, Jared Spool explains that the more time your team spends with users, the better your end product. He also says that companies that intentionally include everyone — not just the UX team, but developers, managers, etc. — have better results.
When everyone sees users struggling with the product first-hand, people argue less about what needs to be done. UX debt is the responsibility and concern of everyone working on the product. This even extends to your customer.
Observing your users is also the most effective way to identify UX debt. Instead of only conducting user research in a frontloaded Sprint 0, consider spreading out some of those user exposure hours across all your sprints.
For example, even just 2–3 hours of user interviews and/or usability testing every 3 weeks can help the entire team identify and prioritize critical gaps in the product.
Conclusion
Once you’ve inventoried all of your UX debt, you may feel a bit overwhelmed. “How in the world are we going to get rid of all this debt?!” This is a perfectly normal reaction. It won’t seem nearly as bad once you’ve planned an approach to deal with it.
Don’t panic. Prioritize.
Addressing UX Debt
You know you have debt. You’ve identified it. You’ve classified it. Now, what are you going to do about it?
If you are able to walk through your debt inventory and begin penciling in solutions and rough order of magnitude estimates, chances are your debt is manageable.
That doesn’t mean you immediately know all the answers or will have it all fixed by the next release. If you can create a plan that doesn’t give product management a heart attack, you’ll eventually be able to eliminate your debt.
Roll up your sleeves. We can do this.
Step 1: Prioritization
Your debt must be prioritized so that it can be addressed in phases.
1. Severity & Impact
How big is the issue? Is it keeping users from doing their work? Is it creating a safety or security risk? Is it causing a potential customer to turn around and look to a competitor’s product?
These are all relatively severe effects that would suggest the issue is a high priority.
But don’t just consider the negatives. How big improvement will the user see? Will the improvement save hours of time in the course of a month? Will it reduce errors? If so, it may be worthy of high prioritization, even if it isn’t currently considered to be a big problem.
If you have a lot of products, you may consider employing a UX Maturity Model as the basis for prioritization.
2. Estimated Time to Address
How long is it going to take to fix?
If all you have to do is tweak the CSS, you might slip it into the next build. On the other hand, if it’s going to require a significant amount of development or will have to be thoroughly regression tested, it may make sense to hold off until it can be resolved with other issues requiring similar treatment.
3. Responsible Party
Who will be tasked with addressing the issue?
If it falls primarily on the UX team, and they currently have a light workload, it may be given a high priority. If it requires the attention of a specific developer who is already assigned to other high-priority work, then it will have to wait.
Step 2: Schedule
After prioritizing your debt, the next step is to work with product management to get it into your release schedule.
Agile is so popular these days that it seems like any process that isn’t Agile is labeled “waterfall.” I find that to be a bit dismissive. There are degrees of being Agile, and you can have an effective, iterative process that doesn’t involve stories, scrums, and sprints.
For our purposes, however, I’ll address all non-Agile processes at once. Then I’ll make suggestions for Agile teams.
1. Not Agile
Your work is likely planned based on a release cycle. Your organization decides what will go into the next release based on criteria such as how long the development effort will be; how badly a feature is needed by customers; what will sell; what bugs exist and how bad they are; and so forth.
I recommend handling UX debt issues as bugs. The real benefit of this approach is that debt items can be entered and tracked using the same tools and business processes as bugs. This will ensure that they get reviewed and treated equally. A representative from the UX team on the issue review board should prioritize items, ensuring that usability issues get the full weight they deserve.
Ideally, a representative from the UX team will also work closely with product management when releases are scheduled.
When a particular part of the application is being scheduled for work, check it for UX debt. Would it add much effort to address the debt at the same time? Often, there will be savings simply because the code is already being updated by developers. Even if it’s a low-priority item, take advantage of the opportunity to pay down some debt.
2. Agile
A company that employs a healthy Agile process shouldn’t have any problem prioritizing debt with other types of work, assigning it story points, and fitting it into sprints.
Find the rhythm
In my own experience, however, Agile has been embraced as a way to get more work done faster, rather than as a method of iterative improvement.
In such situations, you may have a harder time scheduling UX debt because (as management sees it) there’s not enough time to fit in everything they aim to wrap up, so there certainly isn’t time for all those trivial corrections you’re asking for.
If you find yourself in such an environment, your goal should be to find a rhythm for addressing debt.
Propose a certain number of story points per sprint (or every other sprint). Or, perhaps a sprint could be devoted to addressing debt at some regular interval (payback sprint). This should be done at least until the backlog of historic debt — your debt inventory — has been handled. Then it should become easier to keep up with new debt that crops up without that regular schedule.
Try a “Cheese Day”
For even tighter schedules, consider holding a Cheese Day to knock out as much debt as possible. Management is almost always receptive to a one-day workshop every 60 days where you knock many items off the debt list.
The following procedure suggested by Roy Man is both realistic and effective:
1. About 2–4 weeks before Cheese Day, create the project in your app of choice (Asana, Trello, Basecamp, etc) and encourage everyone from customer support to developers and designers to briefly describe product annoyances.
2. Prioritize the cheese list based on the advice in the below chart. Separate the “Quick Wins” from the “Nice-to-Haves”.
3. Schedule 6–8 hours for the Cheese Day, inform everyone of the date, then dive right into the “Quick Wins”. Everyone will feel productive, and you’ll have progress to show management at the end.
Conclusion
Most importantly, we address UX debt through collaboration.
UX debt should be understood as the responsibility of the entire organization — not just the UX group. It takes a good working relationship with your entire team to ensure that UX debt is given the attention it deserves.
Of course, the best way to eliminate UX debt is avoiding it in the first place. In the next chapter, we’ll explain some proactive tactics for minimizing UX debt.
