How are you auditing tagged features?

How are you managing and auditing your tagged features when something changes in your product UI?

Scenario: We had a number of tagged elements where the CSS recently had a "/" removed from the href URL which meant that every single tagged element needed to be audited, tested and edited. This was recognized in passing, as opposed to through some sort of alert. 



1 comment
  • Hey Andrina, 

    Here are a few ideas that could help get you started with your feature audit:

    • Look for outliers, Sort by # of clicks, and review the features with 0 clicks / extremely high number of clicks first.
    • If there's a specific area of the application that is extremely important/valuable/changed recently, focus on the pages/features for that area first
    • Make sure your page rules are accurate before you look at feature rules




Please sign in to leave a comment.

Didn't find what you were looking for?

New post