Computing · Year 4

Active learning ideas

Designing for Users

Active learning helps Year 4 students grasp user-centered design by putting ideas into practice immediately. Children learn best when they experience the challenges of designing for real people rather than abstract concepts.

• National Curriculum Attainment Targets
• KS2: Computing - Information Technology
• KS2: Computing - Programming and Algorithms

• 20–40 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Collaborative Problem-Solving
• 30 min · Pairs

Pairs: User Persona Interviews

Pairs interview three classmates about app preferences, like game controls or menu colours. They create simple persona sketches with needs and pain points. Pairs then draw a tailored main menu layout for an animation viewer.

Explain why different people might use a program in different ways.

Facilitation Tip

During User Persona Interviews, provide sentence starters on the board to guide students in asking clear, open-ended questions about their partner’s preferences.

What to look for

Present students with two different interface designs for a simple drawing app. Ask them to point to the design they think a younger sibling could use more easily and explain one specific reason why.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 02

• Collaborative Problem-Solving
• 40 min · Small Groups

Small Groups: Paper Prototype Swap

Groups sketch interactive screens for a story animation app on card. They swap prototypes with another group for 5-minute usability tests, noting confusions on sticky notes. Groups revise one screen based on feedback.

Design a simple interface that is clear and easy for a friend to use.

Facilitation Tip

For Paper Prototype Swap, set a 3-minute timer per station so students learn to give focused feedback quickly.

What to look for

Students share their hand-drawn interface sketches. Ask them to ask their partner: 'What is one thing you like about my design?' and 'What is one thing that might be confusing?'

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 03

• Collaborative Problem-Solving
• 25 min · Whole Class

Whole Class: Design Feedback Walk

Display all prototypes around the room. Students rotate in a carousel, leaving one positive and one improvement note per design. Hold a 10-minute share-out to discuss common patterns and vote on clearest interfaces.

Evaluate how feedback from others can help improve a design.

Facilitation Tip

In Design Feedback Walk, place sticky notes on prototypes to mark issues so students can see patterns in user struggles.

What to look for

On a slip of paper, ask students to draw one button or icon they would include in an app for elderly people and write one word explaining why they chose that design.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 04

• Collaborative Problem-Solving
• 20 min · Individual

Individual: Quick Iteration Cycle

Each student selects feedback from the walk and redraws their interface. They self-assess against criteria like clarity and ease. Share one change with a partner for final thumbs-up.

Explain why different people might use a program in different ways.

Facilitation Tip

During Quick Iteration Cycle, encourage students to circle one change they made and explain why it improved usability.

What to look for

Present students with two different interface designs for a simple drawing app. Ask them to point to the design they think a younger sibling could use more easily and explain one specific reason why.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

A few notes on teaching this unit

Teachers should model how to respond to feedback without taking it personally, using phrases like ‘What if we tried…’ to frame suggestions as collaborative problem-solving. Avoid praising designs too early, as this can discourage students from making changes. Research shows that structured peer feedback leads to more iterative improvements than teacher-led critiques alone.

Successful learning looks like students adapting their designs based on direct user feedback and explaining how specific user needs shape their choices. Observing peers interact with their prototypes shows clear evidence of empathy in their designs.

---

Watch Out for These Misconceptions

• During Paper Prototype Swap, watch for students who assume their design is already perfect and skip the peer testing stage.

  Stop groups who rush and remind them that the purpose is to find problems, not to defend their work. Ask, ‘What did your partner struggle with?’ to refocus their attention on user needs.

• During Quick Iteration Cycle, watch for students who change their design based only on their own preferences instead of feedback.

  Direct students back to the feedback they received by asking, ‘Which comment did you use to make this change?’ and have them point to the specific suggestion.

• During Design Feedback Walk, watch for students who give vague feedback like ‘It looks good.’

  Hand out sticky notes with sentence starters (‘I noticed…’, ‘What if…’) to guide students toward specific, actionable comments.

---

Methods used in this brief

• Collaborative Problem-Solving