IB MYP Design: The Design Cycle

This guide covers the design cycle, the repeated methodology every project in IB Middle Years Programme Design is built around. The full syllabus guide confirms each of the four assessment criteria maps directly onto one stage of the cycle, alongside the Criteria in Practice guide already on the site.

Where this fits in the subject

The design cycle is used to structure inquiry, analyse a problem, develop a feasible solution, create it, then test and evaluate it. It is not followed once per year; it is the working structure applied to every project across the course. Because each criterion is one cycle stage made assessable, mastering the design cycle and mastering the four assessment criteria are the same task viewed from two angles.

The four stages, mapped to the four criteria

Design cycle stage	Assessment criterion	What it involves
Problem stage	A: Inquiring and analysing	Identify a problem needing a solution, analyse the need, inquire into its nature
Specification stage	B: Developing ideas	Write a detailed specification, present the proposed solution
Build stage	C: Creating the solution	Plan the creation, follow the plan to build a testable prototype
Test stage	D: Evaluating	Design tests, carry them out, objectively evaluate success and impact

Worked example: applying the cycle to a design situation

A design situation asks students to solve a problem for a specific client – for example, a storage solution for a small space. At Stage A (inquire), the student identifies the client’s actual need, researches existing solutions, and analyses what a genuine solution requires. At Stage B (develop), the student writes a detailed specification – size, materials, budget, constraints – and presents a proposed solution against it. At Stage C (create), the student plans the build sequence, then follows the plan to produce a prototype sufficient for testing. At Stage D (evaluate), the student designs and carries out objective tests against the original specification, honestly identifies limitations, and explains the solution’s impact on the client.

Documentation matters more than the finished product

Because the ePortfolio is assessed as a complete design folder, not a single final product, documenting the process at every stage – not just presenting a finished prototype – is where most marks actually sit. A polished product with thin process documentation across stages A and B typically scores lower than a rougher prototype backed by thorough inquiry, specification and evaluation.

Honest evaluation is rewarded, not penalised

Stage D specifically requires objective testing and an honest account of limitations. Resist the instinct to only showcase what worked – transparently identifying real weaknesses and explaining how a solution could be improved is exactly what this stage rewards, not a claim that the solution is already perfect.

Connecting to the DP pathway

MYP Design eAssessment tasks are explicitly aligned with the skills that prepare students for the DP Design Technology course. Building genuine fluency with the design cycle at MYP level – particularly the habit of documenting inquiry and specification thoroughly, not just presenting a finished product – pays forward directly if a student continues design at Diploma level, where the same cyclical process underpins coursework there too.

How to approach it

Learn the four design cycle stages in order, alongside the criterion each one maps to, since confusing which criterion corresponds to which stage undermines documentation planning for the whole project. For any current project, check that documentation exists for all four stages, not just the finished product, and treat the cycle as the repeated working structure for every project rather than a single introductory unit covered once and then set aside. Practise writing an honest, objective evaluation that names real limitations, not just successes, since Stage D specifically rewards this transparency.

Common mistakes

Treating the design cycle as a one-off introduction rather than the repeated structure every project uses. Submitting a polished final product with thin documentation of the inquiry and specification stages. Presenting only successes in the evaluation stage instead of an honest, objective account of the solution’s limitations. Confusing which criterion maps to which stage when planning documentation.

Design’s role in the MYP certificate

Design is one of the subjects the MYP certificate accepts as satisfying its arts/practical requirement – the certificate requires a satisfactory level of achievement in at least one course from physical and health education, arts, or design. For students taking design specifically to meet this requirement, a genuinely well-documented ePortfolio carries weight beyond the subject’s own grade, since it directly affects whether the broader certificate requirement is satisfied.

Why the cycle repeats rather than runs once

A student who only encounters the design cycle in an introductory unit at the start of the course, and then treats subsequent projects as simply “making things,” misses the point of the cycle’s repetition: each new project is a fresh opportunity to apply and strengthen the same four-stage process against a new problem, and the criteria are reassessed every time. Revising the design cycle is therefore not a one-time task completed early in the course – it is a working habit that should be reinforced and checked against on every project, since weak documentation habits established early tend to persist into later, more complex projects unless they are actively corrected.

Official syllabus

International Baccalaureate Organization, Middle Years Programme Subject Brief – Design, from 2014, (c) 2015 – the same source already cited by the full syllabus guide and the revision notes already on the site. Verified 2026-09-06.