From user to insider: What working inside Lifelines taught me

Melissa first encountered Lifelines during her Master’s research, through a project focused on the development of ADHD across adolescence. In subsequent work, she studied the familial transmission of psychiatric disorders and comorbidity of psychiatric and somatic conditons. Across these projects, Lifelines functioned as a powerful and versatile data source.

From a researcher’s perspective, Lifelines initially appeared straightforward: a well-curated dataset that, once released by Lifelines data-management, could be analysed. “Especially in psychiatric research, the combination of questionnaires, biomarkers and genetic data is rare,” she says. What remained largely invisible, however, was everything that happens before and around the release of your dataset.

Before working internally, Melissa assumed that data management mainly involved preparing datasets and responding to researcher queries. “I expected the data managers to have all answers ready,” she explains. “What I didn’t realise was how much work goes into getting those answers in the first place.”

Inside Lifelines, she saw that data management operates at the intersection of content expertise, infrastructure, and accountability. Data managers are not simply service providers; they continuously coordinate with researchers, internal systems, and the companies that host the technical environments to ensure that data use remains possible, secure, and traceable.

Processes that can feel cumbersome from the outside, took on a different meaning from within. “As a researcher, it’s easy to experience registrations and procedural checks as bureaucracy,” she says. “Internally, you realise that Lifelines must very thoroughly demonstrate how their data are being used. This is essential for reporting, evaluations and, ultimately, for securing funding.”

Her view on amendments changed most noticeably. “From a research perspective, it feels like an unnecessary burden  to register an amendment when you will be using data to which you already have acces, especially when you will share the final publication anyway,” she notes. “Internally, you realise that not all researchers share their publications with Lifelines and, moreover, that not all data use results in a publication. Instead, data use is evaluated using internal registrations; meaning  that when changes are not documented, data use may simply not count.” This difference in incentives—publications versus demonstrable data use—explains some friction researchers may experience.

Melissa’s main insight is not that Lifelines is complex—most researchers already suspect that. What changed for her was understanding why that complexity exists, and what is at stake if it is underestimated. “As a researcher, you only encounter a small part of Lifelines,” she reflects. “From the inside, you see how much coordination, documentation, and human judgement is required to keep a cohort like this usable and credible.”

That perspective now shapes how she works with Lifelines data. Processes that once felt like an unnecessary burden are easier to place in context, not as obstacles to research, but as conditions for its continuity. Seeing Lifelines from both sides made one thing clear to her: sustainable data access depends as much on careful organisation and visibility of data use as it does on scientific output.