Research Data Management
The controlled handling of participant details, notes, recordings, transcripts, and outputs across collection, access, retention, sharing, and deletion.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/research-data-management/
01What it means
Research data management applies documented privacy, security, consent, retention, and access rules to the information created during user research. It separates recruitment details from study evidence where possible and maintains enough traceability to honor participant choices without exposing identity unnecessarily.[1][2]
- 01PlanPurpose, minimization, consent, roles, systems, and retention
- 02Collect securelyParticipant details, notes, recordings, and artifacts
- 03Separate + protectIdentifiers, research data, keys, access, and transfer
- 04Process responsiblyTranscription, redaction, analysis, and quality context
- 05Share selectivelyAudience, permissions, provenance, and reuse conditions
- 06Retain or deleteApply schedule, withdrawal promises, and verified disposal
De-identification reduces but does not eliminate re-identification risk; consent, purpose, sensitivity, legal duties, and participant expectations shape every lifecycle decision.
02Why it matters
Research routinely creates sensitive personal data in notes, recordings, screen captures, and prototypes. Deliberate management reduces harm and legal risk while keeping evidence findable, interpretable, and usable within the permission participants gave.
03When to use it
Plan data management before recruiting or recording anyone and scale controls to sensitivity, identifiability, and organizational obligations. Consult privacy, legal, security, or ethics specialists when handling regulated or high-risk information.
04How it works
- Inventory the personal and research data the study genuinely needs.
- Define lawful purpose, consent boundaries, access, storage locations, naming, retention, and deletion.
- Collect the minimum data and separate identities from research records using participant codes where practical.
- Secure transfers, tools, recordings, analysis, and sharing; redact or anonymize outputs appropriately.
- Review access and retention, honor withdrawals, and delete data safely when its permitted use ends.
05A practical example
A health-app team stores contact details in a restricted recruitment system, labels notes with participant codes, excludes live medical data from its prototype, redacts clips used in a readout, and schedules recording deletion after analysis.
06Where it breaks
Anonymization can be difficult when stories or roles are distinctive, and removing identifiers can reduce analytic context. Policies and legal duties vary; this topic is not a substitute for professional privacy or legal advice.
Common mistakes
- Collecting sensitive details because they might be useful later.
- Uploading recordings or transcripts to unapproved tools.
- Keeping identifiable raw data indefinitely after the stated purpose has ended.
07Sources
- Managing user research data and participant privacyGOV.UK Service Manual · Government privacy guidanceManaging user research data and participant privacy
- Taking notes and recording user research sessionsGOV.UK Service Manual · Government service guidanceTaking notes and recording user research sessions