Welcome to Criterion B: Developing Ideas

Welcome to one of the most creative and rewarding parts of the MYP Design cycle! In Criterion A (Inquiring and analysing), you investigated a real-world problem, researched existing products, and wrote a design brief. Now, you are stepping into Criterion B: Developing ideas.

Before you start sketching or building, you need a precise blueprint of what your solution must achieve. This chapter focuses on Strand i of Criterion B: developing a design specification that clearly states the success criteria for your solution.

Don't worry if this seems a bit formal at first. Think of a design specification as your project's personal checklist for success. It tells you exactly what your product or digital solution needs to do, how it must perform, and how you will know it actually works!

Note: The other parts of Criterion B — generating feasible ideas, selecting and justifying your final design, and creating planning drawings or diagrams — are explored in detail in the companion chapters of this section.

What is a Design Specification?

A design specification is a structured list of specific, measurable requirements and constraints that your solution must satisfy. It defines the exact success criteria against which your final product or system will be tested and judged.

Design Brief vs. Design Specification: What is the Difference?

A very common mix-up in MYP Design is confusing the design brief with the design specification. Here is how they differ:

• Design Brief (Criterion A): A broad statement written at the end of your inquiry. It defines the problem, identifies the client or target audience, and summarizes what kind of solution is needed based on your research findings.
• Design Specification (Criterion B): A detailed set of explicit, testable conditions and performance targets derived directly from your research. It specifies the exact limits, dimensions, functions, and qualities the final design must meet.

Everyday Analogy: Imagine ordering a birthday cake.
• The Brief: "I need a fun, celebratory birthday cake for my 12-year-old sister who loves chocolate."
• The Specification: "The cake must be entirely nut-free; it must measure no more than \(25\text{ cm}\) in diameter to fit the cake stand; it must serve at least 10 people; and it must include chocolate frosting that stays firm at room temperature (\(21^\circ\text{C}\))."

Key Takeaway: The brief explains what the goal is and who it is for; the specification provides the exact rules and targets that will determine whether the solution succeeded.

Understanding Success Criteria

Success criteria are the individual, measurable targets within your specification. If your finished solution meets these criteria, your project is a success!

Vague Criteria vs. Measurable Criteria

The biggest challenge students face when writing specifications is being too vague. A criterion must be specific enough that anyone could test your product and give a clear "yes" or "no" as to whether it met the standard.

Let's look at how to transform weak, vague statements into strong, measurable success criteria:

• Weak / Vague: "The website must look nice."
• Strong / Measurable: "The website must follow a high-contrast colour palette (dark text on a light background) with standard body text of at least \(16\text{ px}\) so that \(100\%\) of surveyed target audience members report it is easy to read."

• Weak / Vague: "The storage box must be strong."
• Strong / Measurable: "The storage box must support a downward load of at least \(5\text{ kg}\) without buckling or showing visible deflection greater than \(2\text{ mm}\)."

• Weak / Vague: "The app must be easy to use."
• Strong / Measurable: "A first-time user from the target audience must be able to complete account registration and reach the main dashboard within \(60\text{ seconds}\) without adult assistance."

Quantitative vs. Qualitative Criteria

To create a balanced specification, include both types of criteria:

1. Quantitative Criteria: Targets based on numbers, physical measurements, and hard data (e.g., dimensions in \(mm\), mass in \(g\), load capacity in \(kg\), load times in seconds, or budget limits in currency).
2. Qualitative Criteria: Targets based on user experience, aesthetic qualities, or sensory feedback (e.g., user satisfaction ratings from a survey, consistency of branding, or visual clarity). To make these measurable, connect them to a survey, rating scale, or clear checklist.

Key Takeaway: If a criterion cannot be tested with data, a measurement tool, or an authentic user survey, it is not ready for your specification.

Success Criteria Across the Design Strands

In MYP Design, your school offers one of three formal strands. Your success criteria will naturally reflect the strand you are working in:

1. Product Design (Physical Artefacts)

In product design, your criteria focus on physical characteristics, materials, and functional performance. Examples include:

• Dimensions: "The desk organizer must fit within a maximum footprint of \(200\text{ mm} \times 150\text{ mm}\)."
• Material Properties: "The outer shell must be made from non-toxic, moisture-resistant material suitable for bathroom use."
• Weight & Portability: "The product must have a total mass of under \(400\text{ g}\) so it can be carried easily in a school bag."

2. Digital Design (Digital Artefacts & Systems)

In digital design, your criteria focus on interactivity, interface design, performance, and functionality. Examples include:

• Compatibility: "The web application must render correctly and maintain responsive layout across modern desktop and mobile browsers."
• Navigation & Speed: "Every main page must load in under \(2\text{ seconds}\) on a standard broadband connection."
• Data Handling: "The system must validate user email input and display an error message if the '@' symbol is missing."

3. Combined Digital and Product Design

In combined design, your solution includes both a physical component and a digital component working together. Examples include:

• Hardware-Software Integration: "The physical housing must protect the microcontroller from moisture while allowing a USB connection to pass through."
• System Feedback: "When the physical push button is pressed, the digital display must update its count within \(0.5\text{ seconds}\)."

Developing and Justifying Your Specification

To reach the highest achievement levels (Levels 7–8) in MYP Year 5, you cannot simply write down a random list of requirements. You must develop design specifications that clearly state the success criteria and justify why each criterion is necessary, linking back directly to your research from Criterion A.

The Command-Term Ladder

The MYP assessment criteria follow a clear progression of command terms as you advance through the years and achievement bands:

• States: Gives a simple name or brief value without explanation (e.g., "The box must be \(15\text{ cm}\) wide"). This reflects lower achievement levels or earlier MYP years.
• Outlines: Gives a brief summary of the essential features.
• Explains: Gives a detailed account including reasons, causes, or connections.
• Justifies: Proves or supports your choices with valid evidence, data from research, or client needs. This is essential for top marks in Year 5!

The "Target + Justification + Test Method" Framework

A proven way to structure each specification point in your ePortfolio folder is using this three-part formula:

1. The Criterion (The Target): What exact requirement must the design meet?
2. The Justification (The 'Why'): What specific primary or secondary research finding from Criterion A proves this requirement is necessary for the client or problem?
3. The Verification Method (The 'How to Test'): Exactly how will you test or measure this in Criterion D?

Full Example for an ePortfolio:
• Criterion: The reading lamp base must not tip over when tilted up to an angle of \(15^\circ\).
• Justification: My client interview in Criterion A showed that the client's desk is frequently bumped during study sessions. Secondary research on domestic stability standards indicates a \(15^\circ\) tilt threshold prevents accidental falls.
• Verification Method: Place the finished lamp on an adjustable inclined plane, increase the tilt to \(15^\circ\), and record whether it remains stable or tips over.

Great specifications show a deep understanding of the big ideas in Design. You can use MYP concepts to inspire thoughtful specification points:

• Ergonomics (Related Concept): How does the solution fit human anatomy, comfort, and ease of use? (e.g., grip size, button spacing, text legibility).
• Sustainability (Related Concept): What impact will materials, energy consumption, or disposal have on the environment? (e.g., recyclable materials, minimal waste during production).
• Systems (Key Concept): How do the different parts of your solution interact with each other and with the environment? (e.g., how the software sends data to the hardware, or how modular parts assemble).
• Innovation & Adaptation (Related Concepts): Does the specification require adapting an existing idea to solve a new challenge for your specific community?

The Golden Thread: Linking Criterion B to Criterion D

Always remember: You cannot evaluate what you did not specify!

In Criterion D (Evaluating), strand ii requires you to critically evaluate the success of the solution against the design specification, based on authentic product testing.

If your specification in Criterion B says something vague like "The product must look nice," when you reach Criterion D, you will have no real way to test it with authentic data. However, if your specification says "At least \(80\%\) of 10 surveyed target audience members must rate the color palette as 'professional and calming' on a 5-point Likert scale," you have an authentic, data-driven test ready to go!

Writing a rigorous specification right now makes your future work in Criterion D straightforward and high-scoring.

Common Pitfalls to Avoid

Keep these frequent traps in mind while writing your design specification:

• The "Pre-Determined Solution" Trap: Writing a specification that describes one specific idea before brainstorming (e.g., "Must be made of red pine with two brass hinges"). Keep your criteria focused on performance and function so that you can still explore a wide range of feasible ideas in the next strand.
• Untestable Descriptors: Using subjective words such as "stylish," "cool," "fun," "cheap," or "sturdy" without defining a measurable target or survey rating.
• Ignoring Research Findings: Listing requirements out of thin air rather than citing your surveys, interviews, existing product analyses, or ergonomic charts from Criterion A.
• Forgetting Constraints: Omitting real-world limits like available workshop tools, software platforms, budget, safety rules, or the project deadline.

Chapter Review & Checklist

Before moving on to generating design ideas, verify your specification against this quick checklist:

• Is your specification distinct from your design brief?
• Does every criterion have a clear, measurable target (quantitative or qualitative)?
• Have you justified each criterion by citing evidence or findings from Criterion A?
• Are the criteria suitable for your formal strand (product, digital, or combined)?
• Does each criterion outline a realistic method for testing and evaluation in Criterion D?
• Have you avoided locking yourself into one specific design before exploring creative alternatives?