Skip to main content
Product Teams

Launch features people actually understand and use

Ship a challenge alongside every release. Audit existing feature knowledge to find the gaps that explain low adoption. Turn product data into product decisions.

40%

of features go unused after launch

2.4x

faster adoption with release challenges

5 min

to create a feature launch challenge

73%

average challenge completion rate

The Problem

You ship features. Users don't use them.

Your team spends months building a feature. You write the changelog, send the email, add a tooltip. Two weeks later, adoption is at 8%. The feature sits there, unused, while users keep asking for things you already built.

The problem isn't awareness. They saw the announcement. The problem is comprehension. Users don't understand what the feature does, when to use it, or how it fits into their workflow. And you have no way to measure that gap.

Release v4.2

3 new features shipped

Smart Workflows
8%
Custom Dashboards
12%
API Webhooks
5%

Adoption 2 weeks after launch

The Solution

Ship features with built-in comprehension

Create a "What's new in v4.2" challenge from your release docs. Users play through 15 questions that teach them what each feature does, when to use it, and how it connects to what they already know. They learn by doing, not by scanning a changelog.

Then run challenges on your existing features. If 60% of users can't answer basic questions about your core workflow engine, that's not a marketing problem. It's a product problem. Now you have the data to decide: improve the UX, write better docs, or rethink the feature entirely.

Feature Knowledge Audit

v4.2 Release Challenge Results

Smart Workflows34% comprehension
Custom Dashboards58% comprehension
API Webhooks22% comprehension
Core Features85% comprehension

Action needed: 66% of users don't understand Smart Workflows. Consider a targeted deep-dive or UX improvement.

Why This Works

Turn launches into learning moments

Ship features with built-in education

Every release gets a challenge. Users learn what's new through interactive questions, not changelog walls. They discover features by engaging with them, not by stumbling into them weeks later.

Measure adoption, not just awareness

Knowing users saw the announcement isn't enough. Challenges tell you who actually understands the feature. Low scores on 'Workflows' means your users aren't ready to use it, even if they clicked the banner.

Find the gaps before they become churn

Run a challenge on your existing features. If 60% of users can't answer questions about your core value prop, that's a product problem, not a docs problem. Now you have the data to fix it.

Two playbooks, one tool

New feature launches + existing feature audits

Feature Launch Challenge

Ship a challenge alongside every release. Users learn what's new through interactive questions instead of passive changelogs.

1

New release? Create a challenge

Paste the docs or changelog URL for your new feature. We auto-generate 15 questions that teach users what's new, how it works, and when to use it.

2

Distribute with the release

Add the challenge link to your release email, in-app banner, or Slack announcement. Users play through it in 3 minutes and actually learn the feature.

Feature Knowledge Audit

Run challenges on existing features to find comprehension gaps that explain low adoption. Turn data into product decisions.

3

Audit existing feature knowledge

Create challenges for features that have low adoption. The results tell you whether users don't know the feature exists, don't understand it, or understand it but don't need it.

4

Close the loop with data

Per-feature knowledge scores feed directly into your product decisions. Low comprehension on a feature? Improve the UX. High comprehension but low usage? Rethink the value prop.

The Shift

Before vs. After

BeforeAfter
Ship feature, hope users find itShip feature with a challenge that teaches it
"We announced it in the changelog""82% of users understand the new workflow"
No data on feature comprehensionPer-feature knowledge breakdown across all users
Guess why adoption is lowKnow exactly which concepts users don't understand
Same release email for everyoneTargeted follow-ups based on knowledge gaps
We shipped three features last quarter. Two had single-digit adoption. We ran a challenge and found out users didn't even know what the features did. Now every release ships with a challenge and adoption is up 2.4x.

What our users are saying

Early access

Apply for Early Access

We're opening up early access to a small group of teams. Drop your email and we'll reach out when your spot is ready.

No spam. We'll only reach out if it's a fit.