← VCE Data Analytics U4O1

Collecting user feedback on a solution

Set questions you ask users after they try your solution. You record their ratings and comments, then sum up the answers to compare with your criteria.

Understanding Collecting user feedback on a solution in VCE Data Analytics U4O1

What it does: This question has no fixed answer choices, so users can write their own comments and ideas. COUNTIF counts the ratings of 4 or 5, giving a summary you can check against a criterion such as 'most users rate it 4 or more'. A survey uses the same set of questions for every user after they try the solution, so the answers can be fairly compared. A rating question asks users to choose a number on a scale. The second one is an open comment question. Users can only give useful feedback once they have actually tried the solution. Record all answers, good and bad. Leaving some out gives you a biased picture of how well the solution works.

Common mistakes: The average is the total of the ratings divided by the number of answers. The line should be average ← total / count. To find the average you divide the total by the number of ratings, not multiply. It should be avg ← total / LENGTH(ratings).

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

This module's key terms are also in a printable crossword (Modules 85–105) and word search (Modules 63–105).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
Which is a good way to collect user feedback on your new quiz app?
Ask each user the same set of questions after they try itAsk only your best friend what they think while you build it
Matches
Don't you think our app is great?
↓
This is a leading question. It pushes users to agree, so the feedback is not honest.
Applying
Meanings
Term
user feedback survey
Meaning
Set questions you ask users after they try your solution. You record their ratings and comments, then sum up the answers to compare with your criteria.
Practice
Q1: Rate how easy the app was (1-5).
Testing
Gaps
ASK question: "Rate the quiz 1 to 5"
Check Answer
Spots
3 total ← total + rating
4average ← count / total

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Badger' badge — Determined Digger, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Quick Questions

1. Which is a good way to collect user feedback on your new quiz app?
A. Ask only your best friend what they think while you build it
B. Ask each user the same set of questions after they try it ✓
A survey uses the same set of questions for every user after they try the solution, so the answers can be fairly compared.
2. Which is a rating question?
A. How easy was the app to use? Rate it from 1 to 5. ✓
B. What would you change about the app?
A rating question asks users to choose a number on a scale. The second one is an open comment question.
3. Which question lets users give an open comment?
A. What did you find confusing, and why? ✓
B. Did you like the app? Yes or No.
Open comments let users write answers in their own words. A yes/no question only gives two fixed choices.
4. When should you ask users the survey questions?
A. After they have tried the solution ✓
B. Before they have seen the solution
Users can only give useful feedback once they have actually tried the solution.
5. After collecting survey answers, what should you do first?
A. Keep only the answers that say nice things
B. Record every answer so you can sum them up ✓
Record all answers, good and bad. Leaving some out gives you a biased picture of how well the solution works.

Match the Pairs

Rate the app from 1 to 5 → A rating question that gives each user's opinion as a number you can compare with your criteria
=AVERAGE(B2:B11) → Summarises ten ratings by finding the average score
An open comment question lets users explain their thoughts in their own words → What would you change about the app?
Summarise the answers by counting how many users gave a high rating, then compare to your criteria → =COUNTIF(B2:B11,">=4")
Don't you think our app is great? → This is a leading question. It pushes users to agree, so the feedback is not honest.
Was the app fun and easy to use? Yes/No → This asks two questions in one, so you can't tell which part the answer is about.

Key Term

user feedback survey
Set questions you ask users after they try your solution. You record their ratings and comments, then sum up the answers to compare with your criteria.

Fill in the Blanks

1. ASK rating question: "Rate the quiz 1 to 5"
Hint: Type the kind of question that asks users to pick a number on a scale.
2. ASK open comment: "What would you change?"
Hint: Type the word for a comment question where users write answers in their own words.
3. SET scores ← [4, 5, 3, 5] SET average ← SUM(scores) / LENGTH(scores)
Hint: Type the function that adds all the ratings together to help summarise them.
4. SET average ← 4.25 IF average >= 4 THEN PRINT "Criteria met"
Hint: Type the operator that checks the average is at least the target in your criteria.
5. SET answer ← ASK("Rate the quiz 1 to 5") APPEND answer TO responses
Hint: Type the keyword that records each answer by adding it to the list of responses.

Spot the Error

Question 1
A total ← 0
B FOR each user answer
C total ← total + rating
D average ← count / total
E SHOW average
Line D — The average is the total of the ratings divided by the number of answers. The line should be average ← total / count.
Question 2
A ratings ← [4, 5, 3, 4]
B total ← SUM(ratings)
C avg ← total * LENGTH(ratings)
D SHOW avg
Line C — To find the average you divide the total by the number of ratings, not multiply. It should be avg ← total / LENGTH(ratings).
Question 3
A ASK 'Is the game good? 1 to 5'
B SAVE answer TO ratings
C ASK 'Any comments?'
Line A — A yes/no question does not suit a 1 to 5 scale. A rating question should ask the user to rate something, like ASK 'Rate the game 1 to 5'.
Question 4
A ratings ← [4, 5, 3]
B highest ← MAX(ratings)
C lowest ← MIN(ratings)
D SHOW 'Lowest: ', highest
Line D — The label says Lowest but the line shows the highest rating. It should show the lowest variable so the summary is correct.
Question 5
A ratings ← []
B APPEND answer TO comments
C SHOW ratings
Line B — The list comments was never created, and the rating belongs in the ratings list. The line should be APPEND answer TO ratings.

Student with a class code? Join your class →