Reflective practice for researcher developers: strengthening your impact over time

Reflective practice for Research Development Managers and researcher developers in UK higher education, from Resourceful Researchers.

Researcher developers spend their year improving the practice of other people. PhDs, ECRs, fellowship applicants, PIs — the work is, almost by definition, about helping someone else become better at the thing they do. It's surprisingly common to find that the developers themselves haven't had a regular space to reflect on their own practice in months, sometimes years.

Reflective practice for the people who deliver researcher development isn't a luxury. It's the thing that keeps the work fresh, keeps the practitioner credible, and stops the slow drift into running the same workshop the same way for the seventh year running.

Why reflective practice matters for RDMs

Research development as a profession is unusually exposed. You're working across faculties that rarely talk to each other, with cohorts that rotate every year, in a culture where the impact of your work is often invisible until much later. Most of the obvious feedback loops are weak.

Strong reflective practice fills the gap. Not in a poetic, journal-with-a-candle way — in a structured, practical way that takes maybe an hour a fortnight and changes how the year goes.

The RDMs I see do this well tend to do three things:

They keep a running list of what surprised them. The session that landed differently than they expected. The participant who took the workshop somewhere it wasn't designed to go. The conversation in the corridor after a session that revealed something the session itself missed.

They review the list quarterly, on purpose. Not to draw conclusions immediately — to notice patterns. The patterns are the curriculum for next year.

They have a person, or a peer group, to think out loud with. Not for advice. For the act of articulation. Saying it out loud is half the work.

A practice you can start tomorrow

At the end of any session you deliver, before you do anything else, write three lines:

  • What surprised me?
  • What landed less well than I expected, and what's my best guess as to why?
  • What's the smallest adjustment I'd want to try next time?

That's it. Three lines, fortnightly. Compounded over a year, they're a more honest curriculum review than most institutions ever produce.

If you'd like to talk about reflective practice as part of a researcher-developer programme — for yourself, your team, or a regional network — get in touch.

Bring practical training to your researchers

Tell me about your group and I'll suggest the format and timing that fits.

Contact