Usability Objectives
& SWOT
Use two structured tools to move from “I like it” toward evidence-based product evaluation.
By the end of class, you should be able to…
Name five objectives
Recall learnability, efficiency, memorability, errors and satisfaction.
Apply objectives
Use each objective to evaluate a product interaction.
Build a SWOT
Analyse strengths, weaknesses, opportunities and threats.
Avoid superficial analysis
Support evaluation with function, performance, usability, features and materials.
Usability can be broken into five questions.
After a defined training period, can the user reach the required level of competence?
Once learned, how quickly and effectively can the task be completed?
Can users return later and remember what to do?
What mistakes happen, how serious are they and can users recover?
How acceptable or pleasant is the experience to users?
Can the user reach a defined level of competence after training?
What must the user be able to do?
Set the task/performance level that counts as competent use.
How much learning time is allowed?
Use a predetermined period of instruction, practice or familiarization.
Can the user now operate correctly?
Observe task success, errors, assistance needed or other relevant evidence after training.
Once learned, can the user perform the task effectively?
8 actions · 18 seconds
Several hand repositioning steps.
5 actions · 11 seconds
Fewer unnecessary transitions.
Can users return after time away?
A product may be learnable on day one but hard to remember after a week or month.
Controls map clearly to actions
Users can resume the task with little relearning.
Hidden sequences or arbitrary controls
Users repeatedly need instructions or trial and error.
What mistakes occur—and what happens next?
How often?
Do users commonly make the same wrong action?
How serious?
Minor delay, spill, damage or safety risk?
Can users recover?
Does the product make the error visible and easy to correct?
How do users feel about the experience?
Satisfaction is not “do you like the colour?” It can reflect confidence, comfort, frustration, perceived effort and willingness to use the product again.
Which objective is being tested?
A user successfully learns a coffee machine on Monday. Two weeks later, the user cannot remember which button starts the cleaning cycle.
Which usability objective is most directly involved?
SWOT structures product analysis into four categories.
Internal positives
Features or performance that currently work well.
Internal negatives
Current product limitations or failures.
Future improvement
Directions where redesign could create value.
External risks / pressures
Factors outside the current product that may challenge success or relevance.
Weak SWOT labels are easy. Good SWOT analysis is specific.
“Strength: good design”
Vague, subjective, no evidence.
“Strength: seal prevented leakage in 5/5 inversion tests.”
Specific product feature linked to performance evidence.
Use usability evidence to populate a stronger SWOT.
Usability test
After a 3-minute guided introduction, 4/6 users still press the wrong control during the target task.
Objective
Learnability + errors are weak.
SWOT
Weakness: control mapping remains unclear after the defined introduction/training period.
Opportunity
Redesign control visibility / mapping and retest.
Test one classroom product with three objectives.
Choose a stapler, tape dispenser, door latch, pencil sharpener or similar object.
Usability + SWOT vocabulary
Retrieve first. Then check.
Can you retrieve it without looking back?
Before you leave…
IA Day 2 — Research Plan
Keep the evidence chain moving: user → research → decision → test.
Explain today’s key ideas without notes, then apply one idea to a different product, user or design context.