Move from a design need to a tested proposal
Use research, a measurable specification, iterative ideas, models and evaluation to develop a purposeful product proposal.
This lesson is original StudyForA learning support aligned to Cambridge International AS & A Level Design & Technology 9705. It is not Cambridge material or an official mark scheme. Practical activity must follow the learner's centre procedures and trained supervision.
Before you begin
- Read the product brief and identify its intended user and context.
Work on paper. Try each question before revealing help, and explain why your method works.
Quick readiness check
Which is stronger evidence that a closure meets a brief?
What you will learn
- 9705 T1 approaches
- 9705 T1 design thinking
- 9705 T1 product analysis
- 9705 T1 design stages
Iterate from evidence
Design can be iterative, intuitive, or a considered combination. An iterative process cycles through understanding users, defining the problem, generating ideas, refining, realising a solution and testing it. Each cycle should use evidence to improve the next decision; it is not simply repeating sketches.
Start with an original need or a specific opportunity to improve a product. Gather relevant primary and secondary research, analyse it, then write a brief and a concise specification. Each criterion should be justified and measurable where possible, so the design can later be checked against it.
Compare, model and refine
Analyse existing products through function, appearance, ergonomics, materials, processes, customer, cost, safety, quality and sustainability. Separate observation from inference: a product's visible feature is evidence, while a claim about its comfort or durability needs testing.
Generate alternatives, test them against the specification, model important features, select and develop a proposal, plan resources and make safely. Evaluate the product with suitable tests and identify further improvements. A successful process keeps the specification visible throughout.
Sources for this lesson
Pause and explain
Which principle best supports this lesson: move from a design need to a tested proposal?
Worked example
A reusable lunch container leaks in a school bag. Turn the complaint into one design criterion and a fair test.
Show the worked solution
- Clarify the user's need and the conditions in which the leak occurs.
- Write a measurable criterion, such as no visible leakage after a stated duration in a stated orientation.
- Use the same fill volume, closure procedure and test duration for each prototype.
- Record results, compare them with the criterion and revise the closure if needed.
Answer A testable criterion might require no visible leakage after 20 minutes on its side with a specified water volume. The duration and volume should reflect evidence about actual use; the test supports this condition only and does not prove performance in every situation.
Try a topic test
Choose Easy, Normal or Difficult. Save your answers and open worked review after finishing.
Test this topic →From guided practice to a new situation
Write your answer and reasoning first. Use a hint only if you are stuck. The model solution is for self-checking; your written work is not automatically marked.
A user says a desk organiser is 'hard to use'. Give three research questions that could turn this into a design need.
Give me a hint
Ask who uses it, what task fails, and where the organiser is used.
Compare my reasoning
- Identify the user and the task they are trying to complete.
- Ask what objects, space and frequency of use matter.
- Observe or interview with permission, then record evidence and uncertainty.
Find out which user cannot locate or reach which item, how often this happens, and what desk space and storage objects are involved. Those answers can guide a brief; the phrase 'hard to use' alone is too vague to test.
Look for these in your work
- Names the user and task
- Collects context-specific evidence
- Avoids assuming the cause
Two prototypes meet the size criterion; one is cheaper and the other is easier to clean. How should a designer select one?
Give me a hint
Use the justified specification and compare evidence, not an unweighted list of likes.
Compare my reasoning
- Check how important each criterion is to the user and brief.
- Gather comparable cost and cleaning evidence for both prototypes.
- Explain the trade-off and record why the selected option best meets the weighted needs.
There is no automatic winner. Use research to prioritise cost and cleanability, test both prototypes under the same conditions, then justify the choice against the specification. If the criteria conflict, revise the brief or collect more user evidence.
Look for these in your work
- Uses the specification
- Compares evidence fairly
- Explains the trade-off
A first model is awkward for left-handed users. Describe the next design cycle.
Give me a hint
Use the test finding to refine the problem, not just decorate the same model.
Compare my reasoning
- Record which interaction causes difficulty and confirm it with suitable users.
- Revise the specification to include an observable access or control criterion.
- Generate and model alternatives, test them, and compare results.
Document the specific access problem, check it with left-handed users, and update the specification. Try alternatives such as reversible controls or a different grip, then repeat a controlled task test. One test group does not represent every left-handed user.
Look for these in your work
- Connects evidence to a revised need
- Creates alternative responses
- Retests against a criterion
Common mistakes
- Treating a design cycle as a fixed one-way list
- Writing preferences as if they were measurable requirements
- Claiming a prototype works without naming the test
What can you explain now?
Which is stronger evidence that a closure meets a brief?
Compare with the explanation
A repeatable leakage test against a stated criterion
A test connects a stated need to observable evidence; appearance alone cannot establish leak resistance.
After trying it yourself, choose your next review. This is your self-assessment.
Your review choice appears on Today. Sign in to sync it across devices.
Make it stick
Name the sequence from user research to testing, then explain how a measurable specification improves an iteration.
If you needed the solution, close it and solve the problem again from a blank page. A correct answer is stronger when you can explain the reason for each step.