Teachers meet this skill early in AQA GCSE Design and Technology because it sits at the start of the iterative design process. Before students sketch, model or choose materials, they need to show that they can investigate a design situation properly, identify a genuine problem, and define the needs of a client or user clearly.
This specification point sits within 3.3 Designing and making principles and links directly to the way students gather and use evidence. In practice, that means moving students beyond vague statements like “I want to make something better” and towards sharper thinking such as who is the user, what is not working, what evidence proves it, and how should the brief change as findings emerge?
This page helps teachers teach that process with confidence and mark it consistently. It focuses tightly on what students need for AQA GCSE Design and Technology: using investigation to identify problems and needs, drawing on relevant primary and secondary data, and refining a brief when the evidence points in a clearer direction.
At a Glance
🧭 Specification context
AQA GCSE Design and Technology, 3.3 Designing and making principles
Focuses on investigating design problems and identifying client or user needs before design development
Students need to know
how to identify a design problem rather than jump straight to a solution
how primary and secondary research help reveal needs, wants and constraints
how findings shape or refine a design brief
why briefs often need adjusting as investigation develops
Typical exam focus
explaining why investigation matters
selecting relevant research methods
linking evidence to user needs
justifying changes to a brief
Common student challenges
describing methods without explaining purpose
confusing a product idea with a design problem
writing generic user needs
forgetting to use evidence to refine the brief
Understanding the Topic
What this specification point is really about
Students are not being rewarded for simply listing research methods. They need to understand why designers investigate and what that investigation should uncover.
A strong grasp of this topic means students can:
- identify an actual problem in a context rather than inventing a random product
- investigate the needs, wants and limitations of a client or user
- use evidence from research to inform design decisions
- recognise that the brief may need refining once better information is available
The core idea
In AQA terms, students should understand that investigation helps designers move from a broad situation to a focused brief.
A useful classroom sequence is:
- explore the context
- identify the problem
- investigate the client or user
- gather evidence from primary and secondary data
- identify needs and constraints
- refine the brief
What counts as useful investigation
Useful investigation is purposeful. It should help answer questions such as:
- Who is the user?
- What are they struggling with?
- What do they need the product to do?
- What conditions or limitations matter?
- What does existing product analysis reveal?
- What should now change in the brief?
Primary and secondary data in this topic
Primary data is collected first-hand.
Examples include:
- interviews
- questionnaires
- observations
- user trials
- measurements linked to ergonomics or anthropometrics
- product testing with target users
Secondary data comes from existing sources.
Examples include:
- product reviews
- existing product research
- catalogues and manufacturer information
- published dimensions or guidance
- trend research
- design movement or market information where relevant
Students should see that the best investigation often combines both. A questionnaire might reveal user preferences, while existing product analysis may reveal what already works well and what repeatedly fails.
From findings to a refined brief
This is often the missing link in weaker answers. Students may collect information but fail to use it.
Teachers should push students to complete the sentence:
“Because the investigation showed ..., the brief should now ...”
For example:
- because users need quicker access with one hand, the brief should prioritise simple opening mechanisms
- because existing products are too bulky for school bags, the brief should emphasise compact dimensions
- because anthropometric data shows hand size variation, the brief should account for a suitable range of users
📌 Teacher reminder
If students cannot point to evidence, they are usually giving assumptions dressed up as design decisions.
Key Terms and Concepts
| Term | Explanation |
|---|---|
| Design problem | A need, issue or gap that requires a design response. It is the problem to solve, not the finished product idea. |
| Client | The individual or organisation asking for the design solution. |
| User | The person or group who will actually use the product. |
| Need | An essential requirement the design must meet. |
| Want | A preference that may improve appeal but is less essential than a need. |
| Primary data | Information collected first-hand, such as interviews, observation or testing. |
| Secondary data | Information gathered from existing sources, such as product research or published data. |
| Anthropometric data | Measurements of the human body used to help design for size, reach or fit. |
| Ergonomics | Designing products so they are comfortable, efficient and safe to use. |
| Design brief | A short statement outlining what is to be designed and for whom. |
| Refining the brief | Adjusting the brief when investigation reveals clearer or more accurate user needs. |
How to Teach This Topic
Classroom priorities
👩🏫 Teaching moves that work well
start with a poor product or awkward user scenario
ask students to identify the problem before suggesting solutions
model the difference between a vague and precise design brief
make students rank needs versus wants
insist that every design decision links back to evidence
📝 Useful classroom outputs
user profile sheets
interview question sets
observation records
existing product comparison charts
“original brief” and “refined brief” comparison tasks
A practical teaching sequence
- Begin with context, not solutions
Give students a design context such as storage in a small study space, packaging for a fragile product, or an aid for carrying equipment safely.
Ask:
- What is the actual problem here?
- Who is affected by it?
- What evidence would we need before designing anything?
- Teach the difference between needs and wants
Students often write everything as a need.
Try a quick sorting task:
- Need: must be safe, fit the user, function reliably
- Want: should look modern, match room décor, use a certain colour
That distinction improves both briefs and justification.
- Model research methods with purpose
Rather than asking students to list methods, ask them to complete:
- interviews are useful because ...
- observation helps because ...
- product analysis reveals ...
- anthropometric data matters because ...
This keeps the focus on what each method uncovers.
- Use existing products intelligently
Have students compare two or three existing products and evaluate:
- strengths
- weaknesses
- user suitability
- size and ergonomic fit
- features worth adapting or avoiding
This helps students identify gaps in the market or design opportunities.
- Refine the brief out loud
After research, display the first brief and ask the class what now needs changing. This is the moment where the topic becomes more than note-taking.
A refined brief should usually become:
- more specific
- more user-focused
- more realistic
- more clearly linked to evidence
Discussion prompts
- What is the difference between a design problem and a design idea?
- Why might a client request lead to a poor product if the designer skips investigation?
- When should a brief be changed?
- Which research method would best reveal comfort, fit or ease of use?
Scaffolding ideas
- provide sentence starters for justification
- use a grid with columns for evidence, what it shows, and impact on brief
- give students an over-general brief and ask them to sharpen it using data
- provide mixed examples of assumptions and evidence, then sort them
Extension tasks
- ask students to critique whether a given research plan is balanced enough
- introduce percentile data and ask which user range should be prioritised
- compare two refined briefs and decide which is better evidenced
💡 A handy teacher line
“If the research would not change the brief, it probably was not worth doing.”
How to Mark This Topic Effectively
What strong answers usually contain
Strong responses typically:
- focus on the user or client clearly
- explain how investigation identifies real problems and needs
- refer to appropriate research methods rather than random ones
- link findings to specific design implications
- explain why a brief may need to be modified or refined
What weaker answers usually do
Weaker responses often:
- stay generic and say research is useful “to get ideas”
- list methods without explaining what they reveal
- confuse needs with preferences
- jump from problem to solution too quickly
- ignore the role of evidence in shaping the brief
What to reward
| Feature in the answer | Reward when you see |
|---|---|
| Clear problem focus | Accurate identification of the issue to be solved rather than a vague product statement. |
| Relevant research choice | Selection of methods that match the design context, such as observation for use issues or anthropometric data for fit. |
| Evidence-led reasoning | Explanation of what the research shows and why it matters. |
| User-centred thinking | Reference to client or user needs, comfort, safety, access, size or function. |
| Refinement of the brief | Recognition that investigation leads to changes or sharper focus in the brief. |
Quick marking checks
Use these questions when reading a response:
- Has the student identified a problem rather than only naming a product?
- Has the student used research methods appropriately?
- Is there a clear link between evidence and the brief?
- Has the student shown why needs matter more than guesses?
✅ Marking tip
Reward specificity. “Ask users questions” is weaker than “interview target users to identify storage problems, access needs and size limitations”.
Example Student Responses
Example question
A student is designing a storage product for pupils who have limited desk space at home.
Question: Explain why investigating design problems and needs is important before writing or refining a design brief.
Marks: 6
Marking guidance
Award credit for points such as:
- identifying the real problem before proposing solutions
- understanding user or client needs
- using primary or secondary data to gather evidence
- identifying constraints such as size, safety or ease of use
- refining the brief based on findings
- improving the suitability of the final design outcome
**Strong response**
Investigating design problems and needs helps the designer understand what the user actually requires instead of making assumptions. In this case, pupils with limited desk space may need storage that is compact, easy to reach and suitable for different items. Interviews and observation could show what causes clutter, while product analysis could reveal why existing storage is too large or awkward. This information helps the designer write a more accurate brief and refine it if the first idea is too broad. As a result, the final product is more likely to meet the user’s needs.
Why this is strong
- focuses clearly on the user and the problem
- uses relevant research methods
- explains what those methods reveal
- links findings to refining the brief
- stays analytical rather than descriptive
**Weak response**
Investigating is important because designers need ideas. They can do questionnaires and look online. This helps them make a product that looks good and that people like. Research is useful because it gives information and then they can start designing.
Why this is weak
- too generic and lacks a precise design problem
- names methods but does not explain what they reveal
- focuses on “ideas” and appearance more than needs
- does not explain how the brief would improve
- gives little evidence of AQA-style user-centred reasoning
Practice Questions
Question 1
Explain two ways primary data can help a designer identify user needs more accurately.
Marks: 4
Marking guidance
- 1 mark for identifying a relevant way primary data is gathered or used
- 1 mark for explaining how it helps identify needs
- repeat for the second developed point
Question 2
A designer has written an initial brief for a lunch container for students. Describe how investigating existing products could help refine that brief.
Marks: 6
Marking guidance
- reward analysis of strengths and weaknesses in current products
- reward reference to user needs such as portability, leakage, storage and cleaning
- reward explanation of how evidence changes or sharpens the brief
Question 3
Assess which research method would be most useful when designing a handheld product for a range of users.
Marks: 8
Marking guidance
- reward justified method choice
- credit use of anthropometric or ergonomic thinking where relevant
- reward comparison of methods, not just description
- reward a supported judgement
Question 4
Why might a designer need to modify a brief after carrying out investigation?
Marks: 6
Marking guidance
- reward recognition that early assumptions may be incomplete or inaccurate
- reward links to user feedback, product analysis or measured data
- reward explanation of how the revised brief becomes more focused and suitable
🧪 Revision idea
Ask students to take a weak design brief and improve it using three pieces of investigation evidence. It is excellent training for both exam answers and NEA thinking.
Common Misconceptions
- “Investigation is just a box-ticking exercise.”
- Correction: investigation should directly shape the brief and later design decisions.
- “The design problem is the same as the solution.”
- Correction: the problem is the issue to solve. The solution comes later.
- “Questionnaires are always the best method.”
- Correction: the best method depends on what needs to be discovered.
- “Needs and wants are basically the same.”
- Correction: needs are essential requirements. Wants are preferences.
- “Once the brief is written, it should not change.”
- Correction: good designers refine the brief when evidence reveals a better direction.
- “More research automatically means better research.”
- Correction: relevant, focused evidence is more useful than a large pile of unfocused notes.
FAQ
**How much detail do students need when describing research methods?**
Enough to explain why the method is suitable and what it reveals. A named method on its own is rarely enough for stronger marks.
**Should students always use both primary and secondary data in an answer?**
Not always in one short exam response, but they should understand the difference and be able to use either appropriately. The strongest understanding usually recognises the value of both.
**What is the easiest way to improve weak answers on this topic?**
Train students to link every piece of research to a finding and then to a change in the brief. That one chain often lifts an answer noticeably.
**How can I stop students writing vague briefs?**
Make them define the user, problem, context and key needs before they write the brief. If any of those are missing, the brief is probably still too woolly.
**Where do ergonomics and anthropometrics fit here?**
They fit when students are investigating user size, comfort, reach, grip or fit. They help students justify design needs with measurable evidence.
**Is this only relevant to exam questions, or does it help NEA thinking too?**
Both. The specification point supports exam performance, but it also builds the habit of evidence-led design thinking that strengthens project work.
Smarter marking starts here
Marking.ai helps teachers turn strong subject knowledge into faster, more consistent marking. Once students are writing clearer, better-evidenced Design and Technology answers, Marking.ai can help you assess them efficiently while keeping feedback specific and useful.
A little less time wrestling with piles of scripts is rarely bad design thinking.