ELITMa is currently under development and may change at any point - it is not meant for production use
Skip to aside Skip to content Skip to footer

Communication: Foundations of communication in research infrastructures

Communication is already happening in your Node – the question is whether it's working. This section helps you understand the difference between internal and external communication, why both matter in a distributed infrastructure like ELIXIR, and how to take stock of where your Node currently stands.
Page image

You may not have “communications” in your job title. But if you coordinate a project, lead a work package, manage a team, or represent your Node in any capacity – you are already communicating on behalf of ELIXIR. The question is not whether you communicate, but how intentionally you do it.

In a distributed network like ELIXIR, where 22 Nodes operate across different countries, cultures, and institutional contexts, communication is the connective tissue. When it works well, it’s invisible. When it doesn’t, the costs are real: duplicated effort, missed opportunities, missed authority in research grants, misaligned expectations and outputs that never reach the people who needed them.

This module won’t turn you into a communications expert. It will help you communicate more deliberately – and know when to ask for help.

Internal vs external: two different jobs

All communication in ELIXIR falls into one of two categories, and confusing them is one of the most common mistakes:

  • Internal communication is the flow of information within your Node or across the consortium — project updates, shared decisions, meeting outputs, cross-Node coordination. Its goal is alignment. When it fails, people duplicate work, miss deadlines, or pull in different directions.
  • External communication is how you present your work to the world – to funders, policymakers, researchers outside ELIXIR, and the public. Its goal is impact. When it fails, good work goes unnoticed and opportunities are missed.

The same output often needs both. A new service your Node launches needs internal communication so the consortium knows about it – and external communication so potential users find it or to gain visibility for funding and sustainability.

A scenario you’ll recognise

Two Work Package leads in a multi-Node project each spent months producing what turned out to be near-identical outputs. Neither knew the other was doing it. There was no shared update mechanism, no agreed communication touchpoint, and no moment where someone asked: who else needs to know what we’re doing?

This isn’t rare. It’s the default when communication is treated as something that happens after the work, rather than alongside it.

Quick exercise: your communication audit

Reflect on a current or recent project.

  • Do all active members know where to find the latest updates?
  • Have I identified which outputs are worth communicating beyond the project team?
  • Is there a clear process for sharing successes and lessons learned?
  • Are our members aware of current objectives?
  • Are the channels I’m using actually working?

What’s next

Communicating research and, in particular, inside Research Infrastructures, is complex, but the end communications piece should not reflect that complexity.

This short module will help you understand how to take action on some of the easy steps and give you cues for ELIXIR-specific applications.

Dive deeper

Category Resource Description
External resource Communication Toolkit for European Projects
External resource Communication Toolkit for Research Infrastructures

Related pages