Test & Evaluate
Evaluation is not “I like it.” It is a claim about success supported by authentic test evidence.
Today students will…
Outline
simple relevant testing methods that generate data.
Evaluate
success against the success criteria using authentic test evidence.
Improve
outline how the solution could be improved.
Impact
outline the effect on the intended user / target audience.
Too vague
“I will see if it works.”
Relevant + data-producing
“A user will place and remove five pencils three times. I will record successful removals and ask for a 1–5 ease-of-use rating.”
Count, time, capacity, stability, repeated function, pass/fail.
Observe the intended / representative user completing the real task.
Check size, fit, clearance, or another measurable requirement.
Use a short rating plus a specific comment about the experience.
Use the product the way it was designed to be used.
Appropriate tester
Intended user or teacher-approved representative user.
Real task
Do the actual holding, organizing, carrying, supporting, or access task.
Honest data
Record the result you get, including failure.
Plan → test → record → evaluate.
Plan
Outline 2–3 relevant test methods.
Performance
Collect count / time / measurement / pass-fail data.
User
Run an authentic user trial and collect a rating/comment.
Evaluate
Compare the evidence to the criteria.
Generic
“I would make it better.”
Evidence-based
“The product tipped in 2 of 5 retrieval trials. I would widen the base or lower the storage height, then repeat the same test.”
Positive impact
Does the solution make a task easier, clearer, more organized, less wasteful, or more convenient for the user?
Limit / unintended impact
Does it take extra space, need maintenance, create another inconvenience, or only work for some users?
Outline the impact on the user / target audience, not the impact on your grade.
Finish the unit with one insight.
What comes next?
Unit 5 brings the full A → B → C → D cycle together in the year’s major Product Development project.