← Reflective analysis of developing a digital outcome

New knowledge and skills

Named as its own criterion in every schedule 2023–2025: explaining how new knowledge or skills guided the development process, not merely listing what you learned.

What separates a full answer from a weak one

  • A weak answer LISTS something learned: "I learned how to use Git."
  • A full answer explains HOW that knowledge changed what you did: "Learning to use Git meant I could safely try a risky refactor, knowing I could revert it — so I attempted a change I would otherwise have avoided."
  • The schedule rewards TWO distinct examples, each guiding the process in a different way — not the same skill described twice.
Exam-style New knowledge guiding the process Explain a piece of new knowledge or a new skill and how it guided your development process. NEW KNOWLEDGE: learned partway through that form input should be validated on both the client side (for instant feedback) AND the server side (because client-side checks can be bypassed). HOW IT GUIDED THE PROCESS: went back and added server-side validation that had been skipped, even though the interface already looked correct without it. WHY IT MATTERED: a tester who disabled JavaScript in their browser could otherwise have submitted invalid data straight past the form entirely. ✓ Naming when in the timeline the knowledge arrived, and what you went BACK and changed because of it, is what makes this guide the process rather than simply describe a fact you now know.

Where new knowledge typically comes from

  • A problem that FORCED research — something did not work, and finding out why taught you something you then applied.
  • Feedback from a teacher, peer, or online resource that introduced an approach you had not considered.
  • Trial and error during testing that revealed a gap in your own understanding of the tool or technique.

Practise just this