The prioritization flow often involves identifying issues that are visually impactful. If you can see the issue occurring, either in a session recording or in a defined line of code, you're more likely to figure out what's going on and propose and implement a solution. Fixing visually impactful issues can often make for quick wins to prevent revenue loss while your team pursues deeper, more complicated errors.
Many of Noibu's prioritization features, like resolvability, point you toward visually impactful issues. However, when examining an issue on your own, you can run through the list of Yes/No questions below to decide for yourself whether the issue is visually impactful and worth investigating. Each Yes indicates a visual impact, and therefore priority.
- Is the issue still occurring?
- If the issue is not occurring anymore, it is not considered impactful and should not be prioritized.
- Is the issue a result of a shopper click?
- If the issue results from a shopper clicking a button or link, chances are you can find a session video to see the issue in action and dig into what's happening in the session timeline.
- Does the issue have a significant amount of daily occurrences?
- The more daily occurrences, the more session videos, and the more chances to observe the issue. Also, more occurrences indicate a greater impact on potential revenue.
- Are there videos that show the shopper being blocked, or experiencing friction?
- If the shopper's path is clearly blocked, it's easy to identify how to fix their experience.
- Is the issue First Party?
- A First Party issue can be traced back to your codebase. A Third Party issue is due to a problem you cannot resolve independently. To resolve a Third Party issue, you must go through the third party company's support team.
- Is the issue reproducible?
- If you have enough information to reproduce the issue on an emulator, you can gather even more insights into the issue's cause, which may lead to a solution.
- A Stacktrace may point toward the specific line of code that's causing the issue.
- Is the issue contained to a single stage of the checkout process?
- Is the issue contained to a single browser or operating system?
An equally important aspect of the prioritization flow is Identifying Low-Priority Issues.