← Reflective analysis of developing a digital outcome
Critiquing the outcome and the process
The Excellence-level task, every year on record: critique BOTH the outcome and the development process, and draw a conclusion — not just list what you would change.A critique needs a standard to critique against
- State what the outcome or process was TRYING to achieve, then judge how well it actually achieved that — a critique with no stated goal is just a list of complaints or compliments.
- Ground the critique in evidence you already have: testing results, user feedback, or a problem you had to work around, not a new idea invented for the exam.
- A conclusion draws the pieces together: given everything discussed, was the outcome successful, and what would matter most to fix first?
A list of "things I would change" is not a critique
Excellence asks you to CRITIQUE and draw CONCLUSIONS, not simply enumerate possible changes. "I would add more features" or "I would test more" restates the task without judging anything. A real critique states what was good or bad AND WHY, measured against what the outcome or process was meant to achieve.Drawing a conclusion, not just two critiques side by side
- State whether the outcome was successful RELATIVE TO its own purpose — not a vague overall judgement.
- Say what would matter most to fix first, and why that one thing outranks the others.
- A conclusion is a synthesis of everything discussed, not a new, unrelated final thought.