How To Measure The Impact Of Features

How To Measure The Impact Of Features Measure UX & Design Impact (use the code 🎟 WithTARS, we can assess how effective features are and how well they are performing.(Large preview) Adoption rates: from low adoption (<20%) to high adoption (>60%). Illustration byAdrian Raudaschl. (Large preview) We ask users how easy it was to solve a problem after they used a feature. Illustration byAdrian Raudaschl. (Large preview) Evaluating features on a 2×2 matrix based on S/T score Illustration byAdrian Raudaschl. (Large preview) Leading vs. Lagging Measures byJeff Sauro and James R. Lewis. (But please do avoid NPS at all costs). (Large preview) A practical overview of design metrics and UX scorecards:Measuring UX: Your First Step Towards Objective Evaluationby Roman Videnov. (Large preview) Design KPIs and UX Metrics, a quick overview by yours truly. Numbers are, of course, placeholders. (Large preview) IMPACT to save 20% off today). So we design and ship a shiny new feature . How do we know if it’s working? How do we measure and track its impact? There is no shortage in UX metrics , but what if we wanted to establish a simple, repeatable , meaningful UX metric - specifically for our features? Well, let’s see how to do just that. TARS , we can assess how effective features are and how well they are performing.( Large preview ) I first heard about the TARS framework from Adrian H. Raudschl’s wonderful article on “ How To Measure Impact of Features ”. Here, Adrian highlighted how his team tracks and decides which features to focus on - and then maps them against each other in a 2×2 quadrants matrix . It turned out to be a very useful framework to visualize the impact of UX work through the lens of business metrics. Let’s see how it works. 1. Target Audience (%) We start by quantifying the target audience by exploring what percentage of a product’s users have the specific problem that a feature aims to solve. We can study existing or similar features that try to solve similar problems, and how many users engage with them. Target audience isn’t the same as feature usage though. As Adrian noted, if we know that an existing Export Button feature is used by 5% of all users, it doesn’t mean that the target audience is 5%. More users might have the problem that the export feature is trying to solve, but they can’t find it. Question we ask: “What percentage of all our product’s users have that specific problem that a new feature aims to solve?” 2. A = Adoption (%) Next, we measure how well we are “acquiring” our target audience. For that, we track how many users actually engage successfully with that feature over a specific period of time. We don’t focus on CTRs or session duration there, but rather if users meaningfully engage with it. For example, if anything signals that they found it valuable, such as sharing the export URL, the number of exported files,...

Preview: ~500 words