01202 006 464
learndirectPathways

Reflecting on Research: Critical Evaluation of Methods and Findings

Podcast episode 49: Reflecting on Research: Critical Evaluation of Methods and Findings. Alex and Sam explore key concepts from the Pearson BTEC Higher Nationals in Computing. Full transcript included.

Series: HTQ Computing: The Study Podcast  |  Module: Unit 9: Computing Research Project  |  Episode 49 of 80  |  Hosts: Alex with Sam, Computing Specialist
Key Takeaways
  • Reflective practice involves stepping back from an experience to consider what happened, why it happened, and what you would do differently in future.
  • Gibbs' Reflective Cycle and Kolb's Experiential Learning Cycle are established frameworks for structuring reflective writing in an academic context.
  • Reflecting critically on your methodology means honestly appraising whether your chosen methods were the most appropriate and effective for your research.
  • Limitations identified through reflection are not failures; they are evidence of intellectual honesty and a mature understanding of research practice.
  • The habit of regular reflection is a key component of CPD, transferring naturally from academic research into professional practice after graduation.
Listen to This Episode

Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.

Start learning →
Full Transcript

Alex: Today we're covering reflection on research, which is the final lesson in Unit 9. Sam, what does it mean to reflect critically on your research?

Sam: Critical reflection means stepping back from your research and evaluating it honestly: not just what you did, but how well you did it, what you would do differently, and what you've learned about yourself as a researcher. It requires a degree of intellectual honesty that can feel uncomfortable, because it means acknowledging weaknesses and limitations rather than just presenting your work in the best possible light.

Alex: Are there structured frameworks for reflection that students can use?

Sam: Several good ones. Gibbs' Reflective Cycle is one of the most widely used in academic contexts. It takes you through six stages: description, what happened; feelings, how did you feel; evaluation, what was good and bad about the experience; analysis, what sense can you make of it; conclusion, what else could you have done; and action plan, what will you do differently next time. It's structured enough to be useful but flexible enough to accommodate different types of reflection.

Alex: Kolb's experiential learning cycle is related, isn't it?

Sam: Yes. Kolb's model describes learning as a cycle: a concrete experience leads to reflective observation, which leads to abstract conceptualisation, which leads to active experimentation, which generates a new concrete experience. The idea is that learning happens through a cycle of doing, reflecting, theorising, and experimenting, not just through absorbing information. It emphasises that experience only becomes learning when it's followed by deliberate reflection.

Alex: What specific aspects of research methodology should students reflect on?

Sam: Start with your research design: was it the right approach for your research question? Would a different methodology have produced better or more robust findings? Then reflect on your data collection: did your instruments work as intended, were there questions that participants struggled with, did you reach the right participants? Then your analysis: were your methods appropriate for the type of data you had, and did you handle the data rigorously?

Alex: What about reflecting on the outcomes themselves?

Sam: Reflect on whether your findings actually answered your research questions. If they didn't fully, why not? What assumptions did you make that turned out to be incorrect? What would you need to do differently to address the remaining questions? And reflect on the quality of your reporting: was your writing clear, were your conclusions properly supported by your evidence, were your recommendations realistic?

Alex: How does this reflective practice extend beyond the academic context?

Sam: It becomes a fundamental professional habit. The best computing professionals are constantly reflecting on their work: why did this project succeed or fail, what did I learn from this experience, how would I approach this differently next time? This habit of reflection is what drives continuous improvement, both individually and in teams. The computing professionals who grow fastest are those who treat every project as a learning opportunity and extract lessons systematically.

Alex: Brilliant. Thanks Sam. We move into Unit 10: Business Process Support in the next lesson.