Lesson Notes By Weeks and Term v4 - JHS 3
DESIGNING
Download the Lessonotes Mobile Ghana app for faster lesson access on Android and iPhone.
DESIGNING
Download the Lessonotes Mobile Ghana app for faster lesson access on Android and iPhone.
Subject: Career Technology
Class: JHS 3
Term: 3rd Term
Week: 3
Grade code: B9.5.2.1.1
Strand code: 5
Sub-strand code: 2
Content standard code: B9.3.3.1
Indicator code: B9.5.2.1.1
Theme: DESIGNING AND MAKING OF ARTEFACTS/PRODUCTS
Subtheme: DESIGNING
This page supports the lesson note with a companion video and a short classroom-ready summary.
For class groups and homework, share this lesson page so learners also get the summary, objectives, and full lesson context.
Welcome, future designers and innovators! In today's lesson, we will explore the most important first step in creating any successful product or artefact: understanding the people who will use it. Think about your school bag, the cooking pot at home, or even the tro-tro you ride. These things were all designed for a user. If a product doesn't meet the user's needs, it is a failed design. This lesson is crucial because whether you are designing a new machine for a farm, a better package for selling gari, or a new mobile app, success starts with listening to and understanding your user. We will learn how to ask the right questions and observe carefully to discover what people truly need.
a. Who is a 'User'?
A user is any person or group of people who will interact with or use the product, service, or system you are designing. The user is the most important person in the design process. Example 1: For a school uniform, the user is the student who wears it. The parents who buy and wash it are also important stakeholders, but the student is the primary user. Example 2: For a new cooking pot, the user is the person who does the cooking – your mother, father, or yourself. Example 3: For a new farm tool, the user is the farmer. b. What are 'User Requirements'?
User Requirements are the specific needs, wants, goals, and expectations that a user has for a product. They are the problems a product must solve. They answer the question: "What must this product do to be successful for the user?"
We can group user requirements into two main types: Functional Requirements: These describe what the product *must do* or the specific tasks it must perform. They are about the function. A water bottle *must hold water without leaking*. A mobile phone *must be able to make and receive calls*. A school bag *must be able to carry books*. Non-Functional Requirements: These describe the *qualities* or characteristics of the product. They are about how well the product performs its function. A water bottle should be *durable* (not break easily), *lightweight*, and *easy to clean*. A mobile phone should have a *long battery life*, be *easy to use*, and be *affordable*. A school bag should be *comfortable to carry*, *look fashionable*, and be *made of strong material*.