The most common MYP Personal Project mistakes are rarely caused by weak ideas. Marks are more often limited by an unclear learning goal, untestable success criteria, incomplete evidence, superficial ATL explanations, or reflection that describes events without analyzing learning.
The current public IB framework assesses the Personal Project through three equally weighted criteria: Criterion A: Planning, Criterion B: Applying skills, and Criterion C: Reflecting. Each criterion has a maximum of 8, producing a total of 24. Avoiding the following mistakes will help you make your process, decisions, and learning visible.
Understand the current Personal Project criteria
According to the IB Personal Project overview, the project includes a process, a product or outcome, and a reflective report. It assesses how students apply approaches to learning, or ATL skills, during an extended independent project.
| Criterion | What the report must communicate | Maximum |
|---|---|---|
| A: Planning | The learning goal, personal-interest connection, intended product, success criteria, and detailed plan | 8 |
| B: Applying skills | How particular ATL skills supported the learning goal and product | 8 |
| C: Reflecting | The project's impact on the student or learning, plus an evidence-based product evaluation | 8 |
The official IB Personal Project brief summarizes these criteria. Some older resources instead present four criteria called Investigating, Planning, Taking action, and Reflecting. Always use the rubric and submission instructions supplied by your school, since your coordinator confirms the requirements applying to your cohort.
Mistake 1: Confusing the topic, learning goal, and product
A topic identifies an area of interest. A learning goal states what you intend to understand or learn to do, while the product is what you will create to support and demonstrate that learning.
For example:
- Topic: Nutrition for teenage athletes
- Learning goal: Learn how nutritional needs change before, during, and after endurance exercise
- Product: A tested digital meal-planning guide for teenage distance runners
“Sustainable fashion” is only a topic. “Learn how fabric selection, garment construction, and repair techniques can extend clothing's usable life” is a learning goal. This distinction matters because Criterion A requires both a learning goal and an intended product; an attractive product cannot compensate for learning that was never clearly defined.
Mistake 2: Choosing an unrealistic project
Strong MYP Personal Project topics provide genuine challenge while remaining achievable within the school's timeline. Projects become unmanageable when students target an enormous audience, attempt several advanced skills simultaneously, or depend on equipment and expertise they cannot access.
“Create an app that solves teenage anxiety” is too broad and makes an unrealistic causal claim. “Learn basic user-interface design and create a non-clinical breathing-exercise prototype tested for usability by ten students” has a clearer learning area, audience, product, and testing method.
Before committing, ask whether you can complete the product with your available time and resources, collect evidence of development, and evaluate the result through more than personal opinion. A focused project usually produces deeper learning than an ambitious project that cannot be tested or completed.
Mistake 3: Writing vague success criteria
Weak criteria use words such as “good,” “professional,” or “effective” without defining them. Strong success criteria identify observable product features and the evidence that will be used to test them.
| Weak criterion | Improved criterion | Evidence |
|---|---|---|
| The guide will look professional | Every page will use two readable fonts and a consistent heading hierarchy | Design audit and screenshots |
| The app will be easy to use | At least 8 of 10 users will complete the main task without verbal help | Usability results |
| The podcast will be informative | Each episode will explain three verified concepts and identify its sources | Content checklist and bibliography |
Criteria may address content, function, audience, dimensions, accessibility, durability, accuracy, or user response. Establish them before finishing the product so that they guide development rather than being rewritten to match whatever you eventually create.
Mistake 4: Producing a schedule instead of a plan
“Research, create product, write report” is a schedule, not a detailed plan. A useful plan connects each task, deadline, relevant success criterion, and item of evidence.
For example, write: “By 14 October, test the prototype with five intended users, record completion rates and comments, and revise the navigation.” This is more useful than “Test app in October” because it defines the action, evidence, and intended response.
Include checkpoints and contingency time for technical problems, unavailable materials, or delayed feedback. Changing the plan is not automatically a weakness. An explained adjustment can demonstrate self-management and critical thinking when you record what changed, why it changed, and how the new decision supported the goal.
Mistake 5: Treating the process journal as a diary
The process journal should preserve evidence of inquiry, decisions, problems, feedback, and development. Statements such as “I worked on my project today” reveal little about your thinking.
Useful records include dated drafts, photographs, screenshots, source notes, test results, supervisor-meeting notes, version histories, and explanations of important changes. A strong entry identifies what you did, what you learned, the decision that followed, the ATL skill involved, and the next step.
Do not invent a journal shortly before submission. If your record is incomplete, recover authentic evidence from dated files, messages, photographs, or document histories and explain the process honestly. Follow your school's instructions concerning journal extracts, supporting files, and submission limits.
Mistake 6: Naming ATL skills without explaining them
Criterion B does not reward a list such as “I used research, communication, and self-management skills.” You must explain how particular ATL skills helped you achieve the learning goal and create the product.
Use this structure:
Situation --> strategy --> evidence --> effect
For example: “To distinguish reliable nutritional guidance from social-media claims, I checked authors' qualifications, publication dates, references, and agreement with established health organizations. My evaluation table shows that I rejected two articles without identifiable authors. This strategy improved the accuracy of the recommendations in my guide.”
Research summaries are also insufficient unless you show their influence. Use the decision chain because I learned X, I changed Y, which affected Z. Cite borrowed facts, images, code, music, methods, and design assets consistently according to your school's required referencing system.
Mistake 7: Evaluating and reflecting in general terms
“I think my product was successful” is an opinion rather than an evaluation. Criterion C requires you to judge the product against its success criteria using evidence such as test data, feedback, measurements, screenshots, or observations.
| Success criterion | Evidence and judgment | Improvement |
|---|---|---|
| Ten users complete the task independently | Eight succeeded; two needed help finding the menu, so the criterion was partly met | Increase contrast and label the menu |
A partly met criterion does not ruin the project. Honest judgment often demonstrates more understanding than unsupported claims of complete success.
Reflection should then explain the project's impact on you or your learning. Instead of writing “I improved my time management,” identify the difficulty, strategy, and result. For example, explain how missing a prototype deadline led you to divide later work into short tasks, review progress weekly, and identify delays earlier.
Mistake 8: Writing the entire report at the end
Students who postpone writing often lose the evidence needed to explain ATL skills and important decisions. After each significant test, setback, research finding, or design change, draft several sentences explaining what happened and why it mattered.
Before submission, compare every section with the exact rubric rather than checking only spelling and presentation. The RevisionDojo Personal Project Grader can identify unclear explanations, but its feedback should be checked against your official rubric and supervisor guidance. You remain responsible for the report's reasoning, evidence, wording, and academic integrity.
Final Personal Project checklist
Confirm that your report:
- uses your school's current rubric and instructions;
- separates the learning goal from the intended product;
- explains the connection to personal interest;
- includes testable success criteria and a detailed plan;
- preserves evidence of research, drafts, testing, and changes;
- explains how ATL skills supported learning and product creation;
- evaluates every criterion with evidence;
- reflects on specific changes in your knowledge or abilities; and
- acknowledges all borrowed material.
Conclusion
Avoiding common MYP Personal Project mistakes depends on alignment. Your learning goal, product, success criteria, plan, ATL evidence, evaluation, and reflection should support one another and reveal how your thinking developed.
RevisionDojo's Personal Project examples can show how students communicate evidence without providing material to copy. You can also consult the Personal Project support overview and guide to common project mistakes, then use Jojo AI or the rubric-based grader to question and refine your own work.
