Skip to main content
ScotlandDesign and ManufactureSyllabus dot point

How does a designer evaluate a proposal against the specification and resolve it into a final design?

Evaluating and resolving design proposals: testing ideas and models against the specification, using objective and subjective evaluation, identifying improvements, and refining a proposal on an ongoing basis until it is resolved and meets the brief.

A focused answer to the SQA National 5 Design and Manufacture content on evaluating and resolving design proposals, covering objective and subjective evaluation against the specification, identifying improvements, and refining a design until it is resolved.

Generated by Claude Opus 4.811 min answer

Reviewed by: AI editorial process; not yet individually human-reviewed

Have a quick question? Jump to the Q&A page

Jump to a section
  1. What this dot point is asking
  2. Evaluate against the specification
  3. Objective and subjective evaluation
  4. Gathering user and client feedback
  5. Identifying improvements and resolving
  6. Try this

What this dot point is asking

The SQA wants you to know how a designer evaluates a proposal and resolves it into a final design. Evaluation is not a one-off step at the end: it happens throughout the process, and a proposal is only resolved when it meets every point of the specification and the original brief.

Evaluate against the specification

The specification is the standard the proposal is judged against. Good evaluation checks the proposal point by point: does it meet the required size, cost, function, materials, safety and finish? Judging a design on opinion alone is weak; judging it against the measurable specification is what earns marks.

Objective and subjective evaluation

A full evaluation uses both: some specification points (size, strength, cost) are measurable and judged objectively, while others (aesthetics, comfort) are matters of opinion judged subjectively, often by gathering user and client feedback.

Gathering user and client feedback

Subjective evaluation is only as good as the people asked. A designer gathers honest feedback from the target user and the client - through trying the model, answering a short questionnaire, or being observed using it - rather than relying on the designer's own opinion. User feedback is most useful for factors the designer cannot measure: whether the product is comfortable, easy to understand and attractive, and whether it actually solves the user's problem. The designer then weighs this feedback alongside the objective test results when deciding what to improve.

Identifying improvements and resolving

When a test shows a point is not met, the designer:

  1. Identifies exactly what is wrong (e.g. the model is too weak, too large, slides off).
  2. Refines the design to fix it (change material, shape, size or detail).
  3. Re-tests the improved version against the specification.

This loop repeats - the iterative process - until the proposal meets every point. At that stage the design is resolved: it fully satisfies the specification and the brief and is ready to take forward to manufacture.

Try this

Q1. State what a designer evaluates a proposal against. [1 mark]

  • Cue. The design specification (and the original brief).

Q2. Give one example of an objective test and one of a subjective evaluation for a chair. [2 marks]

  • Cue. Objective: measure whether it supports a stated weight without breaking. Subjective: ask users whether they find it comfortable and attractive.

Q3. Explain what it means for a design to be resolved. [2 marks]

  • Cue. It has been refined through evaluation until it meets every point of the specification and the brief, so it is ready for manufacture.

Exam-style practice questions

Practice questions written in the style of SQA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.

SQA-style Explain4 marksExplain how a designer would evaluate a design proposal during the design process.
Show worked answer →

Award up to 4 marks for explained points. The designer tests the proposal or model against each point of the specification, so success is judged against agreed measurable requirements rather than opinion (1). Objective evaluation uses measurement and testing (for example, checking a dimension or load) to give factual results (1). Subjective evaluation gathers opinions from the user or client about appearance and comfort, which matters for factors such as aesthetics (1). Where a point is not met, the designer identifies the improvement needed and refines the design, then re-tests, continuing until the proposal is resolved (1). Markers reward the link to the specification and the use of both objective and subjective evaluation.

SQA-style Describe3 marksDescribe the difference between objective and subjective evaluation, with an example of each.
Show worked answer →

Award up to 3 marks: 1 for the distinction and up to 2 for examples. Objective evaluation is based on facts that can be measured or tested, so the result is the same for anyone, for example measuring whether a shelf holds a 5 kg load without bending (1 distinction, 1 example). Subjective evaluation is based on personal opinion and feeling, which can differ from person to person, for example asking users whether they like the colour and find the product comfortable (1 example). A full evaluation uses both, because some factors (size, strength) are measurable while others (appearance, comfort) are matters of opinion. Markers reward the fact-versus-opinion contrast with a relevant example each.

Related dot points

Sources & how we know this