Problem Statements &
Design Specifications
Synthesize research into a precise design direction, then define essential and desirable success criteria.
By the end of class, you should be able to…
Write a problem statement
Explain the current situation, current problem and research basis for the redesign.
Construct specifications
Translate primary and secondary research into essential and desirable success criteria.
Use design categories
Consider attributes, components, constraints, environment, function, user needs, safety, aesthetics and manufacture where relevant.
Prepare Criterion B
Align task-analysis opportunities and existing-product/UI/UX evidence to project definition.
A problem statement sets the direction—not the solution.
The guide says the first step in solving a problem is to define it clearly.
What is happening now?
Describe intended user, product, task and context.
What needs to improve?
Identify the key user difficulties / opportunities supported by task analysis.
Why is this problem appropriate?
Synthesize qualitative + quantitative findings that justify the redesign.
Specific evidence creates a designable problem.
“Students need a better charging station.”
No defined user, task, evidence or opportunity.
“Students using the shared station during short passing periods struggle to reach rear ports and confirm connection status…”
Continue by summarizing the evidence and the redesign opportunities without prescribing the final mechanism.
Build the problem statement from evidence
Criterion B explicitly links the problem statement to task-analysis opportunities.
Task analysis
Identify the most important pain points and opportunities.
Persona
Explain why the issue matters to the intended user.
Existing products
Show what current products do well / poorly and where opportunity exists.
Synthesize research
Use qualitative + quantitative evidence to justify the problem.
Write concisely
Current situation + current problem + research summary + design direction.
A design specification defines what success must look like.
Specifications are generated from research and communicate the essential and desirable criteria for the redesigned product.
Must be achieved
Without it, the redesign fails a critical user / functional / safety requirement.
Improves the solution
Adds value if feasible but is not as critical as an essential requirement.
Consider the categories that actually matter to your product.
Specifications must include UX evidence from product analysis and the empathize phase.
What should improve?
Learnability, efficiency, memorability, errors or satisfaction.
What should become easier?
Reduce a pain point, step, force, error or workaround.
What performance must change?
Translate comparative testing into measurable success criteria.
Replace vague adjectives with evidence-based criteria.
Which specification is strongest?
Research shows the primary persona often carries books in one hand and currently uses two hands to open the product.
Which criterion is most defensible?
Show where each specification came from.
| Research finding | Specification | Priority | Future test |
|---|---|---|---|
| Rear port is beyond comfortable reach for shorter users. | All user interaction points within validated reach zone. | Essential | Reach test with intended users. |
| 4/6 users miss colour-only status cue. | Status uses at least two interpretable cues. | Essential | First-use recognition test. |
| Users prefer minimal desk footprint. | Footprint should remain within agreed area. | Desirable / context dependent | Dimension check + user feedback. |
Criterion B: Defining the project — 6 marks.
Explain the opportunities and explain the requirements.
Key opportunities informed by task analysis
Links should be explicit and evidence-based, not superficial.
Relevant + detailed reference to research
Requirements should be justified, prioritized and traceable.
Convert three findings into specifications.
Project-definition vocabulary
Retrieve first. Then check.
Can you retrieve it without looking back?
Before you leave…
IA Day 5 — Criterion A Build Day
Keep the evidence chain moving: user → research → decision → test.
B2.1.8 problem statement · B2.1.9 design specifications · Criterion B: current situation/current problem/research summary + essential/desirable requirements + UX/product-analysis evidence.