MYP Personal Project Guide: Criteria & Examples

The MYP Personal Project is one of the most independent pieces of work you complete in the Middle Years Programme. Instead of receiving a tightly defined assignment, you choose something you genuinely want to learn, decide what you will create or achieve, plan the work, apply your Approaches to Learning skills, and reflect on what the experience taught you.

That freedom is also why the project can feel confusing. Students often focus so heavily on making an impressive final product that they forget what the Personal Project actually assesses: the quality of the learning process and the evidence used to explain it.

This MYP personal project guide takes you from the first idea to the final report, with practical examples, supervisor insights and a realistic timeline.

What Is the MYP Personal Project?

The Personal Project is completed in the final year of the MYP. The IB describes it as an independent learning experience of approximately 25 hours that allows students to explore a personal interest while strengthening the skills developed across the programme.

The International Baccalaureate Personal Project page summarizes the structure clearly:

The project is made up of a process, a product and a reflective report.

In practice, you need to think about the process you follow, the product or outcome you create, the learning you can evidence and the report that explains what happened.

A product can be tangible, such as a cookbook, prototype, artwork or website. It can also be an outcome, such as organizing an event, completing an investigation or developing a new skill.

Important Update: The Current Personal Project Uses Three Criteria

Many online guides still describe four Personal Project criteria: Criterion A Investigating, Criterion B Planning, Criterion C Taking Action and Criterion D Reflecting. That is an older assessment model.

The current IB subject brief uses three equally weighted criteria, each with achievement levels from 1 to 8.

Criterion A: Planning

You state your learning goal and explain the personal interest behind it. You define the intended product or outcome, create appropriate success criteria and present a clear plan for achieving them.

A strong Criterion A section therefore connects three things clearly: what you want to learn, what you want to create and how you will know whether the product succeeds.

Criterion B: Applying Skills

You explain how specific ATL skills helped you achieve your learning goal and your product or outcome.

Simply naming an ATL skill is not enough. Saying that you used research skills or self management skills tells the assessor very little.

You need to explain where you used the skill, what you actually did and how that action helped the project progress.

Criterion C: Reflecting

You explain the impact of the project on you or your learning, then evaluate the finished product against the success criteria you created earlier.

This is why good success criteria matter so much. If your criteria are vague at the beginning, your final evaluation will also be vague.

This distinction matters because regular MYP subjects commonly use four criteria labelled A to D, while the current Personal Project assessment uses three. If a guide tells you to write a current Criterion D section, check the date and compare it with your school's latest instructions.

What About the 1,500 to 3,500 Word Report?

The familiar 1,500 to 3,500 word range appears in older IB and school materials, including earlier Personal Project handbooks. Newer implementations often use page based submission limits instead.

The safest approach is to follow your school's current Personal Project handbook and template rather than assuming an older word count still applies.

The purpose of the report has remained consistent. It needs to explain the process concisely, use evidence from your work, include a bibliography and meet academic integrity requirements.

A useful structure is to organize the main body around Criterion A, Criterion B and Criterion C. This makes it much easier to check whether every assessment requirement has actually been addressed.

Seven Steps to Complete the MYP Personal Project

The IB publishes a seven step Personal Project infographic, but it is mainly written for schools, supervisors and coordinators. For students, the journey is easier to understand as these seven practical actions.

Step 1: Choose a Learning Goal, Not Just a Topic

"Photography" is a topic.

"Learn how shutter speed, aperture and composition affect sports photography so I can produce a curated photo series" is a learning goal.

A strong goal is personal, focused and realistic within roughly 25 hours.

Ask yourself what you genuinely want to understand or become better at by the end of the project.

Step 2: Define the Product and Success Criteria

Decide what will prove that your learning became action.

If you want to learn beginner web development, your product might be an educational website. Success criteria could cover usability, accuracy, accessibility, visual consistency and feedback from test users.

Make the criteria measurable enough to evaluate later.

"Make the website look professional" is difficult to assess.

"Use a consistent visual system across every page and achieve positive usability feedback from at least five test users" gives you something concrete to evaluate.

Step 3: Research Before You Build

Research should influence decisions, not simply fill pages.

Record useful sources, evaluate them and note what changed because of what you learned.

Suppose research shows that your original app interface would be difficult for younger users to navigate. If you simplify the interface because of that evidence, the research has directly shaped your product.

That is much stronger than simply listing information you found online.

Step 4: Build a Realistic Action Plan

Break the project into milestones for research, product development, testing, revision and report writing. Add supervisor meetings and school deadlines.

A strong plan does not need to remain unchanged.

Real projects change. Materials become unavailable. Research reveals a better approach. Testing exposes problems. Schoolwork becomes busy.

If your plan changes, record what changed and why.

Step 5: Create and Document at the Same Time

Do not separate "doing the project" from "documenting the project."

Save photographs, screenshots, prototypes, source evaluations, feedback, rejected ideas, test results and notes from important decisions while they happen.

A rough first prototype followed by two improved versions can provide more useful evidence than one perfect final photograph.

Do not try to reconstruct months of thinking just before submission.

Step 6: Use Supervisor Meetings Properly

Your supervisor provides guidance and formative feedback. They are not there to choose the project or make the important decisions for you.

Arrive at meetings with evidence and questions.

Instead of saying, "Is my project good?", ask something more useful such as, "My testing suggests two of my success criteria are unrealistic. Should I revise the criteria or change the product?"

Record what you discussed and what you decided to do next.

From a supervisor's perspective, regular evidence of thinking is often much more reassuring than seeing a beautiful product suddenly appear near the deadline.

Step 7: Write the Report from Evidence

Organize the report around the current criteria. Every important claim should be supported by something specific.

Instead of writing:

"I improved my research skills."

Explain which research skill you used, where you used it, what problem it helped solve and what evidence demonstrates the improvement.

Your report should explain the learning behind the project rather than simply retelling everything that happened.

The Process Journal Is an Evidence Bank

A process journal should not become a diary of everything you did.

"Today I worked on my website for two hours" says very little about your learning.

A stronger entry identifies a problem, the information or feedback you considered, what you changed and why.

A useful process journal can contain:

• Early brainstorms and rejected ideas
• Research notes and source evaluations
• Draft success criteria
• Action plan changes
• Product screenshots or photographs
• Testing and audience feedback
• Supervisor meeting notes
• Reflections on ATL skills
• Evidence of setbacks and responses

The South Lakes High School Personal Project guide similarly treats the process journal as a place for ideas, planning, discussions, photographs, meetings and outcomes.

The goal is not to create the longest journal. It is to create enough authentic evidence that your report can prove how you worked and learned.

A Realistic Timeline with Supervisor Meetings

Your school's calendar comes first, but this structure can help you distribute the work instead of rushing everything near submission.

Weeks 1 and 2: Explore and Narrow

Choose your area of interest, draft the learning goal and define a possible product.

Check whether the idea is achievable with the time, resources, skills and access you actually have.

Weeks 3 and 4: Research and First Supervisor Meeting

Research the topic, test feasibility with your supervisor, refine the learning goal and begin creating success criteria.

Bring your early research and possible criteria to the meeting rather than arriving with only an idea.

Weeks 5 and 6: Finalize the Plan

Complete the success criteria and action plan. Identify the ATL skills you expect to use and the evidence you need to collect.

This is also the point to identify risks. If your project depends on interviews, specialist equipment or outside participants, make sure access is realistic.

Weeks 7 to 12: Create, Test and Record

Develop the product in stages.

Keep evidence as you work and test important parts before the product feels finished.

A website can be tested before every page is complete. A recipe can be tested before the cookbook is designed. A prototype can be shown to users before its appearance is polished.

Midpoint Supervisor Meeting

Bring your current product, journal evidence and action plan.

Compare progress with the success criteria.

Ask three questions:

1. What is working?
2. What is not working?
3. What needs to change before the next milestone?

Record the answers.

Weeks 13 to 16: Complete and Evaluate

Finish the product, gather final feedback and evaluate each success criterion using evidence.

Avoid deciding that everything was successful simply because the product was completed.

A thoughtful evaluation can acknowledge that some criteria were fully achieved while others were only partly achieved.

Final Supervisor Meeting and Report Stage

Plan the report around Criteria A, B and C.

Select only the strongest journal evidence. Use any formative feedback your school permits, then check citations, bibliography and academic integrity requirements.

MYP Personal Project Examples and Ideas

Strong personal project ideas for MYP are not necessarily complicated. They create a clear connection between learning, action and evidence.

Real Personal Project exemplar collections include projects involving guidebooks, animation, children's literature, cooking, entrepreneurship, jewellery making, web development, photography, art and sustainable food.

That variety tells you something important: there is no single type of product that automatically earns a strong result.

Beginner Sports Website

Learning goal: develop HTML, CSS and basic user experience design skills.

Product: a website teaching beginners the rules and techniques of a chosen sport.

Useful evidence could include code drafts, interface sketches, usability testing and changes made after user feedback.

Cultural Cookbook

Learning goal: understand how food connects to family or regional history.

Product: a tested cookbook combining recipes with cultural explanations.

Evidence could include family interviews, historical research, recipe trials, photography decisions and reader feedback.

Children's Storybook

Learning goal: understand how storytelling can communicate a social or ethical idea to younger readers.

Product: an illustrated children's book.

Keep audience research, story drafts, illustration development and readability feedback.

Small App Prototype

Learning goal: learn basic interface design and digital prototyping.

Product: a focused tool such as a habit tracker or study planner.

Save wireframes, user feedback, testing results and explanations of design changes.

Local History Photo Project

Learning goal: develop documentary photography and historical research skills.

Product: a curated photo collection connecting present day locations with their history.

Useful evidence could include archive research, location planning, photography experiments and decisions about how photographs were selected.

What Strong Projects Show from a Supervisor's Perspective

A polished product helps, but supervisors need evidence of learning.

Strong projects usually show that the student can narrow an idea, make decisions independently, respond to feedback, apply ATL skills in specific situations, revise a plan when necessary and reflect without pretending everything went perfectly.

Iteration is especially valuable.

A failed prototype, weak first interview or unrealistic timeline does not automatically damage the project.

If you explain what happened, what you learned and how that learning changed your next decision, the problem becomes evidence of growth.

Supervisors can also tell when reflection has been written at the end without supporting process evidence. Consistent records make your report more credible and much easier to write.

The most impressive project is therefore not always the strongest Personal Project.

A student who makes a relatively simple product but can clearly demonstrate planning, skill application, adaptation and reflection can provide much stronger assessment evidence than a student who creates something ambitious but cannot explain how they got there.

Common Mistakes to Avoid

1. Choosing a topic that is too broad for the available time.
2. Making success criteria so vague that they cannot be evaluated.
3. Spending nearly all your effort on the product and very little on evidence.
4. Naming ATL skills without showing how they were actually applied.
5. Treating the process journal as an activity log.
6. Hiding mistakes instead of explaining how you responded to them.
7. Following an old Criteria A to D guide without checking current requirements.
8. Using AI to produce reflection you cannot personally explain or defend.

Your Personal Project should still sound like you because the learning is yours.

Final Advice

The MYP Personal Project becomes much more manageable when you stop treating it as one huge assignment.

Choose a meaningful learning goal, define what success looks like, research intelligently, plan realistically, document important decisions, use your supervisor well and reflect with evidence.

The final product matters, but it is not the whole project. What you can explain about your learning journey is just as important.

Plan milestones, reflection prompts and project evidence with Koncepts.