Yes: a G1 Design and Technology student can turn testing into a useful design change when the test checks one stated requirement, records what actually happened and leads to a decision the student can explain. “It works” is not enough. The useful learning is the chain from purpose to evidence to change.
Try this next: ask the student to finish one sentence before touching the prototype: “I am testing whether ___, because the user needs ___.” Then run one fair check, record the result and choose only one change. This small pause stops random tinkering and makes the reasoning visible.
Tuition can help by diagnosing where that chain breaks—an unclear requirement, a weak test, an observation without evidence, or a change unrelated to the result. It must not design, make or write assessed coursework for the student. The school supervises the project, and the student must remain the author of every design decision.
Parent orientation
- Subject level: G1 Design and Technology, not Posting Group 1.
- Reader job: help a student use a prototype test to justify one improvement.
- Bring: the school brief, the student’s own requirement, prototype, test notes and teacher feedback.
- Boundary: confirm that the school offers the subject and follow its rules for project work.
What this guide covers
- Diagnose the real testing gap
- Use the five-step evidence loop
- See a phone-stand example
- Use critique without taking over
- Protect coursework ownership
- Check the 2027 G1 syllabus
- Check independent progress
First diagnose what “testing” currently means
Two prototypes can look equally unfinished while hiding very different learning needs. One student may not know what the design must achieve. Another may know the requirement but choose a test that cannot answer it. A third may collect evidence and still make a cosmetic change that does not respond to the result. Giving all three students more making time will not repair the same gap.
A quick diagnosis uses the student’s own work. Ask four questions: What user need are you addressing? Which requirement are you testing? What result would count as acceptable? What will you do if the result falls short? A student who can point to the prototype but cannot answer these questions is not yet ready for a useful test.
Parents can listen for vague words such as “better”, “stronger” or “nicer”. These are not wrong, but they need an observable meaning. “Stronger” might mean the stand supports a particular phone for thirty seconds without bending. “Easier to use” might mean a user can insert and remove the phone with one hand. A tutor’s job is to help the student make the requirement testable, not supply the requirement.
Use a five-step loop: requirement, test, observation, decision, change
The most useful routine is short enough to repeat and strict enough to prevent guesswork.
- Name one requirement. State what the product must do for the intended user.
- Choose a matching test. The action must produce evidence about that requirement, not about a different feature.
- Record an observation. Write what happened, including a number, duration, location or user response where useful.
- Make a decision. Keep, modify or reject the feature, and connect the decision to the observation.
- Make one purposeful change. Change the feature most likely to improve the tested requirement, then test again.
This is deliberate practice because the student receives information from the result, repairs one decision and repeats the check. It is not endless polishing. Keeping one variable reasonably stable also makes the result easier to interpret. If the student changes the base width, material and angle at once, a successful retest cannot show which change mattered.
The loop also improves communication. Instead of “I changed it because it fell over”, the student can explain: “The stand failed the stability requirement when the phone was tapped from the side. I widened the base while keeping the support angle the same, then repeated the same test.” That sentence contains purpose, evidence, control and evaluation.
Worked example: testing a simple phone stand
Imagine that a student is developing a phone stand for a family member who follows recipes in a small kitchen. One requirement is that the stand should remain stable when the screen is tapped. The first prototype looks attractive, but the base is narrow.
A weak test is to place the phone on the stand and say, “It can hold the phone.” That checks basic support, not stability during use. A better test places the intended phone on the stand, taps three screen positions using a consistent action and records whether the stand slides, tips or stays in place.
| Step | Student record |
|---|---|
| Requirement | The stand remains stable during ordinary screen taps. |
| Test | With the phone in place, tap the top, centre and lower screen once each. |
| Observation | The stand stayed upright for the lower and centre taps but tipped backwards after the top tap. |
| Decision | Modify the base because the failure occurred when the force acted higher above it. |
| One change | Extend the rear support while keeping the viewing angle unchanged, then repeat the test. |
The first retest may still fail. That is not wasted work. A failure becomes useful when it narrows the explanation and informs the next decision. The student might discover that base width is not the only issue: the centre of mass, surface friction or joint stiffness could also matter. The sequence should remain the student’s investigation, with school requirements guiding what may be made and recorded.
Notice what has not happened. Nobody has handed the student a finished answer. The tutor has helped frame a question, control the comparison and connect evidence to a design choice. The student still chooses, makes, tests and explains.
How critique can sharpen decisions without taking over
If a provider genuinely offers this subject and a three-student group is suitable, a compact critique can be useful. Each student gets one minute to state a requirement and test. The other two may ask only clarifying questions: “What result would count as success?”, “Does that test match the user’s need?” or “Which variable are you changing?” They must not redesign the product for the presenter.
This conditional format gives the student an audience and exposes hidden assumptions. It is not automatically better than individual teaching, and it should not become a contest for the cleverest idea. The measure is whether the original student can revise the plan and explain the decision independently.
A tutor can also use contrasting examples that are unrelated to the assessed project. For instance, compare two mock test plans for a book stand or cable organiser. Students can judge which plan yields useful evidence without sharing or copying one another’s coursework solutions.
Protect the student’s ownership of assessed work
Design and Technology includes practical decisions that may contribute to school-supervised assessment. Useful support teaches transferable processes on fresh examples: turning a need into a requirement, planning a fair test, making accurate observations, comparing evidence and explaining a decision. It does not produce the student’s project concept, drawings, prototype, testing record or written evaluation.
- Appropriate: ask questions, model a method on an unrelated object, teach safe reasoning, and help the student interpret teacher feedback.
- Not appropriate: supply a project solution, rewrite the evaluation, fabricate results, alter school records, or make components for submission.
- When uncertain: stop and ask the school what external support is permitted.
Safety and access matter too. Testing materials, tools and mechanisms must follow the school’s instructions. A tuition setting should not recreate workshop activity it is not equipped or authorised to supervise.
How this aligns with the 2027 G1 syllabus
For candidates using the 2027 G1 Design and Technology syllabus K124, SEAB describes designing and prototyping as an iterative process. The official document includes investigation of needs, evidence-based decisions, mock-ups or prototypes to test ideas, and evaluation that leads to refinement. It also identifies an individual design project with school supervision over a specified period.
Parents should open the exact year-specific document in the official 2027 G1 syllabus directory and read the G1 Design and Technology K124 syllabus PDF. Confirm the child’s registered subject, school offering, project instructions and examination year; G1 is a subject level, not a Posting Group.
The nearby guide How Can G1 Design and Technology Tuition Help My Child Improve a Prototype? owns the broader tuition question. This article has a narrower job: converting one test result into one justified change. For other verified routes, use the G1 section of the complete syllabus and learning directory.
What independent progress should look like
Do not judge progress from a more polished prototype alone. After guided practice, give the student a fresh, unrelated design situation and ask for a short test plan without prompts. Then check the same skill again several days later.
- The requirement is linked to a real user or purpose.
- The proposed test actually checks that requirement.
- The result is recorded as an observation, not rewritten to fit a preferred answer.
- The chosen change responds to the evidence.
- The student can explain what stayed the same and what changed.
If the student can perform this loop only beside the original prototype, the knowledge has not transferred yet. Use another everyday object, reduce the prompts and repeat after a delay. If the student can explain a failed test calmly and propose a targeted retest, that is meaningful progress—even before the product succeeds.
Parent next step: bring one student-authored test record to the next conversation. Ask the student to point to the requirement, result and resulting change. If any link is missing, practise that link on an unrelated example before returning to the school project.
Return to the learning and mastery expansion · Browse G1 guides

