Skip to content

Critical Reflection

Critical reflection means looking back at your work to understand not only what you did, but why it happened that way, and what you can learn from it. It is not just evaluation (“It worked” or “It didn’t”), but deeper questioning of your choices, assumptions, and outcomes. For example, after testing an interactive prototype, you don’t just note that users got confused; you ask why they got confused, and what that means for your design.

Why is this relevant to you? Because as a Creative Technologist, your projects are complex and experimental. Reflection helps you grow: you identify what worked, what didn’t, and how you can improve in the next iteration.

Starting Points

  1. After each sprint or test, take 10 minutes to write down what surprised you.
    Example: “Users kept pressing the wrong button, even though I thought it was obvious.”
  2. Compare your expectations with reality.
    Example: “I expected the sensor to be stable outdoors, but wind made it unreliable.”
  3. Use reflection questions: What worked well? What was difficult? What will I do differently next time?

Key Points

  1. Be honest about both successes and failures; you learn from both.
  2. Look beyond technical outcomes: reflect on teamwork, planning, and communication too.
  3. Link your reflection to evidence: use data, feedback, or concrete examples instead of vague impressions.
  4. End each reflection with an actionable step.
    Example: “Next sprint, I will test the interface with non-technical users earlier.”