HS
Hydrological Sciences

The value of failure: Learning from what didn’t work

The value of failure: Learning from what didn’t work

“What failure prepared you for later success?” Tim Ferriss often asks this question to the high-performing guests on his podcast, giving them the opportunity to reflect on how setbacks have shaped their journey. Whether the guest is a leader in business, medicine or science, their answers often share a common theme: failure is not only inevitable, but essential. These moments of struggle not only propelled them forward, but sharing them also provided valuable lessons for others.

This perspective resonates deeply with the scientific process. Trial and error are at the heart of discovery, yet science is often presented as a linear narrative of success. Behind the polished journal articles and confident conference presentations, however, lies a messier reality. Failed experiments, negative results and statistical dead ends are all natural steps on the path to understanding. But these stories rarely make it into the spotlight.

In the geosciences, as in many disciplines, the pressure to publish positive results reinforces this culture of silence. Studies that confirm accepted theories or produce statistically significant results are far more likely to be published, while experiments that fail or tests of innovative ideas that fall flat are relegated to the “file drawer”. This is a problem. If unpublished failures remain hidden, others risk wasting time and resources repeating the same mistakes, starting from scratch rather than building on previous attempts.

Share your failures!

Early career researchers in particular can find this culture discouraging. Looking at the spotless CVs of senior researchers, it’s easy to assume that their paths have been smooth and free of mistakes. When these early-career scientists experience their own setbacks, they may question their abilities or even their place in the field. But failure is not a sign of inadequacy – it is a cornerstone of the scientific method, a critical part of how knowledge advances. 

At the upcoming EGU General Assembly 2025, we want to invite you to do something a bit unsual at large international conferences, where everyone’s keen to show off their successes. Please share mistakes as well as ideas that didn’t work out. What did you take away from that experience? Share your story during our session  EOS4.8 “BUGS: Blunders, Unexpected Glitches, and Surprises” 

Jonas Pyschik is a PhD student at the University of Freiburg, Chair of Hydrology. In his work, he tries to derive subsurface flow-paths and catchment scale dynamics of subsurface-stormflow using stable water isotopes. Read more on Jonas Website.


Laetitia Le Pourhiet is professor in Geodynamics @ sorbonne university and vice president elect of EGU GD division. She did learn a lot about lithospheric crustal and mantle flow from failed numerical simulation and fixing bugs in her code.


Ulrike Proske is a PostDoc at Wageningen University. Currently she studies the impact of model developers onto climate models, with bugs as one example. She is fascinated by how modelers may view these bugs as a threat, a normal part of work, or as an opportunity to learn something new.


Daniel Klotz is Assistance Professor for Machine Learning in Earth Science at the IT:U, Linz. His research focuses on developing and applying data-driven approaches for understanding, and describe the variability and movement of water. When is how much water where?


Nobuaki Fuji is a theoretical seismologist from IPGP-UPC/IUF, developing numerical methods to image planetary interiors, and also a bassoonist and composer. He creates cine-concerts with music inspired by geophysical imagery, bridging the worlds of music and seismology together. He also organises a biannual workshop CLEEDI, where scientists can talk frankly & quantitatively about our strengths and weaknesses to share our science, which reminds us of BUGS spirit, right?


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*