Skip to topic
    ← Back to course topics

    Product Design (H406) - 8. Viability of design solutions - 8.1 How can designers assess whether a design solution meets its stakeholder requirements? — OCR A-Level Design and Technology

    Test yourself on Product Design (H406) - 8. Viability of design solutions - 8.1 How can designers assess whether a design solution meets its stakeholder requirements? with OCR A-Level practice questions.

    Start free

    7 days Premium · Then free forever · No card, no charge

    Your focus

    1. a. Critically evaluating how a design solution has met its intended requirements ,including:

    Product Design (H406) - 8. Viability of design solutions - 8.1 How can designers assess whether a design solution meets its stakeholder requirements? exam tips

    Quick Revision Summary (Key Takeaway)

    Assessing whether a design meets stakeholder requirements involves evaluating solutions against user needs, performance criteria, and commercial realities. Designers utilise iterative user testing, specialist feedback, and quantitative data collection to validate viability throughout product development.

    Topic Overview

    Assessing design viability requires rigorous validation against the needs and constraints of all stakeholders, from end-users to manufacturing engineers, distributors, and safety regulators. Within OCR A-Level Design and Technology (H406), students must understand how iterative development relies on both qualitative feedback and quantitative metrics to verify that an emerging solution fulfills its Product Design Specification (PDS).

    This topic bridges conceptual design and commercial manufacture. Mastery of stakeholder evaluation enables students to make evidence-based design iterations, justify engineering decisions in their Iterative Design Project (NEA), and critically evaluate commercial success and failure in written exam scenarios.

    Key Concepts
    • →Stakeholder Matrix: Differentiating primary end-users from secondary stakeholders (maintenance crews, manufacturing engineers, logistics partners, and retailers).
    • →Quantitative vs. Qualitative Assessment: Combining measurable engineering metrics (e.g., load capacity, cycle times, anthropometric clearance) with user experience feedback (e.g., perceived comfort, intuitive navigation).
    • →Iterative Usability Testing: Employing low- and high-fidelity physical prototypes, digital CAD simulations, and observational trials to detect failure modes early.
    • →PDS Reconciliation: Directly cross-referencing prototype performance metrics against predetermined, measurable PDS requirements.
    Examiner Tips
    • 💡Whenever discussing stakeholder evaluation, define explicit metrics such as failure rate percentages, task completion times, or anthropometric percentiles rather than general descriptors.
    • 💡Structure extended-response questions by evaluating distinct stakeholder categories: primary consumer, manufacturing operative, and service technician.
    • 💡Reference standard quality assurance and assessment frameworks such as ISO standards, failure mode and effects analysis (FMEA), or design for manufacture and assembly (DFMA).
    Common Mistakes
    • Assuming user testing only happens at the very end of the design process; in modern agile design, user and stakeholder feedback must occur iteratively at every prototyping phase.
    • Confusing subjective user opinions with rigorous ergonomics data; asking 'Do you like the grip?' is insufficient compared to measuring grip comfort using formal rating scales and anthropometric clearances.
    • Overlooking regulatory and environmental stakeholders, which leads to ignoring legal compliance testing (e.g., CE/UKCA marking, RoHS, safety directives).
    Revision Plan
    1. 1Day 1-2: Review stakeholder identification techniques and categorise stakeholders into primary, secondary, and tertiary groups.
    2. 2Day 3-4: Learn quantitative and qualitative data collection methods, focusing on user trials, Likert scales, and empirical stress testing.
    3. 3Day 5-6: Practice linking evaluation methods directly to specific PDS parameters from past exam case studies.
    4. 4Day 7: Complete timed 6-mark and 9-mark evaluation questions, ensuring both commercial and user criteria are addressed.
    Exam Question Types
    • 📋Short-answer data analysis: Calculating percentage satisfaction, mean operational times, or anthropometric range fits from stakeholder survey data.
    • 📋Explain/Describe (4-6 marks): Describing two distinct testing methodologies used to assess a specified product against stakeholder needs.
    • 📋Extended Evaluative Essays (9-12 marks): Critically assessing how a designer balances competing stakeholder requirements (e.g., consumer aesthetics vs. production cost and ease of disassembly).
    Command Word Expectations (OCR)
    Evaluate

    Make reasoned judgements based on evidence, weighing strengths and weaknesses of design validation methods against stakeholder constraints before concluding.

    Explain

    Give clear, detailed reasons and show how a testing method directly produces data to verify a stakeholder requirement.

    Discuss

    Explore multiple perspectives, typically balancing conflicting stakeholder demands such as user preference versus manufacturing feasibility.

    How Students Lose Marks (Examiner Pitfalls)
    Pitfall: Treating 'stakeholders' exclusively as end-users, ignoring other crucial parties such as manufacturers, maintenance technicians, retailers, and regulatory bodies.
    ❌ Weak Answer (Loses Marks):The designer asks users to test the prototype and fill out a survey to see if they like the product and if it solves their problem.
    Example improved answer:The designer employs triangulated testing methods across diverse stakeholder groups. End-users evaluate usability and anthropometrics via structured user trials, while production engineers assess Design for Manufacture and Assembly (DFMA) constraints to confirm production viability and unit cost targets.
    Examiner Tip: Explicitly identify at least two distinct stakeholder perspectives (e.g., end-user vs. manufacturer) to access top-band marks in evaluative questions.
    Pitfall: Providing vague qualitative descriptions such as 'it works well' rather than referencing objective, measurable criteria from the product design specification (PDS).
    ❌ Weak Answer (Loses Marks):The designer tests the kettle to see if it is hot enough and checks if the handle is comfortable for people to hold.
    Example improved answer:The kettle prototype undergoes empirical testing: water temperature is measured using digital thermometry to ensure it reaches 100 degrees Celsius within 180 seconds, and handle grip diameter is verified against 5th to 95th percentile female and male hand breadth data to satisfy quantitative ergonomics criteria.
    Examiner Tip: Always link stakeholder evaluation directly back to measurable parameters defined within the original Product Design Specification (PDS).
    Step-by-Step Worked Solutions

    Question: An ergonomic hand tool was tested by a representative sample of 40 users. 34 users confirmed that the grip diameter matched their hand dimensions comfortably. Calculate the percentage satisfaction rate and evaluate whether this satisfies standard anthropometric design criteria for the 5th to 95th percentile range.

    1. 1.Step 1: Calculate the observed satisfaction rate using the formula: (Number of satisfied users / Total sample size) * 100.
    2. 2.Step 2: Substitute values: (34 / 40) * 100 = 85.0%.
    3. 3.Step 3: Compare to the target percentile range: The 5th to 95th percentile encompasses 90% of the target population.
    4. 4.Step 4: Formulate evaluative conclusion: An 85.0% satisfaction rate falls short of the 90% required to encompass the 5th to 95th percentile, indicating that handle dimensions must be refined or offer modular adjustability.
    Final Answer: 85.0% satisfaction rate; this does not meet standard anthropometric requirements as it fails to cover the full 90% population band defined by the 5th to 95th percentiles.

    Question: Explain two methods a design team could use to gather objective feedback from stakeholders during the prototyping stage of a domestic medical device. [6 marks]

    1. 1.Step 1: Identify and detail method 1 (Empirical usability testing): Set up controlled user trials where participants complete specific tasks (e.g., loading medication). Quantify performance by recording error rates, task completion times, and physical biometric indicators.
    2. 2.Step 2: Explain stakeholder relevance for method 1: Provides empirical data on patient interaction, demonstrating whether interface requirements and human error mitigation targets in the PDS are met.
    3. 3.Step 3: Identify and detail method 2 (Focus groups with clinical experts/healthcare professionals): Conduct structured technical reviews presenting non-functional and semi-functional prototypes to nurses and doctors.
    4. 4.Step 4: Explain stakeholder relevance for method 2: Yields rigorous professional feedback regarding sanitisation protocols, regulatory compliance (e.g., MHRA/FDA standards), and integration within clinical workflows.
    Final Answer: Method 1: Empirical usability trials measuring error rates and task completion times with end-users. Method 2: Structured focus groups and technical audits with clinical healthcare professionals to verify regulatory compliance and sterile handling.
    Active Recall Memory Test
    What is the key difference between qualitative and quantitative evaluation of a prototype?
    Key Fact: Quantitative evaluation gathers measurable numerical data (e.g., mass, decibels, time), whereas qualitative evaluation captures subjective descriptive data (e.g., user opinions, comfort ratings, behavioural observations).
    Name three stakeholders other than the primary consumer who must be considered during prototype evaluation.
    Key Fact: Manufacturing/production engineers, maintenance and service technicians, and logistics/retail handlers.
    What anthropometric percentile range is standard for mass-market hand-held consumer products?
    Key Fact: The 5th to 95th percentile of the target demographic.
    Frequently Asked Questions
    What is the difference between a user and a stakeholder in A-Level Product Design?
    A user is the person who directly interacts with or operates the finished product on a day-to-day basis. A stakeholder is anyone impacted by the product throughout its entire product lifecycle, including manufacturing operatives, logistics providers, retailers, maintenance personnel, recyclers, and safety regulators. While every user is a stakeholder, not every stakeholder is a user.
    How do I evaluate stakeholder requirements in my NEA coursework?
    Throughout your Iterative Design Project (NEA), establish clear, measurable criteria within your Product Design Specification (PDS). At each prototyping iteration, present models to your identified primary user and relevant experts, recording their feedback through video trials, surveys, or measured performance tests. Document how their critiques directly shaped subsequent CAD models and design modifications.
    Why is testing with only friends and family heavily penalised in exams and NEA?
    Testing exclusively with friends and family introduces severe confirmation bias and fails to represent the true anthropometric and skill diversity of your target market. Examiners look for objective, representative sample testing that reflects target demographic percentiles (such as the 5th-95th percentile) and captures unbiased feedback from relevant technical stakeholders.
    What role does DFMA play in assessing stakeholder requirements?
    Design for Manufacture and Assembly (DFMA) evaluates the design from the perspective of the production engineer and assembly worker. It assesses whether parts can be fabricated efficiently using standard processes, whether snap-fits or standard fasteners reduce assembly time, and whether components can be oriented error-free, safeguarding commercial viability.