The TARS framework gives product teams a four-part metric for evaluating feature impact: Target Audience, Adoption, Retention, and Satisfaction. Introduced by Adrian H. Raudschl and detailed in a Smashing Magazine breakdown, TARS replaces vague success signals like CTR and session duration with specific, repeatable percentages. The core output is an S/T score, Satisfied Users divided by Target Users, which lets teams plot every feature on a 2x2 matrix and make prioritization decisions with actual data.
Each component has teeth. Target Audience asks what percentage of all users have the problem a feature solves, not just how many clicked it. Adoption measures meaningful engagement, think exported files or shared URLs, not mere visits. A retention rate above 50% signals high strategic importance. Below 20% flags a feature as low priority. Satisfaction uses CES, but only surveys retained users, which filters out noise and surfaces hidden friction that retention numbers alone miss. The interaction between these four numbers is where the real argument lives in the full article.
The piece also makes a pointed case against conversion rate as a UX metric, citing Fabian Lenz's observation that high conversion can coexist with bad UX when brand power, urgency tactics, or lack of alternatives drive behavior. That argument reframes what UX teams should be accountable for and why. If your team is still reporting to a conversion dashboard and calling it UX measurement, this article is a direct challenge to that practice.
[READ ORIGINAL →]