Year 8 Design & Technologies · Creating Designed Solutions · 9m read

Advanced Design Thinking — User-Centred Design

Ever wonder why some apps feel effortless while others frustrate you? That's because their designers actually studied real people first. User-centred design means building things around what your users actually need—using tools like personas (imaginary character profiles), user journeys (step-by-step maps of how people interact), and prototypes (rough versions you test). For your VCE design projects and future career, this approach transforms you from guessing what people want to confidently creating solutions that genuinely work.

Learning objective: Apply user-centred design methods including personas, user journeys and prototyping to a design challenge.

By the end of this lesson you can:

• I create a user persona and user journey map for a design problem.
• I use "how might we" questions to focus design thinking.
• I rapidly prototype and test solutions based on user feedback.

User-centred design is walking in someone else's shoes. You can't design a great product for someone until you understand how they live, what frustrates them and what they need.

User-centred design tools

USER-CENTRED DESIGN (UCD):
Design process that places the USER — their needs, behaviours, context — at the centre of every decision.
"Design for how people actually behave, not how you assume they should."

USER PERSONA:
A fictional but research-based character representing a user type.
Includes: name, age, occupation, goals, frustrations, tech-savviness, context of use.
Purpose: keeps the team focused on real human needs rather than abstract requirements.
Example persona:
Name: Maya, 13, Year 8 student.
Goal: quickly find relevant study resources between classes.
Frustration: apps that take too long to load, require sign-in for every visit.
Context: using phone on the bus with intermittent Wi-Fi.

USER JOURNEY MAP:
Traces a user's entire EXPERIENCE with a product/service step by step.
Includes: stages of interaction, user actions, thoughts, emotions, pain points.
Reveals: where frustration occurs, what needs improvement.
Stages for a study app: Discover → Download → Create account → First search → Find resource → Study → Return next day.

"HOW MIGHT WE" QUESTIONS:
Convert problems into opportunity questions.
Problem: "Users forget to review notes."
HMW: "How might we remind students to review notes in a way that feels helpful rather than nagging?"
Opens up the solution space without prescribing a solution.

RAPID PROTOTYPING (Iteration):
Build the CHEAPEST possible testable version of an idea.
PAPER PROTOTYPE: draw app screens on paper. Test with a real user holding the paper.
"Fail fast, learn fast" — better to discover problems in a paper prototype than in finished code.
Each iteration incorporates user feedback.

User-centred design rules

• You are not the user: "Designers are cursed with knowledge." You know your design too well to find its problems. Real users ALWAYS reveal issues you never anticipated.
• Test early and often: Every stage — wireframe, paper prototype, digital prototype — should be tested with real users. The later a problem is found, the more expensive it is to fix.
• Pain points = design opportunities: User frustrations and failures are the most valuable design data. They tell you exactly where to focus improvement.

Quick reference

| Tool | Purpose |
|---|---|
| Interviews | Understand needs |
| Observation | See real behaviour |
| Persona | Represent a typical user |
| Empathy map | Says, thinks, does, feels |
| User testing | Feedback on prototypes |

Worked example (Medium)

Create a user persona for a student who uses a school library booking system.

1. Name and demographics. Liam, 14, Year 9 student. Studies mostly at home but needs the library for group projects and research periods.
2. Goals. Quickly book a study room for three people. Check if printer is available. Access from his phone.
3. Frustrations (pain points). Doesn't know which rooms are available without clicking through multiple pages. System times out if he's slow. Forgets the room number after booking.
4. Context. Books rooms between classes (2-minute window). Often on mobile data, not Wi-Fi. Sometimes books with friends who also need to confirm.

Answer: Persona: Liam (14, busy student) needs fast mobile booking with clear availability, immediate confirmation, minimal steps. Pain points guide the UCD priority list.

Worked example (Hard)

A school canteen app has low usage despite being functional. Create a user journey map to identify where students are dropping off, then propose "how might we" questions for the three biggest pain points.

1. User journey stages. Discover app → Download → Create account → Browse menu → Select items → Pay → Collect food. Map emotions at each stage: Discover (curious), Download (neutral), Create account (frustrated — requires email verification), Browse (confused — menu not updated), Pay (anxious — card details), Collect (annoyed — long queue despite pre-order).
2. Pain point 1: Account creation. HMW: "How might we let students start ordering without requiring a full account setup?" Solution direction: guest ordering, school ID login, or progressive account creation (order first, create account later).
3. Pain point 2: Outdated menu. HMW: "How might we ensure the digital menu always reflects what's actually available today?" Solution direction: real-time menu updates linked to stock, daily photo of specials board.
4. Pain point 3: Collection queue. HMW: "How might we reduce wait time for pre-orders so the app saves time compared to queuing?" Solution direction: designated pickup window, notification when order is ready, staggered pickup time slots.

Answer: User journey reveals three drop-off points: complex signup, unreliable menu, no time savings at collection. HMW questions open solution space without prescribing specific solutions.

Common mistakes

• Designing for yourself instead of the user Designers know their own product too well to find its problems. What seems obvious to you may be confusing to first-time users. Fix: Always test with REAL USERS, not just yourself or your friends. Observe them using the product — don't explain how it works.
• Writing vague pain points "Users find it confusing" is too vague to act on. Which part is confusing? When does confusion occur? What are they trying to do? Fix: Be specific: "Users cannot find the 'submit' button because it is below the fold on mobile screens and the same colour as the background."

Design thinking at IDEO — where user-centred design became a movement

The global design firm IDEO popularised the term "design thinking" in the 1990s and demonstrated that user-centred design could solve problems far beyond product design — in healthcare, education, government and social services. Their core principle: empathy before solutions.

IDEO's process follows five stages: Empathise (deeply understand the user through observation and interviews), Define (articulate the core problem in a human-centred way), Ideate (generate many possible solutions without judgement), Prototype (build the cheapest testable version), and Test (put it in front of real users and learn). This process is deliberately non-linear — testing often reveals that the problem was defined incorrectly, sending the team back to empathise again.

A famous example: IDEO redesigned the shopping cart for ABC's *Nightline* show in just five days. Instead of starting with cart engineering, they started by observing shoppers — discovering that cart theft, child safety and navigating narrow aisles were bigger concerns than carrying capacity. The resulting design addressed real human needs rather than assumed engineering problems. This is the essence of user-centred design: the best solution comes from deeply understanding the problem.

Practice questions

1. What is the purpose of a USER PERSONA in design thinking?

   1. To describe the designer's preferences
   2. To represent a fictional but research-based user type, keeping the team focused on real human needs
   3. To list the technical requirements for the product
   4. To create a character for marketing

   (1 marks)

2. Explain why RAPID PROTOTYPING and early testing is more effective than spending a long time perfecting a design before testing.

   (2 marks)

Summary

• Create a user persona and user journey map for a design problem.
• Use "how might we" questions to focus design thinking.
• Rapidly prototype and test solutions based on user feedback.