SkarpChapter 9 of 10
Working Like a Research Team: Notebooks, Collaboration, and Feedback
See how professional labs stay organized and productive through meticulous notebooks, shared responsibilities, and constructive critique.
Big Picture: How Real Labs Work as Teams
Science as a Team Sport
In modern biology labs, science is a team sport. Experiments rarely belong to one person from start to finish; groups share protocols, data, and ideas using systems that keep work traceable and reproducible.
Link to Previous Modules
This module connects your report and presentation skills to the upstream work: keeping a usable notebook, collaborating smoothly, and giving/receiving feedback that strengthens your science.
What You Will Be Able To Do
You will learn to: 1) maintain clear lab notebook entries, 2) divide tasks and communicate in lab groups, and 3) give and receive constructive feedback on experiments and scientific writing.
Current Lab Practices
We will emphasize practices that match how labs work today (2026), including the growing use of electronic lab notebooks (ELNs) alongside traditional bound notebooks.
Step 1: Core Principles of a Good Lab Notebook
What Is a Lab Notebook?
A lab notebook, paper or electronic, is a legal and scientific record of what you did, when, and why. It must let another trained scientist understand and, in principle, repeat your work.
Core Principles
Good notebooks are: 1) permanent (ink or versioned ELN), 2) dated and signed, 3) complete but concise, 4) chronological, 5) legible and organized, and 6) clearly attributable to specific people.
Entry Structure
A typical entry includes: title and date; objective; materials and methods (planned); procedure notes (actual steps and deviations); results; and a short interpretation or next steps.
Why It Matters
These practices are standard across universities, industry, and government labs and are closely tied to research integrity and reproducibility.
Step 2: Model Lab Notebook Entry (Annotated)
Entry Header
Title: Effect of glucose concentration on yeast growth; Date: 11 July 2026; Researchers: A. Lee (primary), J. Patel (plating), M. Gomez (OD readings). Clear who did what and when.
Objective and Plan
Objective: Test how 0%, 1%, and 5% glucose affect yeast growth over 24 h. Planned methods: strain, media, starting OD, incubation conditions, and measurement plan are clearly listed.
Procedure Notes
Procedure notes include time-stamped actions, minor deviations (OD600 = 0.11, 5.1% glucose), and observations (clumping, vortexing). This reflects what actually happened, not just the plan.
Results and Interpretation
Results reference raw data files and summarize mean ± SD. The interpretation is brief, notes possible reasons for patterns, and proposes specific next steps without overstating conclusions.
Step 3: Improve a Weak Notebook Entry
Activity: Read the weak notebook entry below, then list 3 concrete improvements you would make.
---
Weak Entry:
"Date: 3/4
Did yeast lab today. Set up cultures and put them in incubator. Took some OD readings later and wrote them in my notes. 5% sugar seemed bad. Will redo next week."
---
Your task (think or write):
- What critical information is missing for someone to repeat this experiment?
- How could you rewrite the objective so it is specific and testable?
- How would you structure the entry to separate plan, actions, and results?
Hint: Compare to the model entry from the previous step. Think about dates, conditions, who did what, and where the raw data are stored.
If you are in a group, take 2 minutes to individually mark up the weak entry, then 3 minutes to agree on a shared improved version.
Step 4: Roles and Communication in Lab Teams
Complementary Roles
Small lab teams work better when members have complementary roles: coordinator, protocol specialist, data manager, and presenter/writer lead. Roles can be combined or rotated.
Role Details
The coordinator tracks plans and timelines; the protocol specialist monitors reagents and steps; the data manager organizes files; the presenter/writer lead shapes figures and text.
Pre-, During-, Post-Lab
Use short pre-lab huddles to set goals and roles, quick during-lab check-ins to sync, and post-lab debriefs to confirm what was done and how data and writing tasks are divided.
Link to Real Labs
These habits mirror real research practice, where teams use lab meetings and project stand-ups to coordinate ongoing experiments and shared datasets.
Step 5: Plan Your Team Workflow
Imagine you are in a 4-person team doing a semester-long project measuring the effect of a drug on bacterial growth.
Scenario details:
- You will run the same assay 4 times to check reproducibility.
- Each run generates OD600 curves plus images of plates.
- You must submit a joint lab report and give a 5-minute group presentation.
Your task:
- Assign one primary role to each of the 4 teammates from this list: coordinator, protocol specialist, data manager, presenter/writer lead.
- For each role, write one specific responsibility related to:
- Lab notebooks
- Communication
- Final report or presentation
- Decide how you will handle role rotation (if at all) across the 4 assay runs.
If working alone, sketch this plan in bullet points. If working with others, discuss and agree on a plan in 5 minutes.
Step 6: Giving Constructive Scientific Feedback
Why Feedback Matters
Science depends on peer review: other scientists critically but constructively evaluate your work. Your comments on classmates' designs or drafts are practice for this real-world process.
Specific, Not Vague
Constructive feedback is specific: instead of "Methods are confusing," say exactly what is unclear, such as the number of replicates or how treatments were randomized.
Focus on Work, Not Person
Target the work, not the person. Replace "You are bad at statistics" with feedback about the choice of test and assumptions, plus suggestions for alternatives.
Balanced and Actionable
Good feedback notes strengths and offers a few prioritized, concrete suggestions. A simple pattern: start with strengths, then suggestions, then check your understanding of their main message.
Step 7: Rewrite Feedback to Make It Constructive
Transform the unhelpful comments below into constructive scientific feedback.
- "Your graph is terrible. I can't read it."
- "This experiment is pointless."
- "You clearly don't understand controls."
Your task:
For each comment, rewrite it so that it is:
- Specific
- Focused on the work, not the person
- Actionable
Example transformation:
- Unhelpful: "Your introduction is bad."
- Constructive: "The introduction would be clearer if you briefly defined 'osmotic stress' and added 1–2 sentences explaining why yeast is a good model organism for this question."
Write your improved versions. If you are with a partner, compare answers and discuss which versions feel most respectful and most useful.
Step 8: Quick Check on Notebooks and Teamwork
Answer this question to check your understanding of best practices.
Which option best follows current best practices for a shared lab notebook entry in a team experiment?
- One person writes a brief summary at the end of the week from memory, without dates or names, to avoid clutter.
- Each student keeps completely separate notes, and the team never combines them, to avoid conflicts about who did what.
- The team maintains a dated entry for each experimental run, listing all team members and clearly noting who performed key tasks, with raw data files linked or attached.
- Only the team member who will write the report needs to keep detailed notes, because others' contributions will be described in the acknowledgments.
Show Answer
Answer: C) The team maintains a dated entry for each experimental run, listing all team members and clearly noting who performed key tasks, with raw data files linked or attached.
Current best practice is to keep dated, detailed entries for each run, clearly attributing tasks and linking to raw data. This supports reproducibility, fair credit, and later report or poster writing.
Step 9: Key Term Review
Use these flashcards to review core concepts from the module.
- Lab notebook (research context)
- A permanent, dated, and attributable record of experimental plans, procedures, data, and interpretations, kept so that another trained scientist can understand and in principle repeat the work.
- Electronic lab notebook (ELN)
- A digital system for recording experiments with features like time-stamping, version history, file attachments, and sharing. Used increasingly in academic, industry, and government labs.
- Raw data
- Original measurements or observations (e.g., OD600 readings, images, sequencing files) recorded before processing or analysis. Should be clearly stored and referenced from the notebook.
- Team role: data manager
- The person primarily responsible for organizing, naming, backing up, and documenting data files so that the whole team can find and understand them.
- Constructive feedback
- Feedback that is specific, focused on the work (not the person), balanced between strengths and improvements, and provides actionable suggestions.
- Peer review (course context)
- The process of classmates or colleagues critically evaluating each other's experimental designs, reports, or presentations to improve clarity and scientific rigor.
Key Terms
- Raw data
- Original, unprocessed measurements or observations collected during an experiment.
- Team roles
- Defined responsibilities within a lab group (e.g., coordinator, protocol specialist, data manager, presenter/writer lead) that help organize work.
- Peer review
- Evaluation of scientific work by others with relevant expertise; in courses, this usually means classmates reviewing each other's designs or writing.
- Lab notebook
- A bound or electronic record where experiments are documented in a permanent, dated, and organized way so that work is traceable and reproducible.
- Constructive feedback
- Specific, respectful comments that highlight strengths and suggest clear improvements to scientific work.
- Electronic lab notebook (ELN)
- A digital platform for recording experiments, often with time-stamping, version control, and file attachment features.