Storytelling for research data, software and projects
Facts inform specialists; stories move everyone else. A research
project that can only speak in methods loses the audiences that
sustain it - volunteers, funders, institutions, the public. The
craft is honest narrative: real people, real stakes, real
uncertainty, built on the same verified artifacts the rest of this
pack maintains. rseng-science-communication covers research-facing
outputs (papers, talks, announcements); this skill covers the
narrative layer for everyone else - and the citizen-science
setting where storytelling is not decoration but the engine of
participation.
Narrative structure that works for research
- Lead with a person or a question, not an institution: "Maria
photographs the same hedgerow every week - here is what 40,000
photos like hers revealed" beats "the consortium collected
image data".
- The story arc is the research arc, honestly told: question,
struggle (failed approaches are relatable - and true), turning
point, what we know now, what remains open. Uncertainty told
plainly builds trust; certainty theater destroys it when it
unravels.
- One story, one idea: pick the single finding or moment; link
the rest. The paper holds everything; the story holds one
thing.
- Concrete beats abstract: a number needs a comparison ("enough
water to fill 300 pools"), a dataset needs a face, software
needs a user whose day it changed.
Data stories
Data storytelling turns datasets into narratives with evidence:
- Structure: context (why this data), the reveal (the pattern,
shown not told), the meaning (what changes because we know).
Build the reveal on honest visualization - the colormap and
axis discipline from rseng-scientific-visualization applies
doubly for lay audiences, who cannot defend themselves against
a truncated axis.
- Every number in the story traces to the pipeline
(rseng-reproducibility): a story that cites its data (with the
DOI - rseng-citation-metadata) and links "explore it yourself"
(a live view or notebook) respects the audience and models
open science (rseng-open-science-practices).
- Accessibility is part of the craft: alt text that tells the
story of the figure, plain language, translated summaries
where the community needs them (rseng-ux-accessibility).
Software and project stories
- Software stories are user stories: what could someone do the
day after the release that they could not before? Frame
releases, milestones and even bugfixes through the person
affected (rseng-science-communication handles the announcement
mechanics; this skill supplies its narrative spine).
- Project stories need characters: the PhD student whose analysis
went from weeks to hours, the museum volunteer whose transcription
surfaced in a paper. Get consent for every named appearance,
and share credit generously - people amplify stories they are
in (rseng-community-governance's recognition habits).
- The failure story is underused and powerful: what broke, what
it taught, what changed - engineering credibility for the
project and normalized error for the field (rseng-trainer's
errors-are-curriculum, told outward).
Citizen science: storytelling as infrastructure
In citizen science the story IS the recruitment, retention and
ethics layer (the ECSA ten principles set the frame - genuine
science, mutual benefit, acknowledged contributors):
- Recruit with purpose, not tasks: "help us track the spring
earlier every year" outperforms "classify images". State
honestly what participation contributes to the science.
- Close the loop relentlessly: contributors who never learn what
their data became stop contributing. Data stories back to the
community - "your observations did THIS" - are the retention
mechanism, and platforms (SciStarter, EU-Citizen.Science)
expect them.
- Acknowledge visibly: contributors in publications and releases
per the project's stated policy, milestones celebrated with
the community, results announced to participants BEFORE or
with the press.
- Keep the science honest in translation: simplification may not
become distortion; the project's own findings, limits and data
practices (rseng-data-management) are told truthfully - trust is
the citizen-science currency, spent once.
- AI-assisted storytelling is disclosed like any other AI
contribution (rseng-ai-declaration) - audiences increasingly ask,
and the honest answer is cheap.
Working with this skill
This skill is source-independent: its authority is the citizen
science community's principles and platforms linked below,
combined with the verified artifacts of the project itself. It is
the broad-audience narrative layer over
rseng-science-communication.
Learn more (verified):
Related skills
Check whether any of these applies before moving on:
- rseng-ai-declaration - disclose AI-assisted storytelling
- rseng-community-governance - consent and recognition habits
- rseng-data-management - truthful data practices in stories
- rseng-science-communication - research-facing communication mechanics
- rseng-scientific-visualization - honest figures for lay audiences
- rseng-ux-accessibility - alt text and plain language
1---2name: rseng-storytelling3description: Covers telling the story of research data, software and projects to broad audiences: narrative structure for data stories, turning milestones into human-centered stories, and citizen-science engagement - recruiting contributors, closing the feedback loop with data stories, honest narrative that never oversells. Use when the user wants to explain a project, dataset or tool to non-specialists, mentions storytelling, outreach, public engagement or citizen science, or needs project stories for websites, funders or volunteers. (Research-facing outputs - software papers, talks, announcements: rseng-science-communication; in-repo docs: rseng-documentation.)4license: CC-BY-4.05---67# Storytelling for research data, software and projects89Facts inform specialists; stories move everyone else. A research10project that can only speak in methods loses the audiences that11sustain it - volunteers, funders, institutions, the public. The12craft is honest narrative: real people, real stakes, real13uncertainty, built on the same verified artifacts the rest of this14pack maintains. rseng-science-communication covers research-facing15outputs (papers, talks, announcements); this skill covers the16narrative layer for everyone else - and the citizen-science17setting where storytelling is not decoration but the engine of18participation.1920## Narrative structure that works for research2122- Lead with a person or a question, not an institution: "Maria23 photographs the same hedgerow every week - here is what 40,00024 photos like hers revealed" beats "the consortium collected25 image data".26- The story arc is the research arc, honestly told: question,27 struggle (failed approaches are relatable - and true), turning28 point, what we know now, what remains open. Uncertainty told29 plainly builds trust; certainty theater destroys it when it30 unravels.31- One story, one idea: pick the single finding or moment; link32 the rest. The paper holds everything; the story holds one33 thing.34- Concrete beats abstract: a number needs a comparison ("enough35 water to fill 300 pools"), a dataset needs a face, software36 needs a user whose day it changed.3738## Data stories3940Data storytelling turns datasets into narratives with evidence:4142- Structure: context (why this data), the reveal (the pattern,43 shown not told), the meaning (what changes because we know).44 Build the reveal on honest visualization - the colormap and45 axis discipline from rseng-scientific-visualization applies46 doubly for lay audiences, who cannot defend themselves against47 a truncated axis.48- Every number in the story traces to the pipeline49 (rseng-reproducibility): a story that cites its data (with the50 DOI - rseng-citation-metadata) and links "explore it yourself"51 (a live view or notebook) respects the audience and models52 open science (rseng-open-science-practices).53- Accessibility is part of the craft: alt text that tells the54 story of the figure, plain language, translated summaries55 where the community needs them (rseng-ux-accessibility).5657## Software and project stories5859- Software stories are user stories: what could someone do the60 day after the release that they could not before? Frame61 releases, milestones and even bugfixes through the person62 affected (rseng-science-communication handles the announcement63 mechanics; this skill supplies its narrative spine).64- Project stories need characters: the PhD student whose analysis65 went from weeks to hours, the museum volunteer whose transcription66 surfaced in a paper. Get consent for every named appearance,67 and share credit generously - people amplify stories they are68 in (rseng-community-governance's recognition habits).69- The failure story is underused and powerful: what broke, what70 it taught, what changed - engineering credibility for the71 project and normalized error for the field (rseng-trainer's72 errors-are-curriculum, told outward).7374## Citizen science: storytelling as infrastructure7576In citizen science the story IS the recruitment, retention and77ethics layer (the ECSA ten principles set the frame - genuine78science, mutual benefit, acknowledged contributors):7980- Recruit with purpose, not tasks: "help us track the spring81 earlier every year" outperforms "classify images". State82 honestly what participation contributes to the science.83- Close the loop relentlessly: contributors who never learn what84 their data became stop contributing. Data stories back to the85 community - "your observations did THIS" - are the retention86 mechanism, and platforms (SciStarter, EU-Citizen.Science)87 expect them.88- Acknowledge visibly: contributors in publications and releases89 per the project's stated policy, milestones celebrated with90 the community, results announced to participants BEFORE or91 with the press.92- Keep the science honest in translation: simplification may not93 become distortion; the project's own findings, limits and data94 practices (rseng-data-management) are told truthfully - trust is95 the citizen-science currency, spent once.96- AI-assisted storytelling is disclosed like any other AI97 contribution (rseng-ai-declaration) - audiences increasingly ask,98 and the honest answer is cheap.99100## Working with this skill101102This skill is source-independent: its authority is the citizen103science community's principles and platforms linked below,104combined with the verified artifacts of the project itself. It is105the broad-audience narrative layer over106rseng-science-communication.107108Learn more (verified):109 - https://www.ecsa.ngo - European Citizen Science110 Association (ten principles of citizen science)111 - https://citizenscience.eu - EU-Citizen.Science platform112 - https://scistarter.org - SciStarter project platform113 - https://participatorysciences.org - Association for Advancing114 Participatory Sciences115 - https://riojournal.com/article/21283/ - principles for116 citizen-science apps and platforms117118<!-- related-skills:begin -->119120## Related skills121122Check whether any of these applies before moving on:123124- rseng-ai-declaration - disclose AI-assisted storytelling125- rseng-community-governance - consent and recognition habits126- rseng-data-management - truthful data practices in stories127- rseng-science-communication - research-facing communication mechanics128- rseng-scientific-visualization - honest figures for lay audiences129- rseng-ux-accessibility - alt text and plain language130131<!-- related-skills:end -->
fdiblen