How to Document Failed Experiments and Why You Should
Not every experiment works. Some give unexpected results, some fail because of a technical problem and others leave you with data that simply does not make much sense. When that happens, it is tempting to move on quickly, change something and try again.
But failed experiments are still part of your research. Documenting them properly can prevent you from repeating the same mistakes, help you understand unexpected patterns and give important context to the experiments that follow. You do not need to turn every failed experiment into a detailed investigation. You just need to record enough to understand what happened when you come back to it later.
Document the Experiment Before Deciding Why It Failed
When an experiment goes wrong, it is easy to immediately start looking for an explanation. Maybe the cells were unhealthy, the concentration was wrong or there was a problem with the equipment. Those explanations might eventually turn out to be correct, but at this stage they are still interpretations.
Start by documenting what actually happened. Record the experiment just as you would if it had worked, including the aim, conditions, protocol, observations, results and where the data is stored. Then add your thoughts about what might have caused the problem separately. Keeping observations and interpretations distinct makes it much easier to revisit the experiment later without treating an early assumption as a fact.
Avoid Writing Only “Failed”
A failed experiment still produced information. Writing something like “experiment failed, repeat next week” might make perfect sense while everything is fresh in your mind, but a few months later it tells you almost nothing.
Instead, be specific about what made you consider the experiment unsuccessful. Maybe you saw no signal, the controls behaved unexpectedly, contamination occurred or the results were simply too inconsistent to interpret. You do not need a long explanation. A few clear sentences about what you observed can make the record considerably more useful later.
Record Anything That Was Different
Small deviations are often the details that disappear first, especially when you are trying to remember an experiment months after it happened. If something differed from your usual procedure, write it down while you still remember it.
Perhaps an incubation was longer than planned, a reagent came from a new batch or a sample looked unusual before you started. Maybe you used a different instrument because the usual one was unavailable. These details may have nothing to do with why the experiment failed, and that is completely fine. The purpose is not to identify the cause while documenting. It is to preserve information that could become relevant later.
The same applies to changes you made intentionally. If you deviated from your usual protocol, include both what you changed and why you changed it.
Keep the Original Data
Data from an unsuccessful experiment can still be useful. Something that looks meaningless today might make more sense once you have performed another experiment, changed a condition or discovered a pattern across several attempts.
Unless there is a reason not to keep it, preserve the raw data and make sure your experiment notes tell you where it is stored. This does not mean copying every large dataset into your notes. A clear file path, dataset name or storage location may be all you need.
The important part is maintaining the connection between the experiment and its data. You should be able to return to an old experiment and find the relevant files without searching through folders and trying to remember how you named things at the time.
Write Down What You Would Change Next Time
Once you have documented what happened, think about what comes next. If you plan to repeat the experiment, record what you want to change and why.
This can be very simple. You might want to use a lower concentration, prepare a fresh reagent, add another control or repeat the experiment under exactly the same conditions before changing anything. You may also decide that you need to discuss the result with your supervisor or research group before choosing the next step.
Writing this down while the experiment is still fresh preserves the reasoning behind your next decision. When you eventually return to the work, you do not have to reconstruct what you were thinking.
Connect Repeated Experiments
Research often develops through several attempts at the same experiment. The first attempt produces an unexpected result, so you change one condition. The second raises another question and the third finally starts to make sense.
Those experiments are much more useful when you can understand them as a sequence rather than as isolated records. When repeating an experiment, make it clear what changed from the previous attempt and why. A note as simple as “Repeated using a lower antibody concentration after high background in the previous experiment” preserves the reasoning behind the change.
Over time, this gives you a record not only of the experiments themselves but also of how your thinking developed throughout the project.
Look for Patterns Across Unsuccessful Experiments
One failed experiment might not tell you very much. Several failed experiments can.
If the same problem keeps appearing, good documentation makes it possible to compare your previous attempts. You might notice that the issue began after changing a protocol, only occurs with a particular reagent or appears under a specific set of conditions.
This is one of the reasons it is worth documenting unsuccessful experiments with the same basic structure as successful ones. If every failure is recorded differently, or barely recorded at all, comparing them becomes unnecessarily difficult.
You do not need to know which details will matter when you write them down. Consistent records give you the opportunity to make those connections later.
Do Not Clean Up the Story Too Much
Research documentation can easily become a cleaner version of what actually happened. Successful experiments receive detailed records while unsuccessful attempts get a sentence or disappear entirely.
The problem is that research rarely develops in such a straight line. Unexpected results, technical problems, repeated experiments and changes in direction are all part of the process. Removing those parts from your records can also remove the context that explains why later decisions were made.
This does not mean every mistake needs extensive documentation. If an experiment stopped because a machine failed halfway through, recording what happened may be enough. The amount of detail should reflect how useful the information is likely to be later.
Failed Experiments Are Still Part of Your Research
A useful research record should show what actually happened, not only the experiments that produced the result you hoped for. An unsuccessful experiment can tell you what did not work, help explain why you changed direction and prevent you from repeating something you have already tried.
The most important thing is to make documenting these experiments part of your normal process. Record what happened, keep the relevant data, note anything unusual and leave enough context for the next attempt. Your future self should not have to rely on memory to understand why an experiment was repeated or changed.
Documenting Experiments With LabMemo
LabMemo gives every experiment its own place inside the project it belongs to, whether the experiment worked or not. You can document your aim and results, record where your data is stored and link the Master Protocol you used. When additional context is useful, you can also add images, tables, files and voice memos.
Experiments remain alongside the notes and meetings from the same project, creating a record of how the research has developed over time. This makes it easier to keep previous attempts visible rather than only documenting the final successful version.
LabMemo is built to make research documentation easier to maintain as your projects grow. Try LabMemo free for 30 days with no card required.