Metacognition in the MYP Design Cycle

‍

‍

‍

‍

‍

The Gap Between Doing and Thinking

A Year 4 learner at age 15 sits down to design a water filter. She has the project brief: "Create a low-cost filtration system for a school in Kenya using locally available materials." She researches for three days, sketches five ideas, picks one, and builds it. Her prototype works. Her grade is high.

In the metacognitive version of the same project, the learner maps what she knows, what she thinks she knows, and what she needs to find out before research begins. As she develops ideas, she pauses after each iteration to ask: "Am I solving the brief, or have I drifted into a problem I prefer?"

When she builds, she records each major decision and its trade-off. At the end, she does not write "This went well". She writes: "I initially assumed water pressure was unlimited. When I discovered it was not, I had to simplify the filter design. If I redesigned tomorrow, I would..."

The procedural version completes a checklist. The metacognitive version learns how to think like a designer. Learners can then carry that thinking into science practicals, geography fieldwork, and real-world problem-solving.

Many MYP Design teachers teach the procedural version. The Design Cycle sits in the curriculum as a sequence of phases: Inquiring and analysing, Developing ideas, Creating the solution and Evaluating. Learners move through it, but they rarely pause to examine their own thinking at each stage. That weakens the promise of the MYP Design curriculum and the IB Learner Profile attribute of "Reflective", the commitment to "thoughtful consideration of the world and our own ideas and experience" (IBO, 2013).

‍

Why the Metacognitive Layer Gets Skipped

Time pressure is the honest answer. Design projects take materials, room routines, group work and tool safety. Many Design teachers feel they barely finish the product builds before the project ends, so explicit reflection time can feel like a luxury.

There's a second reason, too: metacognition feels vague. Teachers know reflective practice matters, but "journal your thinking" often produces either fluff ("It was fun") or paralysis (learners staring at a blank page asking "What do you want me to say?"). Without structure, reflection becomes an assessment burden rather than a thinking accelerant.

The third reason is subtle: procedural checklists feel safer. A Design teacher can say "You will complete Phase 1 by Friday" and measure compliance. Metacognition is messier, you can't tick a box for "deep thinking." Assessing thinking requires reading between the lines and interpreting what learners have written, which feels riskier than assessing a finished product.

Yet the IB Design subject guide already asks for this kind of thinking. Criterion A requires learners to inquire into and analyse the problem, Criterion B asks them to develop ideas, Criterion C asks them to create the solution, and Criterion D asks them to evaluate. There is no Criterion E in MYP Design.

These criteria ask learners to use metacognition, even when they do not use that word. A learner may justify a design specification in Criterion B, adapt a making plan in Criterion C, or evaluate testing evidence in Criterion D. In each case, they show how they monitored and regulated their thinking. The scaffolds in this article are not extra tasks; they turn the four official criteria into clear classroom practice.

‍

The Four Phases, Mapped to Metacognitive Types

Metacognition comes in types. Flavell (1979) distinguished between knowledge of one's cognitive processes and the ability to monitor and regulate those processes. Schraw and Moshman (1995) expanded this into declarative knowledge (what to know), procedural knowledge (how to apply it), and conditional knowledge (when and why). In design thinking, von Thienen et al. (2023) add a useful distinction between product, process, people and place metacognition, which helps learners separate the solution from the strategy, the team and the context.

For the Design Cycle, we can map each phase to a type of metacognition learners should be practicing:

Phase 1: Inquiring and Analysing → Planning-type metacognition. Learners ask: What do I already know? What are assumptions, and what are real constraints? Where should I spend research time? This is metacognitive forethought, deciding how to think before action begins.

Phase 2: Developing Ideas → Monitoring-type metacognition. Learners ask: Is my design actually solving the brief, or have I drifted? Am I iterating in a useful way, or am I just making variations on one idea? This is metacognitive monitoring, catching yourself mid-action when you're veering off course.

Phase 3: Creating the Solution → Regulation-type metacognition. Learners decide: Where is it worth investing extra effort? Where should I accept "good enough"? When do I stop refining and proceed? This is metacognitive regulation,adjusting effort and strategy in real time.

Phase 4: Evaluating → Reflection-type metacognition. Learners ask: What worked and why? Would I make different choices next time? What did I learn about my own thinking? This is metacognitive reflection-on-action,consolidating learning after the work is done.

The table below maps these phases to the questions learners should ask, the scaffolds that make the thinking visible, and where evidence appears in the IB assessment criteria:

‍

‍

The power of this map is that it makes abstract metacognition concrete. You're not asking learners to "be reflective" (vague). You're asking specific questions at specific moments, and you're building scaffolds to capture the thinking.

‍

Phase 1: Inquiring and Analysing, Planning Your Thinking

The Inquiring and Analysing phase is where design thinking begins. It is also where design thinking often goes wrong. Learners may dive into research without a plan, which wastes time on irrelevant information. Or they may hold on to an early assumption they never question, then build a solution to a problem that doesn't actually exist.

Metacognitive forethought is the antidote. Zimmerman (1986) describes forethought as the stage where learners set goals, plan strategies, and activate relevant knowledge before acting. In design, this means asking: Before I research, what do I think I already know about this problem? What am I assuming? What's the real constraint versus a perceived constraint?

Consider a design challenge: "Create a storage solution for a busy secondary school kitchen." A learner without metacognitive forethought jumps straight to Pinterest, finds "cool storage ideas," and designs a vertical pegboard system. Eight weeks into the project, they discover the kitchen walls are made of tile that can't be drilled. They've wasted five weeks.

A learner who practises planning-type metacognition starts in a different way. She makes her thinking visible on a Knowledge Map:

What I know: Kitchens need organised storage. Secondary schools have high-traffic areas. Storage systems require mounting hardware.

What I think I know: School walls are standard plasterboard. Vertical storage is more efficient than horizontal storage. The budget is around £500.

What I need to find out: What materials are the walls made from (concrete, tile, plasterboard)? What's the actual budget? Who will use this system (learners, staff, or both)? What's currently failing in the kitchen storage?

This Knowledge Map is one page. It takes fifteen minutes. But it forces the learner to surface assumptions before they become costly mistakes. When she later discovers the walls are tile, she's already identified that as a variable to investigate. The iteration isn't starting over; it's adjusting a plan that was always flexible.

The classroom move is simple: Before research begins, ask learners to create a Knowledge Map,three columns, one page, handwritten or digital. As they research, they fill in the third column with actual answers, and they move items from "think I know" to "know" or "know is wrong." This artefact becomes evidence for Criterion A (Understanding the context), and it prevents derailed projects.

One classroom insight: if a learner's Knowledge Map is vague ("I need to find out about storage"), prompt them immediately: "What do you need to know about storage? Be specific." Specific forethought ("I need to know the wall material and load capacity") generates targeted research and faster progress.

‍

Phase 2: Developing Ideas and Monitoring

Design drift is real. Dorst (2015) calls problem-framing the most cognitively demanding part of design. In 2026, drift can also come from generative AI: a learner may ask a tool for three shoe designs and mistake fluent output for a tested response to the brief. Atchley et al. (2024) argue that AI use requires metacognitive control because learners must judge when they are offloading thinking, trusting misinformation, or losing sight of the goal.

The Developing Ideas phase is where monitoring-type metacognition catches drift. Instead of asking "How do I make my sketch better?", learners ask "Is my sketch solving the brief, or solving a different problem I prefer?"

A common example: A Year 4 learner is designing footwear for a hospital worker who's on their feet eight hours a day. The brief emphasises comfort and safety (non-slip, shock absorption). In week two, she sketches a shoe that looks fashionable with neon colour blocks. It's visually striking. She loves it. She iterates on this design for four more weeks, adding cushioning and gripping sole patterns. The final product looks great and functions reasonably.

But she's drifted. The brief never asked for fashion. She's solved "How do I design a shoe that looks cool?" instead of "How do I design a shoe that's comfortable and safe for someone on their feet eight hours a day?" The iteration was meaningful as form-refinement, but it wasn't meaningful as design-thinking refinement. She didn't learn to identify the real constraints; she learned to refine one idea.

Monitoring metacognition helps stop this pattern. After each iteration, or every two days of developing, learners pause. They then complete a Monitoring Prompt:

Right now, my design solves: [Restate the problem you're addressing in one sentence]

The strongest argument for this solution is: [Why does it actually solve the problem?]

The biggest challenge to this solution is: [What could go wrong? What constraint limits it?]

If I had one more iteration, I would: [What would you change and why?]

This four-part prompt forces learners to surface their assumptions about what problem they're solving. If their answer to "my design solves" doesn't match the actual brief, they notice the drift in real time. If they can't articulate why their solution works, they're not ready to iterate further.

The prompt also prevents perfection-chasing. When a learner writes "The biggest challenge is that the heel needs more cushioning," they're monitoring what matters for the brief, not what's easier to refine.

Schön (1983) calls this "reflection-in-action",thinking while doing, not after. That's what the Monitoring Prompt enables. You're not waiting until Evaluation phase to ask if the design makes sense. You're asking mid-project, when there's still time to change course.

A common design drift pattern is idea fixation: learners fall in love with their first sketch and refine it endlessly without testing whether it's actually the strongest solution. The table below captures the most frequent drift patterns and how metacognitive monitoring catches them:

‍

‍

The classroom rhythm is: sketch → test → Monitoring Prompt → iterate. Not sketch → iterate → sketch → iterate. The pause is small, five minutes, but it's metacognitively essential. Learners who monitor their problem-framing develop more flexible design thinking.

‍

Phase 3: Creating the Solution, Regulating Your Effort

Design projects often fail for a simple reason. The idea may be sound, but learners run out of time during the build or spend too long on features that do not matter most. Metacognitive regulation means choosing, on purpose, where to put effort. It helps prevent both problems.

In Phase 3, learners face constant micro-decisions: Which material is fastest to work with? Should I finish this feature or move to the next? Do I have time to sand down these rough edges, or should I declare it "done"?

Without regulation, learners either:

• Under-invest: Build quickly, produce a half-finished prototype that doesn't demonstrate the solution
• Over-invest: Spend all time perfecting details that don't affect the core solution, then rush the finishing

Metacognitive regulation is asking: For this decision, where is the opportunity cost highest? Where will extra effort yield the most learning or the most impact on the final product?

A learner building the hospital shoe (from Phase 2) faces this decision in week 6: "Should I hand-stitch the inner padding or use adhesive?" Stitching looks more finished but takes six hours. Adhesive takes one hour but might fail with heavy use. Without regulation, the learner either stitches obsessively (consuming time for other components) or defaults to adhesive without thinking through the trade-off.

To support regulation, she completes a Decision Register. This is a one-page log of major decisions:

‍

‍

This isn't busywork. It's a working document. When the learner reviews her register at the end, she can see where she invested wisely (the reinforcement stitching paid off; the hand carving ate time without much payoff). She learns what efficient design looks like. More importantly, she's conscious of her own trade-offs rather than defaulting to what feels right.

The Decision Register also provides evidence for Criterion C (Creating the solution). It shows how the learner planned the build, used resources, made technical decisions and adapted the solution when constraints changed. The register is proof of those judgements.

A classroom insight: during the Creating phase, do a mid-build Decision Register review (halfway through). Ask learners: "Looking at your register so far, are you investing time wisely? Is anything taking longer than it's worth?" This prevents late-stage regrets and teaches learners to adjust while there's still time.

‍

Phase 4: Evaluating, Reflecting on Design and Thinking

Most Design evaluations are product-focused. Learners submit work and answer: "Did it solve the brief? What were the strengths and weaknesses?" These are important questions, but they miss metacognitive depth.

Schön (1983) distinguishes between reflection-in-action (thinking while doing, which the Monitoring Prompt captures) and reflection-on-action (thinking after doing, which evaluation enables). Reflection-on-action helps learners secure what they have learned and see how to use it elsewhere. This only happens when they are asked to think about their own thinking, not just the product.

Hattie (2009) placed feedback among the more influential contributors to achievement, and Hattie and Timperley (2007) show that feedback improves learning when learners understand the gap between where they are and where they need to go. Self-evaluation that includes metacognitive reflection deepens that gap-awareness. Instead of "My design worked" (vague), a learner might write "I initially thought the heel padding should be thick, but testing showed that thick padding caused the foot to slip. Thinner padding with a textured surface worked better. Next time, I'll test assumptions about materials earlier, before committing to a design."

That's metacognitive reflection: noticing not just that something failed, but why you thought it would work and what changed your mind. That insight transfers to the next project.

The classroom move is a Reflective Evaluation,not a grade, but a learning conversation. Instead of marking a design 7/10, you ask three questions:

1. The most important thing I learned about design was: [What insight did you gain about how design works?]
2. The most important thing I learned about my own thinking was: [What did you discover about how you think?]
3. Next time I design something, I will: [What metacognitive habit will you carry forward?]

Notice: questions 1 and 3 are about design; question 2 is explicitly metacognitive. This gives permission for learners to name metacognitive growth ("I learned that I get attached to my first ideas without testing them" or "I realised I often assume constraints that don't exist until I ask about them").

A real example from a Year 4 learner designing storage for a kitchen:

1. "The most important thing I learned about design was that storage isn't just about space, it's about workflow. I didn't realise that until I watched the kitchen staff use my prototype. I'd made vertical cubbies, but staff kept putting items horizontally because it was faster."

2. "The most important thing I learned about my own thinking was that I solve for what I see (space efficiency) instead of what I observe (how people actually use the space). Next time I need to spend more time watching before I design."

3. "Next time I design something, I will do a 'workflow observation' first, spend at least one full day watching how people use the space before I sketch any ideas."

That's powerful metacognitive reflection. The learner has identified a thinking pattern (designing for aesthetics before function) and articulated a concrete habit to change it. That learning transfers. When she designs her next project, she'll be primed to observe before sketching.

A note on timing: evaluation works best immediately after project completion, while the project is still vivid. Do not wait three weeks to evaluate. Frame it as a conversation, not an assessment. You can say: "Look at what you have made. What surprised you about the design process? What did you discover about how you think?"

‍

Integrating Metacognition Without Adding Workload

The most common objection is: "My Year 5 learners already feel overloaded. If I add reflection scaffolds, they'll drown." Use it as a starting point for professional discussion: identify the learner's current need, record evidence from more than one lesson, and agree the next classroom adjustment with the SENCO or family.

The answer is that metacognitive scaffolds replace generic journaling, not add to it. Most Design teachers ask learners to maintain a design journal throughout the project. These journals often become either dutiful transcripts of what happened ("Monday: completed research. Tuesday: sketched ideas") or vague navel-gazing ("Design is hard"). The Knowledge Map, Monitoring Prompt, Decision Register, and Reflective Evaluation are more structured alternatives. Each is one page or less. Each fits directly into the project timeline.

Here's the payoff: these four scaffolds work together. They provide evidence for all five IB Design criteria without adding to assessment labour:

• Knowledge Map = evidence for Criterion A (Understanding)
• Monitoring Prompt = evidence for Criterion C (Developing Ideas and iteration)
• Decision Register = evidence for Criterion D (Making and Modifying Design)
• Reflective Evaluation = evidence for Criterion E (Evaluation and transfer)
• All four = evidence for Criterion B (Inquiring and Developing, which runs across all phases)

In other words, you're not adding paperwork. You're substituting structured, metacognitive paperwork for unstructured journaling. The total time learners spend on reflective writing stays the same or decreases, but the quality of thinking, and the evidence you have for grading, improves dramatically.

Another integration point: Assessment doesn't get harder. You read metacognition within the existing criteria. You are not adding new criteria. When a Monitoring Prompt shows meaningful development of ideas, it supports Criterion B. When a Decision Register shows planned making, resource choices and adaptation, it supports Criterion C. When a Reflective Evaluation uses testing evidence to judge success, it supports Criterion D. The criteria have not changed; the thinking is just easier to see.

One more integration idea: the scaffolds scale for different year groups. Year 3 learners need more detailed Knowledge Map templates and simpler Monitoring Prompts. Year 5 learners can sketch their own Knowledge Map and write more sophisticated Monitoring reflections. The framework stays the same; the complexity adapts.

‍

‍

Thinking About Thinking to Action infographic for teachers" loading="lazy">

‍

‍

‍

A Complete Worked Example: Designing a Low-Tech Water Filter

Year 4, ages 14-15. One twelve-week project. Brief: "Design a low-cost water filtration system using locally available materials. The system must filter water from an untreated source (river, borehole, or rainwater collection) in a rural school setting where power and maintenance are limited."

‍

Inquiring and Analysing (Weeks 1-2)

Learner starts with a Knowledge Map:

What I know: Water filtration uses sand, gravel, and activated charcoal. Boiling kills bacteria. Dirty water has visible particles and germs.

What I think I know: Sand alone can filter most contaminants. You need large amounts of water for testing. The school where this will be used is in Kenya.

What I need to find out: What contaminants are in the specific water source (bacteria, parasites, chemicals)? What's the cost limit per litre? How much water needs filtering daily? What materials are actually available locally? How often will the filter need replacing? What will learners and staff be willing to maintain?

The learner researches for two weeks. She interviews the school coordinator via email, discovers the water source is a borehole with visible sediment and occasional chemical smell. Budget: £50 for materials. Daily water use: 200 litres. Maintenance: whatever is simplest. She revises her Knowledge Map:

Now I know: The filter must handle sediment and odour (likely chemical or organic). Activated charcoal is expensive and hard to source; coconut husk charcoal exists locally. Sand is abundant. Gravel is available. Testing will require a water testing kit or basic microbiology (colour, smell, clarity).

New knowledge gaps: How many layers does the filter need? What's the optimal flow rate? How do I test whether it's working?

‍

Developing Ideas (Weeks 3-5)

The learner sketches three different filter designs:

• Design A: Layered sand, gravel, and coconut charcoal in a drum with a tap
• Design B: A gravity-fed system with multiple chambers
• Design C: A solar disinfection approach (bottles in sunlight) combined with basic filtration

She tests each design with small prototypes using water mixed with soil and food colouring. After two iterations, she selects Design A (simplest, lowest cost, easiest to maintain).

After week 4 of development, she completes a Monitoring Prompt:

Right now, my design solves: How to remove visible sediment and make water clearer. It uses materials available in rural Kenya. It does not need ongoing supplies or power.

The strongest argument for this solution is: It uses materials that are easy to find locally (sand, gravel, coconut husk). It needs no electricity. Learners and staff can maintain it by replacing the top layer of sand every two months.

The biggest challenge to this solution is: I'm not certain it removes chemical odour completely, and I can't test for harmful bacteria with the resources I have.

If I had one more iteration, I would: Source actual water from the borehole and test my prototype against it. Also, I'd design a clear chamber so the school can see how much sediment collects, so they know when to replace the sand.

This Monitoring Prompt shows that she's solving the right problem: sediment and clarity. It also shows that she understands a real limit: bacterial testing. She has identified a valuable feature, visibility, and is monitoring her own design thinking. She is not drifting, so she moves forward with confidence.

‍

Creating the Solution (Weeks 6-10)

Learner sources a 60-litre plastic drum, buys sand and gravel, dries coconut husk over two weeks, and builds the prototype. She installs a tap at the bottom and tests flow rate.

During week 7, she creates a Decision Register:

‍

‍

By week 9, the prototype is complete and functioning. Water runs through it. She tests it with water from a nearby ditch (proxy for the borehole water). The filtered water is noticeably clearer. The smell is improved but not gone.

‍

Evaluating (Week 11-12)

She completes the final Reflective Evaluation:

1. The most important thing I learned about design was: Constraints are useful because they force a design to fit its context. At first, I thought "no power, no budget, no lab equipment" were only problems. They made me choose a simple, maintainable filter instead of a complex system the school would abandon after a month.

If I designed for a school with electricity and a larger budget, I would make different choices. In this setting, the constraints improved the design because they kept my attention on maintenance, cost and local materials.

2. The most important thing I learned about my own thinking was: I assumed chemical pollution needed a chemical solution. But the biggest problem was sediment, not chemicals. I spent the first week researching complex carbon filtration, when basic sand layering would solve 80% of the problem. I learned that I need to test my assumptions (Is it really a chemical problem?) before diving into solutions. Most of my assumptions are wrong.

3. Next time I design something, I will: Start by listing my assumptions and then explicitly test them against reality. I'll also watch the people who will actually use my design for at least a day before I finalise the idea. That taught me more than any research.

That learner has grown metacognitively. She has spotted a thinking pattern (assuming complexity when simplicity works), recognised her bias (testing assumptions), and named a clear habit (observe the user first). That learning transfers. She is not just a better filter designer; she is becoming a more reflective designer.

‍

Five Classroom Moves That Make Metacognition Stick

Metacognitive teaching is a skill. Learners don't automatically reflect deeply. Here are concrete moves that make thinking visible and internalised. Use this as a starting point for professional discussion. Identify the learner's current need and record evidence from several lessons. Then agree on the next classroom adjustment with the SENCO or family.

1. Model your own metacognition aloud. Before learners complete a Monitoring Prompt, run a short teacher think-aloud on a design problem you are solving. Kavousi et al. (2020) found that stronger designers use planning, monitoring and control while developing ideas, so make those moves audible: "I assumed pairs would work best, but the prototype talk is stronger in threes. I am changing the grouping because the task needs more challenge." This shows learners what monitoring sounds like before they try it alone.

2. Timing matters more than length. A two-minute Monitoring Prompt completed immediately after testing is more powerful than a ten-minute reflection one week later. Learners' thinking is vivid and specific when they've just struggled. Wait too long and the details fade. Integrate metacognitive prompts into the project rhythm, not as add-ons at the end.

3. Pair scaffolds with peer feedback. Treat monitoring as social metacognition, not private diary work. After a learner completes a Monitoring Prompt, they read it to a peer, who asks: "Is that solving the brief, or are you drifting?" The learner must repeat the feedback, accept or challenge it with evidence, and revise the prompt. That sequence makes peer challenge part of design reasoning rather than a comment at the end.

4. Use "yet" language. When a learner says "I can't test for bacteria in the water," avoid fixing the problem. Say instead: "You can't test for bacteria yet. What would it take to test for bacteria? What's the next step?" This frames constraints as solvable puzzles, not dead ends. Learners then begin asking metacognitive questions: "What resources would I need? Who could help me?"

5. Share metacognitive struggles, not just successes. Design failure creates frustration, and that emotion can block strategy change. Share examples where you or previous learners got stuck mid-project and regrouped: "In week 5, I realised my design would not work. I was frustrated, so I went back to my Monitoring Prompt, reread the brief, and chose one change rather than starting everything again." Name the emotion, then name the next thinking move. This helps learners treat frustration as information, not as proof that the project has failed.

‍

Extending Metacognitive Design Thinking Across the MYP

The Framework transfers beyond Design projects. The IB Approaches to Teaching and Learning (ATL) cluster on Reflection is embedded across all subjects. Many MYP teachers are asking: "How do I make metacognition visible in science, geography, history?"

The Design Cycle framework gives you a language. Any iterative problem-solving process can be wrapped in these four metacognitive types:

In Science practicals: Inquiring means planning the experiment (What are your variables? What's your hypothesis?). Developing means testing (Are your results matching your hypothesis? Should you adjust your method?). Creating means running the final experiment. Evaluating means interpreting results and thinking about limitations.

In Geography fieldwork: Inquiring means deciding where to collect data (What location will give you the most representative sample?). Developing means testing different data-collection spots. Creating means conducting the full survey. Evaluating means judging whether your method captured what you intended.

In History essays: Inquiring means framing the historical question (What evidence is relevant?). Developing means drafting arguments. Creating means writing the full essay. Evaluating means reflecting on your argument's strength.

In Interdisciplinary Units, when a team of teachers collaborates on a unit spanning Design, Science, and Geography, you can explicitly teach the Design Cycle as the thinking framework. Learners complete Knowledge Maps at the start of any unit (not just Design projects). They monitor their understanding mid-unit. They regulate their effort. They reflect on learning.

This consistency matters beyond the Design department. For headteachers and curriculum leaders, shared metacognitive checkpoints can reduce repeated hand-holding because learners meet the same planning, monitoring and evaluation language in Design, science practicals and geography fieldwork. Do not assume transfer will happen by itself. Make the bridge explicit: "The monitoring prompt you used for the prototype is the same check you use before changing a science method."

‍

Assessing Metacognition Without Adding Criteria

The IB Design subject guide has four criteria. You're not adding a fifth. You're reading metacognition within the existing four. Use it as a starting point for professional discussion: identify the learner's current need, record evidence from more than one lesson, and agree the next classroom adjustment with the SENCO or family.

Criterion A (Inquiring and Analysing) explicitly asks: "The learner understands the problem to be solved." A learner with a detailed, specific Knowledge Map that surfaces real constraints demonstrates this understanding more clearly than one without. You're not adding a rubric; you're seeing evidence of understanding more vividly.

Criterion B (Developing Ideas) requires learners to develop design specifications, present feasible ideas and explain choices. A Monitoring Prompt can show why a learner moved from one idea to another. This gives stronger evidence than a sketchbook full of surface variations.

Criterion C (Creating the Solution) asks learners to plan and create the chosen solution, then adapt it when the making process reveals constraints. The Decision Register is explicit evidence of those judgements. Instead of inferring from a finished product whether a learner made deliberate choices or defaulted to the easiest path, you can read the register and see their reasoning.

Criterion D (Evaluating) asks learners to design tests, judge success against the specification, and explain how the solution could improve. A Reflective Evaluation should cover both product evidence and personal learning. This shows understanding more clearly than a brief product review.

In other words, you're not inventing new assessments. You're making the thinking visible so that you can assess it against existing criteria. The grade doesn't change; the evidence becomes clearer, and your assessment becomes fairer.

One practical note: during the project, treat these scaffolds as formative feedback tools. A learner's Monitoring Prompt in week 5 can reveal drift while there is still time to change the design. Schön (1983) matters here: the strongest evidence is reflection-in-action, not a neat reflection written after the deadline. Keep one mid-project checkpoint in the assessed evidence so learners cannot simply invent a rationale after the product is finished.

‍

Common Pitfalls and How to Avoid Them

Metacognitive teaching can fail in specific ways. Here's how to avoid the most common traps: Use it as a starting point for professional discussion: identify the learner's current need, record evidence from more than one lesson, and agree the next classroom adjustment with the SENCO or family.

Pitfall 1: Generic reflection. You ask "How did the project go?" and learners write "It was good. I learned a lot." This teaches nothing. The problem is open-endedness. Solution: use specific prompts with clear structure. "My design solves [X]. The strongest argument is [Y]. The biggest challenge is [Z]." Specificity forces specificity.

Pitfall 2: Over-scaffolding Year 5 learners and overloading novices. Scaffolds should match expertise. Sweller (1988) warned that working memory is limited, so novice learners and learners with SEND may need fewer prompts, icons, oral rehearsal, visual examples and extra processing time. More experienced Year 5 learners usually need lighter prompts, such as "My design solves..." or "If I redesigned, I would..." The aim is to reduce unnecessary load while keeping the monitoring move visible.

Pitfall 3: Reflection timing. Learners often feel like they're being asked to reflect when they're tired or disengaged (end of a long build week, or weeks after a project ends). Reflection in that state produces vague, surface-level writing. Solution: build reflection into natural project pauses. After a prototype test (even a small one), pause for five minutes of Monitoring Prompt. After half the build time, review the Decision Register. These moments of reflection are when thinking is sharpest.

Pitfall 4: Treating reflection as confession. Some learners become anxious that metacognitive reflection is a way to confess mistakes and get lower grades. "If I write that I made a bad choice, will I get marked down?" Reframe explicitly: "This reflection shows me how you think. The more honest you are about what you learned and what you'd change, the better I understand your learning. Your grade is about the design and your final reflection, not about whether you made perfect decisions."

Pitfall 5: Losing the design in the metacognition. You can over-emphasise the thinking and under-emphasise the product. The Design Cycle is still a design subject. The product matters. The scaffolds are meant to deepen design thinking, not replace design standards. Keep the balance: learners should still produce beautiful, functional designs. The metacognitive scaffolds just help them think more clearly while making those designs.

‍

Metacognitive Design Thinking as CPD Leadership

If you're a Design teacher or Design leader, you now have a framework to lead your department. That's the ultimate metacognitive growth: from teaching individual learners to reflect to teaching teachers to see metacognition in their practice.

Here's what a CPD session might look like: present the phase-to-metacognitive-type map. Show the four scaffolds. Then do this: have teachers complete a Knowledge Map for a design problem they're currently solving in their own practice (curriculum planning, lesson design, resource sourcing, anything). After they've mapped their thinking, ask them: "What did you notice? Did mapping your thinking change anything?"

This is powerful because most teachers have never externalised their thinking in a structured way. They notice assumptions they were carrying invisibly. They see gaps in their knowledge. They realise where they need help. That experience, felt in their own practice, makes them believe in metacognition for learners.

From there, you can shift to the Design subject. "Now imagine your Year 4s feel this clarity during a project. Imagine they surface their assumptions before derailing the design. Imagine they catch problem-drift mid-project." Teachers who've experienced the power of metacognition in their own thinking become evangelists for teaching it to learners.

The research backing is useful, but it does not work by itself. Flavell (1979) showed that metacognitive awareness can be learned, and the EEF (2018) found that clear metacognitive teaching with structured scaffolds can support learning. Yu et al. (2024) report positive but moderated effects for design thinking, so term-length projects with small teams make more sense than one-off reflection sheets. Transfer across subjects needs deliberate bridging: Perkins and Salomon (1992) argue that far transfer depends on teachers helping learners compare contexts and abstract the shared strategy.

‍

‍

‍

‍

‍

‍

‍

‍

‍

‍

Limitations and Critiques

Metacognition in the MYP Design Cycle has strong classroom value, but it should not be treated as a guaranteed route to better design work. A first limitation is measurement. Hattie (2009) brought wide attention to visible learning, yet critics argue that large meta-analytic summaries can hide differences in study quality, context, and outcome measures. Snook et al. (2009), Terhart (2011), and Simpson (2017) warn against reading broad effect sizes as simple instructions for every classroom.

A second limitation is assessment backwash. Schön (1983) distinguished reflection-in-action from reflection-on-action. MYP Design can ask for rich reflection, but Criterion D may also reward polished post-hoc explanation. As a result, learners may justify decisions after the product is finished instead of monitoring decisions while they make it.

A third issue is transfer. Perkins and Salomon (1992) argued that far transfer is difficult unless teachers make the bridge explicit. For example, a learner may regulate effort in a water-filter project. They will not automatically use the same strategy in algebra or English unless teachers support direct comparison and rehearsal.

There are also cultural and access concerns. IB research more widely has warned that access and language demands are not neutral (Maire & Windle, 2021). Highly verbal reflection can favour confident writers, fluent English speakers, and learners already familiar with IB discourse. Learners with SEND may need oral rehearsal, visuals, worked examples and shorter prompts. The theory remains useful because it gives teachers a language for planning, monitoring and evaluating thinking, but it works best when treated as scaffolded practice rather than as a universal fix.

‍

References

Hattie, J. (2009). Visible learning.

‍

‍

Further Reading: Research and IBO Sources

Flavell, J. H. (1979). Metacognition and cognitive monitoring: A new area of cognitive-developmental inquiry. American Psychologist, 34(10), 906-911. Use it as a starting point for professional discussion: identify the learner's current need, record evidence from more than one lesson, and agree the next classroom adjustment with the SENCO or family.

Brown, A. L. (1987). Metacognition, executive control, self-regulation, and other mysterious mechanisms. In F. E. Weinert & R. H. Kluwe (Eds.), Metacognition, motivation, and understanding (pp. 65-116). Lawrence Erlbaum Associates.

Schön, D. A. (1983). The Reflective Practitioner: How Professionals Think in Action. Basic Books.

Hattie, J., & Timperley, H. (2007). The power of feedback. Review of Educational Research, 77(1), 81-112.

Education Endowment Foundation. (2018). Metacognition and Self-Regulated Learning: Guidance Report. EEF.

IBO (2014). MYP: From Principles Into Practice. International Baccalaureate Organization.

Erickson, H. L., Lanning, L. A., & French, R. (2017). Concept-Based Curriculum and Instruction for the Thinking Classroom (3rd ed.). Corwin.

‍

‍

FAQ

Free Resource Pack

Metacognition in MYP Design

4 evidence-informed resources to empower students' reflection and teachers' facilitation of metacognitive skills in the MYP Design Cycle.

MetacognitionMYP Design CycleStudent ReflectionTeacher CPDLesson PlanningClassroom Wall DisplayDesk CardCritical ThinkingATL Skills

Download Now ▼

Download your free bundle

Fill in your details below and we'll send the resource pack straight to your inbox.

First name

Last name

School email

School name

Your roleSelect your roleClass TeacherSENCoSubject LeadPhase LeadDeputy HeadHeadteacherTeaching AssistantOther

Current school focusSelect focus areaMetacognition and self-regulationLiteracy and readingNumeracy and mathsBehaviour and wellbeingSEND and inclusionAssessment and feedbackCurriculum developmentStaff CPD and trainingOther / not applicable

Quick survey (helps us create better resources)

How confident are you in explicitly teaching and fostering metacognitive skills within the MYP Design Cycle?

Not at all confident

Slightly confident

Moderately confident

Very confident

Extremely confident

To what extent do you feel supported by your school and colleagues in integrating metacognition into MYP Design projects?

Not supported

Slightly supported

Moderately supported

Well supported

Strongly supported

How consistently do you currently integrate metacognitive prompts and reflection opportunities into your MYP Design lessons?

Never

Rarely

Sometimes

Often

Always

Download Free Resource Pack

✅

Your resource pack is ready

We've also sent a copy to your email. Check your inbox.

Download Resources

Free resource from structural-learning.com · Evidence-based teaching tools