Page 1 of 1
5-minute research: how research teams find (or lose) their own prior knowledge.
Short research study: what makes research planning, execution, and reproduction slow or painful, especially for early-career researchers. 5 minutes, anonymous unless you choose to share contact.
1. Your role?
*
A
PhD/grad student
B
Postdoc/staff scientist
C
PI/group leader
D
Lab manager/data steward/IT
E
Industry R&D scientist
F
R&D director/lead
G
CRO
2. Primary research environment?
*
A
Academic lab
B
University hospital/translational
C
Public research institute
D
Biotech/pharma
E
CRO
F
Other industry R&D
3. Team size whose artifacts you need to understand/reuse?
*
A
1-5
B
6-15
C
16-50
D
51-200
E
200+
4. Where do those artifacts live today?
*
GoogleDrive/OneDrive/Dropbox
SharePoint/Confluence/Notion
Zotero/Mendeley/EndNote
Benchling/Labguru/SciNote/other ELN
Slack/Teams/email
GitHub/GitLab
Local folders
5. In the last 30 days, how often did you search for prior lab/project knowledge that should already exist?
*
A
Never
B
1-2×
C
Weekly
D
Several×/week
E
Daily
6. Most recent time - how long to find the answer?
*
A
<5 min
B
5-30 min
C
30 min-2 h
D
Half a day
E
A full day+
F
Never found it
7. How costly is this for your team?
*
A
Annoying, not costly
B
Hours monthly
C
Hours weekly
D
Delays experiments/projects
E
Duplicated work / wrong decisions
F
Compliance/audit/publication risk
8. New joiner - time until they understand what's been tried and why?
*
A
<1 wk
B
1-2 wk
C
3-4 wk
D
1-3 mo
E
>3 mo
9. How well can you currently answer 'have we tried this before, and what happened?"
*
A
Very well
B
Adequately
C
Poorly
D
Not at all
11. What workaround have you built?
*
12. If you could get an instant, trustworthy answer to any one question about your team's past work, what would it be?
*
13. Can we contact you for a 15-min follow-up?
Submit