How did you first learn about Researchfish and why did you decide to join the team?
I worked with Researchfish, before it was even known as Researchfish! My previous role at the Medical Research Council (MRC) meant I became involved with e-Val and watched it evolve into the service it has become today. My role was to analyse the data, with specific responsibility for the evaluation data, pulled first from e-Val and then Researchfish.
I enjoyed working with the data from Researchfish and helping MRC to understand and use it in everyday situations. I was lucky enough to be able to help other funders and research councils in a similar way and part of the reason for moving to Researchfish was the opportunity to do that on a bigger scale.
What is your role at Researchfish? And what are you responsible for?
My role within Researchfish is Chief Analyst and I am primarily responsible for a data team.
I bring specialised knowledge about understanding research information across lots of different areas and different systems, and understanding how they can connect together. My role is about showing how to use that information to get new insights and, ultimately, to reduce the burden on researchers and increase the quality of the data available.
I also do a lot of work on the development side of the service, helping to ensure that data is being captured in the right way, and ensuring decisions made around the software are aligned with future opportunities.
Before working at Researchfish, what was the most unusual or interesting job you’ve ever had?
I worked for the Vice President for Student Affairs at the University of Virginia and got to work with offices all across the University from Student Health, Housing and Communications to the Dean of Students and Residence Life.
If you could switch your job with anyone else within Researchfish for a day, whose job would it be and why?
I wouldn’t swap my role as I think that I already have the best job (though I may be biased).
What are three words you would use to describe Researchfish?
Dedicated, enthusiastic and innovative.
What do you think will be the most challenging part of your role at Researchfish?
That would be the combination of development moving quite slowly in some ways and very fast in others! There is a lot of work which needs to happen behind the scenes before you can start to see the results. For example, the launch of the Reporting Beta has involved a great deal of work by a lot of people over almost a year, but now this is visible users can really start to see the benefit.
What is on your wish list for the next year working with Researchfish?
An ice machine in the office as I always like a lot of ice!
On a more serious note, I would like to see more integration with external sources to help people report outcomes more easily.