IB MYP Design: The Design Cycle — Revision Notes

The full syllabus guide confirms each of the four assessment criteria maps directly onto one stage of the design cycle. These notes cover the design cycle itself, alongside the assessment revision notes and ePortfolio exam preparation already on the site.

The cycle is not a one-off sequence

The design cycle is the repeated methodology every design project in the course is built around — 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.

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

Because each criterion IS one cycle stage made assessable, revising “the design cycle” and revising “the four criteria” are the same task viewed from two angles — master one and you have effectively mastered the other.

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).

Stage A (inquire):    identify the client's actual need, research
                       existing solutions, analyse what a genuine
                       solution requires
Stage B (develop):    write a detailed specification (size, materials,
                       budget, constraints) and present a proposed
                       solution against it
Stage C (create):     plan the build sequence, then follow the plan to
                       produce a prototype sufficient for testing
Stage D (evaluate):   design and carry out objective tests against the
                       original specification, honestly identify
                       limitations, explain 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.

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.

Quick revision checklist

• Learn the four design cycle stages in order, alongside the criterion each one maps to.
• For any past or current project, check that documentation exists for all four stages, not just the finished product.
• Practise writing an honest, objective evaluation that names real limitations, not just successes.
• Treat the design cycle as the repeated working structure for every project, not a single introductory unit.

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.

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.

Self-test

1. Name the four stages of the design cycle in order.
2. Which assessment criterion corresponds to the “build” stage?
3. Why does documentation of the process matter as much as the finished prototype?
4. What does Criterion D specifically require, beyond simply testing the solution?
5. Is the design cycle followed once per year or repeatedly across projects?

Answers: 1. Inquiring and analysing, developing ideas, creating the solution, evaluating. 2. Criterion C: Creating the solution. 3. Because the ePortfolio is assessed as a complete design folder, and thin documentation of the inquiry and specification stages (A and B) can lower the score even for a polished final product. 4. An objective, honest account of the solution’s limitations and its impact on the client or target audience, not just confirmation that tests were carried out. 5. Repeatedly — it is the working structure applied to every design project, not a one-off sequence.