← Years 7–8 Creating Digital Solutions

Interviewing a user

A conversation where you ask one user questions and listen to their answers to learn about their problem.

Part of: 7-8 Digital Technologies: Defining and decomposing problems — Module 3, 9-10 Digital Technologies: Defining and decomposing problems — Module 8, QCE Digital Solutions Unit 1 — Understanding Digital Problems — Module 47, QCE Digital Solutions Unit 1 — User Experiences and Interfaces — Module 22, QCE Digital Solutions Unit 2 — Data-Driven Problems and Solution Requirements — Module 26

Understanding Interviewing a user in Years 7–8 Creating Digital Solutions

What it does: A short list of planned questions keeps the interview focused and makes sure you learn about the user's problem. Noting the user's answers while listening means you remember what they said and can use it later. Asking 'why' as a follow-up helps you find the real reason behind the problem. An interview is a conversation with one user, so you can listen closely to their answers. Planning your 3 to 5 questions first means you know what you want to learn.

Common mistakes: In an interview you listen to the user's answer. Talking over it means you miss what they say. Line 3 should be LISTEN to the answer. An interview plan should have 3 to 5 questions. 14 is too many. Line 2 should be PLAN 4 questions.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

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

🖨 Print worksheet + answer key Add Interviewing a user to a class →

This module's key terms are also in a printable crossword (Modules 3–47) and word search (Modules 3–125).

Take this worksheet further — free with Cloodit

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

Learning
Duo
Which is the best description of an interview?
You ask one user questions and listen to their answersYou tell the user what they should need
Matches
Do you like my app idea? Yes or no?
↓
This question pushes the user to agree and only allows a yes or no answer, so you learn very little about their problem.
Applying
Meanings
Term
interview
Meaning
A conversation where you ask one user questions and listen to their answers to learn about their problem.
Practice
Interview plan for Mia
Testing
Gaps
"What do you find hard at recess?"
Check Answer
Spots
2ASK question 1
3TALK over the answer

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

The 'Starfish' badge — Five-Point Star, 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.

Add to class →

Quick Questions

1. Which is the best description of an interview?
A. You tell the user what they should need
B. You ask one user questions and listen to their answers ✓
An interview is a conversation where you ask one user questions and listen to learn about their problem.
2. How many questions should you plan for a short user interview?
A. 3 to 5 questions ✓
B. As many as 50 questions
A short list of 3 to 5 good questions keeps the interview focused and the user does not get tired.
3. Which is a good interview question for a Year 5 student who uses a school library app?
A. What is hard about finding a book? ✓
B. Don't you think my app is great?
Good questions are open and let the user share their problem. Leading questions push the user to agree with you.
4. While the user is answering, what should you do?
A. Listen and note down their answers ✓
B. Talk over them to share your own ideas
Listening and noting answers helps you remember what the user said about their problem.
5. A user says, 'I always forget my homework.' What is a good follow-up?
A. Okay, next question.
B. Why do you forget it? ✓
Asking 'why' as a follow-up helps you find the real reason behind the problem.

Match the Pairs

interview → A conversation where you ask one user questions and listen to their answers to learn about their problem
Why is that hard for you? → A follow-up question that digs deeper into an answer to find the real reason behind the problem
Plan 3 to 5 clear questions before you interview a user → 1. What do you do at lunchtime? 2. What is hard about it? 3. What would help you?
Listen and write down what the user says as short notes → Notes: Mia loses her library books. She forgets due dates.
Do you like my app idea? Yes or no? → This question pushes the user to agree and only allows a yes or no answer, so you learn very little about their problem.
User: I always forget my spelling words. Interviewer: OK. Next question. → The interviewer did not ask 'why' as a follow-up, so they missed the chance to learn the reason behind the problem.

Key Term

interview
A conversation where you ask one user questions and listen to their answers to learn about their problem.

Fill in the Blanks

1. ASK "What do you find hard at recess?"
Hint: Type the command that puts a question to the user in an interview.
2. ASK "What games do you play?" NOTE answer
Hint: Type the command that writes down what the user says while you listen.
3. minQuestions ← 3 maxQuestions ← 5
Hint: Type the smallest number of questions you should plan for an interview.
4. IF answer is interesting THEN ASK "Why?" END IF
Hint: Type the keyword that starts a decision, so you ask a follow-up only when it is needed.
5. FOR EACH question IN plan ASK question NOTE answer
Hint: Type the keyword that goes through every planned question one at a time.

Spot the Error

Question 1
A PLAN 4 questions
B ASK question 1
C TALK over the answer
D NOTE the answer
Line C — In an interview you listen to the user's answer. Talking over it means you miss what they say. Line 3 should be LISTEN to the answer.
Question 2
A user ← Sam, age 9
B PLAN 14 questions
C ASK question 1
Line B — An interview plan should have 3 to 5 questions. 14 is too many. Line 2 should be PLAN 4 questions.
Question 3
A ASK Who uses the app?
B LISTEN to the answer
C SKIP why and go on
Line C — Asking 'why' as a follow-up helps you learn more about the user's problem. Line 3 should be ASK why as a follow-up.
Question 4
A PLAN 5 questions
B ASK question 1
C LISTEN to the answer
D NOTE what I would say
Line D — You note the user's answers, not your own ideas. Line 4 should be NOTE key words in the answer.
Question 5
A user ← one person
B PLAN 4 questions
C ASK user 1 and user 2 at once
D LISTEN to the answer
Line C — An interview is a conversation with one user. Asking two users at once makes it a group chat. Line 3 should be ASK user question 1.

Student with a class code? Join your class →