What is the feature adoption rate formula?

Feature adoption rate = (number of users who used the feature / total active users in the same period) x 100. Pick a single time window (usually a week or a month), count the distinct active users who performed the feature's primary action, divide by the total active users in that window, and multiply by 100.

What is a good feature adoption rate?

There is no universal number. Adoption depends on the feature type, the product, and the size of the feature's target audience. As a working guide: core features that define the product should reach 50% or more (70%+ is elite); important secondary features are healthy at 25-40%; niche or advanced features are expected at 5-20%. By context, B2B SaaS features commonly land 30-50%, consumer apps 15-40%, enterprise software 40-70%.

How is feature adoption rate different from feature usage rate?

They are the same core idea measured against different denominators. Feature adoption rate usually measures distinct users who have ever (or recently) used a feature against all eligible users. Feature usage rate is typically measured per period (per week) and emphasises ongoing, repeated use rather than first-time adoption. Adoption answers 'did they try it?'; usage answers 'do they keep using it?'.

How does feature adoption rate reveal feature bloat?

Sort every feature by adoption rate, ascending. The bottom quintile is your bloat audit list. A feature below 5% adoption for 90 days that is not a deliberate niche tool is a deprecation candidate: it imposes maintenance, documentation, test, and cognitive costs on the whole product while serving almost nobody.

9 min read

Feature adoption rate: the formula, the benchmarks, and what it tells you

The formula

Feature adoption rate = (users who used the feature ÷ total active users) × 100

Feature adoption rate is the percentage of your active users who use a given feature in a chosen time window. It is the single most useful number for finding feature bloat: sort every feature by adoption rate, ascending, and the bottom of the list is your audit starting point. There is no universal “good” rate; the right benchmark depends on whether the feature is core, secondary, or niche, and on whether you are B2B, consumer, or enterprise. The benchmark table below gives the working ranges.

01. A worked example

Counting it for one feature

Say you shipped an analytics dashboard. Last month you had 500 monthly active users. Of those, 200 opened the dashboard and ran at least one report. Your monthly feature adoption rate for the dashboard is 200 ÷ 500 × 100 = 40%.

Three details decide whether that 40% means anything. First, define the denominator precisely: active users in the same window, not all signups ever. A feature divided by your all-time registration count will look falsely tiny. Second, count active use, not passive exposure. A user who saw the dashboard tab but never opened it has not adopted the feature. Fire the event on the feature's primary action: a click, a typed input, a completed flow. Third, fix the window and keep it fixed. Weekly adoption and monthly adoption are different numbers; comparing one month's weekly figure to another month's monthly figure tells you nothing.

Adoption vs usage

Adoption rate answers “did they try it?” Usage rate, measured per period, answers “do they keep using it?” A feature can have high adoption and low usage (everyone tried it once, nobody came back) which is often a worse signal than low adoption alone. See the four feature-bloat metrics for the ongoing-usage side.

02. Benchmarks by feature type

What counts as a good feature adoption rate

There is no single “good” number, and any source that gives you one without asking what kind of feature you mean is selling something. Adoption depends on the feature's role in the product and the audience it targets. These ranges synthesise commonly cited product-analytics benchmarks (Pendo, Amplitude, Appcues). Treat them as thinking aids, not targets.

Core features

Healthy 50%+ · Elite 70%+

The features that define what your product is for.

Below 50% on a core feature is a discoverability or onboarding failure, not a niche signal.

Secondary / power features

Healthy 25-40% · Elite 50%+

Important, but not why most people show up.

Healthy range is wide. Watch the trend more than the absolute number.

Niche / advanced features

Healthy 5-20% · Elite 25%+

Built for a specific segment or workflow.

Low adoption is expected and fine, provided the segment it serves is deliberate and valued.

By product context

Product type	Typical good range	Why
B2B SaaS	30-50%	Smaller, engaged user bases; features are often role-specific.
Consumer apps	15-40%	Larger, more casual audiences pull the average down.
Enterprise software	40-70%	Mandated rollouts and admin-driven configuration lift adoption.

03. From adoption rate to feature bloat

The number is a diagnosis, not a scoreboard

The reason adoption rate matters for feature bloat is the shape of the distribution it reveals. Pendo's 2019 Feature Adoption Report, which analysed feature usage across 615 subscriptions over a three-month period, found that around 80% of features in the average product are rarely or never used, and just 12% generate 80% of daily usage. The Standish Group's 2002 figure put 64% of enterprise features in the “rarely or never” bucket. Whatever your product, most of your features sit near the bottom of the adoption list. That is the baseline, not the anomaly.

So the move is not to chase every feature toward a target adoption rate. It is to sort by adoption, look at the bottom quintile, and ask of each one: is this deliberately niche, or is it bloat? A feature below 5% adoption for 90 days that nobody designed to be niche is a deprecation candidate. It still costs you maintenance, documentation, test coverage, and the cognitive load it adds to every user who has to scroll past it. Low adoption is only acceptable when it is a choice.

For what to do once you have the list, see the surgical playbook for removing features, and the decision framework for stopping low-adoption features before they ship.