Course feedback: page feedback vs end-of-course surveys
Use page feedback to find problems in individual lessons and end-of-course surveys to understand the overall learning experience.
A learner can enjoy a course overall and still get stuck on one lesson.
That is why page feedback and end-of-course surveys answer different questions.
Use page feedback when you want to know whether a specific lesson, example, diagram, or exercise worked. Use an end-of-course survey when you want learners to reflect on the course as a whole.
For many courses, both are useful: page feedback finds local problems, while the final survey gives you the broader view.
Page feedback vs end-of-course surveys
| What you want to learn | Best method |
|---|---|
| Was this lesson clear? | Page feedback |
| Did this example or exercise help? | Page feedback |
| Where did the learner get stuck? | Page feedback |
| Was the course well paced? | End-of-course survey |
| Did the lessons work well together? | End-of-course survey |
| What was missing from the course? | End-of-course survey |
| Which lessons need work and how the course performed overall | Both |
The rule is simple: ask about a lesson while the learner is there, and ask about the course after they finish it.
Use page feedback for specific lesson problems
Page feedback works best when the learner can respond while the relevant content is still in front of them.
For example:
Did this lesson help you complete the exercise?
A learner can give a quick rating and, when useful, explain what went wrong.
With PushFeedback, page-level feedback can include ratings, comments, the page URL, and an optional annotated screenshot.
That is useful for:
- code examples
- diagrams
- step-by-step exercises
- setup instructions
- quizzes
- lessons with important prerequisites
If a learner says, "I don't know where the token goes," and the feedback came from the authentication lesson, you already know where to start reviewing.
When the exact location matters, visual feedback can let the learner point to a specific part of the page with an annotated screenshot.
Review the feedback together with the lesson. Check the current instructions, reproduce the task when useful, and decide whether the problem is unclear wording, missing information, an incorrect example, or something outside the course content.
Use end-of-course surveys for the overall experience
Some questions only make sense after the learner has seen the full course.
For example:
- Was the course well paced?
- Did the lessons follow a logical order?
- Which part was most useful?
- What was missing?
- Would you recommend the course?
These questions ask the learner to look back across the whole experience.
The trade-off is that the answers usually contain less precise page context.
A learner might say:
The authentication section was confusing.
That tells you where to investigate, but not whether the problem was the introduction, a code sample, an exercise, or the transition into the next lesson.
That is where page feedback adds useful detail.
Use both when you need both views
You do not have to choose one method for the entire course.
A simple setup is:
- Add a short feedback prompt to lessons where learners perform an important task.
- Keep comments optional.
- Add a short survey after the final lesson.
- Use page feedback to improve individual lessons.
- Use the final survey to review pacing, structure, and coverage.
Imagine a four-lesson API onboarding course.
During the authentication lesson, several learners report that they do not know where to place the API token.
That points to a specific lesson problem. You can review the instructions and code example.
At the end of the course, several learners say the transition from authentication to making the first API request feels abrupt.
That points to a broader course problem. You may need a better transition, another example, or a different lesson order.
The two types of feedback complement each other.
Keep the questions short
More questions do not automatically produce better feedback.
For lesson-level feedback, one question is often enough:
Did this lesson help you complete the task?
Let learners add a comment if they want to explain their rating.
For the end-of-course survey, ask only the questions you intend to review.
For example:
- How useful was this course?
- Which part should we improve first?
- Was anything important missing?
The easier the feedback is to submit, the more likely learners are to complete it.
Keep lesson and course feedback separate
A low rating on one lesson does not necessarily mean the whole course is poor.
A high overall course rating does not mean every lesson works well.
For page feedback, look at:
- lessons with repeated negative ratings
- recurring comments
- tasks where several learners get stuck
- screenshots or annotations pointing to a specific problem
For end-of-course surveys, look for patterns around:
- pacing
- structure
- difficulty
- missing topics
- overall usefulness
Then decide what needs to change.
Frequently asked questions
Should every course lesson have feedback?
No. Start with lessons where learners complete important tasks, follow multi-step instructions, or are likely to get stuck.
Can an end-of-course survey replace page feedback?
Not completely. A survey can tell you that part of the course needs work, but page feedback is better at showing which lesson or element caused the problem.
Can page feedback replace an end-of-course survey?
Not completely. Page feedback is useful for individual lessons, but learners need to finish the course before they can judge pacing, sequence, and overall completeness.
What should a page feedback prompt ask?
Tie it to the lesson. For example: "Did this lesson help you send your first API request?" Keep any follow-up comment optional.
Should I use both?
Use both when you want to improve individual lessons and the overall course experience. If you only need one of those views, use the method that matches the question.
Start with one important lesson
Choose a lesson where learner feedback would help you make a concrete improvement.
Add a short page-level question there, then use a brief end-of-course survey if you also need feedback about pacing, structure, or the course as a whole.
If you want to collect page-level ratings, comments, and optional visual feedback from your course, create a PushFeedback project and follow the Quickstart to add the widget to your site.