measuring quality with rubrics - Dashboard
2,573
visibility Viewed
21
Total Responses
21
flag Completed
100%
timelapse Completion Rate
0
do_not_disturb_on Dropouts
44 mins
access_time Average Time
 
Countries Responses
US 38.10%
IL 14.29%
CZ 4.76%
DE 4.76%
VN 4.76%
DK 4.76%
GB 4.76%
IN 4.76%
CA 4.76%
NL 4.76%
CN 4.76%
RU 4.76%
Total 100.00%
1. The approach described here for measuring documentation quality is sound and well thought out.
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 1 4.76%
Disagree 0 0%
Neutral 0 0%
Agree 7 33.33%
Strongly agree 13 61.9%
Other 0 0%
Total 21 100%
1. The approach described here for measuring documentation quality is sound and well thought out. - Text Data for Other
No Data To Display
2. User satisfaction surveys (rather than rubrics like the one described here) are usually a much better way to measure documentation quality.
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 4 19.05%
Disagree 8 38.1%
Neutral 7 33.33%
Agree 1 4.76%
Strongly agree 1 4.76%
Other 0 0%
Total 21 100%
2. User satisfaction surveys (rather than rubrics like the one described here) are usually a much better way to measure documentation quality. - Text Data for Other
No Data To Display
3. Feedback from user satisfaction surveys is usually general, vague, and not actionable. As such, it's not all that helpful.
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 0 0%
Disagree 5 23.81%
Neutral 1 4.76%
Agree 7 33.33%
Strongly agree 8 38.1%
Other 0 0%
Total 21 100%
3. Feedback from user satisfaction surveys is usually general, vague, and not actionable. As such, it's not all that helpful. - Text Data for Other
No Data To Display
4. Technical writers rarely have unfettered access to users (via surveys, training, support) to gather feedback about docs on a regular basis.
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 1 4.76%
Disagree 1 4.76%
Neutral 3 14.29%
Agree 5 23.81%
Strongly agree 11 52.38%
Other 0 0%
Total 21 100%
4. Technical writers rarely have unfettered access to users (via surveys, training, support) to gather feedback about docs on a regular basis. - Text Data for Other
No Data To Display
5. The list of criteria in your rubric includes the most important points to look for in developer docs.
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 0 0%
Disagree 0 0%
Neutral 0 0%
Agree 12 57.14%
Strongly agree 9 42.86%
Other 0 0%
Total 21 100%
5. The list of criteria in your rubric includes the most important points to look for in developer docs. - Text Data for Other
No Data To Display