Documentation Feedback Survey
Did the docs answer the question? Findability, accuracy, and the missing article.
4 questions · 1 page · about 3 minutes to answer · fully editable after you start
Documentation has one job: answer the question the reader arrived with. This survey measures exactly that, plus the failure modes when it does not – could not find it, found it but outdated, found it but did not understand it – each of which routes to a different docs fix.
The what-were-you-looking-for write-ins, clustered monthly, are your content calendar: the questions asked most and answered worst are the next articles to write.
Template preview
This is a picture of every question as a respondent would see it, so nothing on it can be clicked or typed into. Use this template to get your own editable copy.
Opens in the Light theme, or in your own default theme if you have set one — change it anytime to any of the 4 built-in looks, or build your own on a paid plan.
Page 1
About the docs
This survey is about the documentation you have just used. Tell us whether it answered your question, so we can improve it. It takes about 3 minutes.
Q1.Did the documentation answer the question you came with?*
- Yes, fully
- Partly
- No - could not find it
- No - found it but it did not help
Q2.What were you trying to find or do?*
Q3.How would you rate the docs on each of these?
| Poor | OK | Great | Not applicable | |
|---|---|---|---|---|
| Search and findability | ||||
| Accuracy | ||||
| Up to date | ||||
| Clarity of writing | ||||
| Examples and code snippets |
Q4.Which article is missing or most needs a rewrite?
Where this template is used
More Product & UX templates
Browse all Product & UX templates
Feature Prioritisation Survey
Rank the roadmap candidates and surface the problems behind the requests.
Feature Request Intake Form
Requests that arrive as problems, context, and impact - not just wishes.
First-Run Copy Test
Do your empty states and onboarding words actually instruct? Tested on fresh eyes.