Turn passive reading into active learning
Add "Test your knowledge" challenges at the end of any docs section. Find out if your documentation is actually teaching anything.
12%
of users finish reading docs
10 min
average retention of docs content
75%
retention with active recall
32%
of docs sections need rewriting (avg)
You write great docs but nobody reads them
You pour hours into documentation. Users skim, scroll, and close the tab. Only 12% finish reading. Even the ones who do forget most of it within 10 minutes. There's no way to know if your docs are actually teaching anything, and the support tickets keep rolling in for features you've already documented.
Page views tell you nothing about comprehension. You're guessing which sections need work. Static, one-way documentation leaves you blind.
Test Your Knowledge: Workflows
5 questions based on what you just read
Add challenges. Get direct signal on comprehension.
Embed a "Test your knowledge" challenge at the end of any docs section. Users test themselves on what they just read. You get instant feedback on what they understood and what they missed.
If 80% of users get Question 7 wrong, that tells you something specific: the section on Workflows needs rewriting. No survey, no feedback form, no guessing. You identify exactly which sections confuse users before the support tickets arrive.
Knowledge Gap Report
Action needed: "Workflows" section has a 32% comprehension rate. Consider rewriting with more examples.
What the analytics reveal
Knowledge Gap Report
Getting Started: 94% comprehension
Your onboarding docs are solid. No action needed.
Workflows: 32% comprehension
This section needs rewriting. Add more examples and screenshots.
API Reference: 45% comprehension
Consider adding code snippets and a quickstart guide.
How docs teams use this
Add widget to docs
Embed a 'Test your knowledge' challenge at the end of any docs section. Simple iframe or link. Works with any docs platform.
Users test themselves
Readers take a quick challenge on what they just read. They get instant feedback on what they understood and what they missed.
Track weak spots
Dashboard shows which docs sections have the lowest comprehension rates. Per-question breakdown reveals exactly what confuses users.
Update docs
Rewrite the sections that score lowest. Measure improvement over time. Data-driven documentation that actually works.
Built on learning science
Testing effect
Cognitive science shows that being tested on material improves retention by 50-150% compared to re-reading. Your users remember more when they're challenged.
Direct signal
Page views tell you nothing about comprehension. Challenge scores tell you everything. If 80% of users get Question 7 wrong, that section needs rewriting.
Continuous improvement
Update your docs based on real data. Measure the impact of your changes. Create a feedback loop between documentation and user understanding.
Before vs. After
| Before | After |
|---|---|
| "Did anyone read the docs?" | "94% completed the Workflows challenge" |
| Page views as success metric | Comprehension scores per section |
| Support tickets about documented features | Proactive docs improvements before tickets |
| Guessing which sections need work | Data showing exact comprehension rates |
| Static, one-way documentation | Interactive, measurable learning |
We added challenges to our top 5 docs sections. Within a week, we discovered that our Workflows docs had a 32% comprehension rate. We rewrote the section, and the next challenge showed 71%. First time we've ever had data on whether our docs actually work.
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.