Self-Determined Project Design Protocol

What This Skill Does

This skill encodes an original practitioner framework developed by Gareth Manning, educator, curriculum designer, and learning systems designer. Unlike skills in other domains, it is not drawn from peer-reviewed research traditions. It is grounded in serious engagement with learning science, original curriculum design work, and active classroom testing. It is included because the methodology is coherent, transferable, and genuinely useful — and because intellectual honesty requires distinguishing practitioner frameworks from research-validated approaches.

This skill guides both student and educator through the full arc of designing, planning, and executing a self-determined personal project — from initial idea through to completion, defence, and reflection. It specifies what BOTH parties need to do at each phase, how to calibrate ambition honestly, and how to build the knowledge and skill acquisition plan alongside the project itself. The output is a complete dual-perspective protocol: student-facing roadmap and educator-facing mentoring guide, phase by phase. The protocol maps directly to Zimmerman's (2000, 2002) self-regulated learning phases: forethought (Phases 1-3), performance (Phase 4), and self-reflection (Phase 5). Bandura (1997) informs the feasibility calibration: over-ambitious and under-ambitious projects both reflect miscalibrated self-efficacy, and the educator's role is to help students calibrate honestly without crushing agency. Ericsson & Pool (2016) inform the knowledge/skill acquisition plan: the skills a student needs to develop for their project constitute a deliberate practice design problem. The tracking system — a shared, visible artefact that both student and mentor can see at all times — is the structural backbone of the protocol. Without it, mentoring conversations have no shared reference point and project drift is invisible until it's too late.

Evidence Foundation

Manning developed this protocol through personal project mentoring in multiple international school contexts, most recently through capstone mentoring at REAL School Budapest. The methodology addresses a specific problem: most "independent project" programmes give students freedom without structure — resulting in either teacher-directed projects that aren't really self-determined, or student-led projects that drift, stall, or collapse because the student lacked the self-regulation skills to manage the process. Zimmerman (2000, 2002) provides the theoretical framework for the protocol's phase structure. His self-regulated learning model describes three cyclical phases: forethought (goal-setting, strategic planning, self-efficacy assessment), performance (self-monitoring, strategy use, help-seeking), and self-reflection (self-evaluation, attribution, adaptive responses). The protocol operationalises these phases: Phases 1-3 ARE forethought, Phase 4 IS performance, Phase 5 IS self-reflection. Bandura (1997) informs the feasibility calibration — the most critical and most frequently skipped part of the protocol. Self-efficacy (the student's belief in their ability to succeed) directly predicts effort, persistence, and resilience. But self-efficacy can be miscalibrated: a student who believes they can build an app in 6 weeks with no coding experience has inflated self-efficacy that will lead to demoralising failure. Equally, a student who says "I can't do anything interesting" has deflated self-efficacy that will lead to an uninspired project. The educator's role is to calibrate honestly: probing what the student actually knows, what they need to learn, and whether the timeline is realistic. Over-ambitious equals under-ambitious in terms of harm — a student who fails a project they weren't ready for learns the wrong lesson. Ericsson & Pool (2016) inform the knowledge/skill acquisition plan. The skills a student needs for their project — coding, woodworking, research methods, writing, design — are not acquired by wishing. They require deliberate, structured practice. The protocol builds a parallel skill acquisition plan alongside the project plan: what do you need to learn, how will you learn it, and how will you know when you've learned it? Black & Wiliam (1998) inform the milestone checkpoint design: each checkpoint is a structured formative assessment moment where the student self-assesses against the rubric, shares evidence, gets feedback, and adapts the plan.

Input Schema

The educator must provide:

• Student idea: The initial project idea. e.g. "I want to build a website for my mum's bakery" / "I want to write and illustrate a children's book about climate change" / "I want to design and build a model bridge that can hold 50kg" / "I want to learn to play guitar and perform at the school concert" / "I don't know what I want to do"
• Student level: Developmental band and age. e.g. "Band D, age 13" / "Band C, age 11" / "Band B, age 9"
• Available time: Total duration and weekly commitment. e.g. "One semester (18 weeks), 3 hours per week dedicated project time plus independent work" / "One term (10 weeks), 2 hours per week" / "Full year, 90 minutes per week"