Skip to content
BENIBIX Learn

Feature Launch and Adoption

Level 5 Β· Shipping and measuring

How a product team releases a feature in steps, from a beta to everyone. How to measure feature adoption once it is out.

Course contentsLesson 11 of 13

After this lesson you can

  • Plan a release in steps
  • Work out a feature adoption rate
  • Tell trying a feature from adopting it

12 mincovers 4 glossary entries

Worth reading first: Product Roadmap Types

How a feature goes out, and how to know it landed

A product launch is not one day. For the product team, it is a release in steps, then a few weeks of watching. A feature might go to 50 beta users first, then 10% of all users, then everyone. Each step is a chance to catch a problem while it is still small and cheap to fix.

A beta release goes to users who agreed to try something early. They know it may have bugs, and they report what goes wrong. A good beta has a clear question, such as can people finish the new checkout without help. It also has an end date, so it does not drift on for months.

A feature flag makes the steps easy. It is a switch in the code that turns a feature on for some users and off for others, without a new release. If the 10% step goes badly, the team flips the switch off in seconds. Nothing has to be rebuilt or sent out again.

Once a feature is out, feature adoption says whether it landed. The adoption rate is the share of active users who used the feature in a set time. If 1,500 of 10,000 active users try a new filter in its first month, the rate is 15%. That number alone hides a lot, though.

Trying is not adopting. Count who came back to the feature, not just who clicked once. A funnel helps: how many saw it, how many tried it, how many used it again. A feature that 6,000 people see, 1,500 try and 600 use again has a clear weak spot to work on.

Low adoption has three usual causes. People cannot find the feature, they do not need it, or it is hard to use. Each one has a different fix: move it, drop it or simplify it. A few user talks will tell you which one you are facing far faster than staring at the chart.

The marketing side of a launch, with its message, its press and its sales training, is a subject of its own. The product team's part is the release and the numbers after it. Both are planned together, and the PRD's success number is what the launch is judged by.

Each step loses people for a different reason. Finding the step with the biggest drop tells you what to fix first.

Worked example

Jack's new search filter

Jack's app has 10,000 active users. He turns a new search filter on for 10%, then everyone. In month one, 6,000 see it, 1,500 try it and 600 use it again.

The drop from seeing to trying is the biggest, at 75%. User talks show nobody understands the icon. A text label lifts trying from 1,500 to 2,700 the next month.

The words for this lesson4

Check yourself

1,500 of 10,000 active users try a new feature, and 600 use it again. What is the first-month adoption rate?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.