[Brainstorming] What is the RAM "skillset" or "expertise" to research teams?

[dingaaling]

Summary

• This is an open Github issue for asynchronous brainstorming about ^ that key question
• For whenever inspiration hits... drop a comment :)

What needs to be done?

• Add any thoughts here about this question
• Ultimately wrap these thoughts into our external comms docs

Who can help?

• Any and every RAM

---

Updates

• Issue starting based on convo with @f-rower in a 1:1, but everyone is welcome to contribute

[dingaaling]

From brainstorming with @f-rower

"RAMs don't just do things on a checklist... we make sure the right thing is built"

• for the research team/skills at hand
• for the user
• for maximising real world impact

[dingaaling]

@f-rower point about

• RAM as research methodology vs.
• RAM as professional role/career pathway/skillset

[dingaaling]

Another brainstorming convo with @f-rower:

• What is the unique perspective/contribution we can bring to conversations in a research team, programme, field, conference/workshop?
• What is the value of "translational research"? What is the relationship between foundational and translational research in your field?
• If we just focus on translation, how is that different than "consultants"?

[harisood]

Some thoughts from RAM meeting 04/12:

• What meetings should we be in?

  • This was raised by Fran, as in a workshop he was in recently the people there already had domain and impact knowledge and expertise.
  • IMO, if a research is already doing RAM stuff (translation, impact, etc.) really well, we probs shouldn't be there, at least from a value add POV. Could be there from a learning perspective though!
  • Sometimes it may feel like RAM views aren't needed/wanted in a meeting, that can often be because people just aren't thinking about it properly. Sometimes being a RAM and advocating for it causes some tension as it's a different way of thinking/approach, but is kinda needed to shape projects in the right direction

• What skills/expertise do RAMs have?

  • Theoretical knowledge - this is stuff we learn from training/reading/papers etc. I think we should be doing more of this proactively (finding papers, reviewing them, writing papers, networking with experts etc.
  • Our own experiences. When we've run workshops, engaged stakeholders, made strategy, done user testing, brought two programmes together etc, what have we learned and what went well/didn't go well? This should be easier to share from a personal perspective, finding a way to bank this knowledge across the team would be huge

[f-rower]

I have found some resources that might be worth considering from the theoretical perspective. Worth considering if you have time and are in look of fresh perspectives on translational research!

• Assessment, evaluations, and definitions of research impact: A review
• What Is Societal Impact of Research and How Can It Be Assessed? A Literature Survey
• Conceptualizing and communicating value in business markets: From value in exchange to value in use
• Creating and managing value in collaborative networks

[f-rower]

@harisood you shared some great analyses on the RAM Slack channel, could you add those here?

[harisood]

Mainly just shared pics I like, e.g.

Can't remember what I thought about them though!

[aldenc]

summarise in discussions folder