28 January 2014 2 Comments
Isn’t it brilliant when you learn something within a week of the new year?
When one of my academic buddies asked me in late 2013 what research developers are meant to do, I happily said, “Let me write a blogpost on that!”, and rubbed my hands with glee at the gift of an easy post to knock off in the new year.
I sat down to write this post, and was immediately bogged down in pondering the specificities and individualisation of the role. I realised that it wasn’t as straightforward as I’d thought.
Let me explain:
When I started this job three years ago (thank you, LinkedIn, for the congratulations), I was one of three research developers who were stepping into new positions. My Research Whisperer buddy @jod999 is another from this cohort. We each had responsibility for one of our institution’s colleges (similar to faculties). There was no-one there before us, and no standing expectations to fulfil.
There were expectations, of course, and these are otherwise known as our job descriptions.
As it turns out, though, each of us has cultivated different processes and priorities when carrying out our basic job of helping researchers find money to do their research.